search for: operst

Hi, I encounter a problem that the eth can't be up in the VM by using VT-d. I boot the VM using "virsh create vt_d.xml". The VM could recongize the NIC which was assigned .then I do in VM as follows: #cat /sys/class/net/eth0/operstate down #ifconfig eth0 up #cat /sys/class/net/eth0/operstate down #ficonfig eth 10.100.0.5 #cat /sys/class/net/eth0/operstate down more system information is attached.(uname ?ifconfig ?lspci?cmdline...) I can't figure out the reason why the eth is still down? can anyone help me ? best regards...

...ght up. > What piece of data can I monitor programmatically (C++, python, etc) to know > when the interface is up and running ok? > > What I want to void is having to execute an ifconfig command and then parse > the output in a program. There's /sys/class/net/<interface>/operstate, which should exist and contain "up" when the interface is up. Otherwise, there's the netlink interface, but I've never worked with that myself. But be warned, whether an interface is up still doesn't mean that your network is actually working. For example, you'd want...

...piece of data can I monitor programmatically (C++, python, etc) to know >> when the interface is up and running ok? >> >> What I want to void is having to execute an ifconfig command and then parse >> the output in a program. > There's /sys/class/net/<interface>/operstate, which should exist and > contain "up" when the interface is up. Otherwise, there's the netlink > interface, but I've never worked with that myself. > > But be warned, whether an interface is up still doesn't mean that your > network is actually working. For...

On Mon, Feb 29, 2016 at 07:48:45AM -0600, md at rpzdesign.com wrote: > I want to use TIncVPN in a systemd Ubuntu environment. > > But I want other services to run AFTER tinc has started running and has its > tun0 device initialized and ready. > > Does anybody have a suggestion on what I put into the service files so that > they are ExecStart after Tinc has come up at boot

...esuming at sender. Output from crashed VM: [69204.815336] kernel BUG at /build/buildd-linux-2.6_2.6.32-31-amd64-vrfdM4/linux-2.6-2.6.32/debian/build/source_amd64_xen/drivers/xen/events.c:1245! [69204.815336] invalid opcode: 0000 [#1] SMP [69204.815336] last sysfs file: /sys/devices/virtual/net/lo/operstate [69204.815336] CPU 0 [69204.815336] Modules linked in: dm_snapshot dm_mirror dm_region_hash dm_log snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr evdev xfs exportfs dm_mod xen_blkfront xen_netfront [69204.815336] Pid: 9975, comm: kstop/0 Not tainted 2.6.32-5-xen-amd64 #1 [69204.815336] RI...

...6.32-bpo.5-amd64 2.6.32-30~bpo50+1 Linux 2.6.32 for 64-bit PCs ii xen-hypervisor-4.0-amd64 4.0.1-2 The Xen Hypervisor on AMD64 Here is the trace : [469390.126691] alignment check: 0000 [#1] SMP [469390.126711] last sysfs file: /sys/devices/virtual/net/lo/operstate [469390.126718] CPU 0 [469390.126725] Modules linked in: snd_pcsp xen_netfront snd_pcm evdev snd_timer snd soundcore snd_page_alloc ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_snapshot dm_mod xen_blkfront thermal_sys [469390.126772] Pid: 22077, comm: rsh Not tainted 2.6.32-bpo.5-amd64 #1...

...6.32-bpo.5-amd64 2.6.32-30~bpo50+1 Linux 2.6.32 for 64-bit PCs ii xen-hypervisor-4.0-amd64 4.0.1-2 The Xen Hypervisor on AMD64 Here is the trace : [469390.126691] alignment check: 0000 [#1] SMP [469390.126711] last sysfs file: /sys/devices/virtual/net/lo/operstate [469390.126718] CPU 0 [469390.126725] Modules linked in: snd_pcsp xen_netfront snd_pcm evdev snd_timer snd soundcore snd_page_alloc ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_snapshot dm_mod xen_blkfront thermal_sys [469390.126772] Pid: 22077, comm: rsh Not tainted 2.6.32-bpo.5-amd64 #1...

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal This issue is similar to http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2011-March/003217.html but since I was not able to find a bug report I'm reporting this now. Steps to reproduce: 1) cat << EOF > config name = 'squeeze64' vcpus = '4' memory = '512' disk = [

Changes since v9: * series re-ordering so make functionality more distinct. Basic vlan filtering is patches 1-4. Support for PVID/untagged vlans is patches 5 and 6. VLAN support for FDB/MDB is patches 7-11. Patch 12 is still additional egress policy. * Slight simplification to code that extracts the VID from skb. Since we now depend on the vlan module, at the time of input skb_tci is

This series of patches provides an ability to add VLANs to the bridge ports. This is similar to what can be found in most switches. The bridge port may have any number of VLANs added to it including vlan 0 priority tagged traffic. When vlans are added to the port, only traffic tagged with particular vlan will forwarded over this port. Additionally, vlan ids are added to FDB entries and become