thr3ads.net - Xen users - Xen does not find bridge device [May 2013]

If this information is useful, please help other people find it:
Share via:

Ole Johan Væringstad

2013-May-22 03:10 UTC

Xen does not find bridge device

Xen 4.2.0-r1, xen-tools 4.2.0-r3 from portage
Kernel 3.8.13-gentoo

/etc/conf.d/net:
config_eth0="null"
config_eth1="dhcp"
bridge_xenbr0="eth0"
config_xenbr0="dhcp"
brctl_xenbr0="setfd 0"
brctl_xenbr0="sethello 10"
brctl_xenbr0="stp on"
rc_net_xenbr0_need="net.eth0"
rc_net_xenbr0_provide="!net"
rc_net_xenbr0_provide="xenbridge"
carrier_timeout_xenbr0="0"

# brctl show
bridge name     bridge id               STP        enabled interfaces
xenbr0          8000.902b34599a01       yes             eth0

# ping -c 3 -I xenbr0 192.168.0.1
PING 192.168.0.1 (192.168.0.1) from 192.168.0.104 xenbr0: 56(84) bytes
of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.78 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.92 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.88 ms

# xl create /etc/xen/ubuntu.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019df48
  TOTAL:         0000000000000000->00000000ff800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fb
  1GB PAGES: 0x0000000000000002
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge online [9506] exited with error status 1
libxl: error: libxl_device.c:978:device_hotplug_child_death_cb:
script: Could not find bridge device xenbr0
libxl: error: libxl_create.c:1096:domcreate_attach_pci: unable to add
nic devices
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge offline [9547] exited with error status 1
libxl: error: libxl_device.c:978:device_hotplug_child_death_cb:
script: Could not find bridge device xenbr0
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge remove [9599] exited with error status 1
libxl: error: libxl_device.c:978:device_hotplug_child_death_cb:
script: Could not find bridge device xenbr0

/etc/xen/ubuntu.cfg:
builder="hvm"
name="ubuntu"
vif=[''mac=00:16:3E:00:00:02,bridge=xenbr0'']
disk=[
  ''phy:/dev/ssdraid/gentoo,hda,w'',
 
''file:/export/media/Installs/ubuntu-13.04-desktop-amd64.iso,hdd,cdrom''
  ]
memory="4096"
vcpus="2"
vnc=1
vncconsole=0
vnclisten="0.0.0.0"
vncdisplay=4
boot="dc"
on_xend_stop="shutdown"
on_poweroff="destroy"
on_reboot="destroy"
on_crash="destroy"
on_watchdog="destroy"
xen_platform_pci=1
usb=1
usbdevice=''tablet''
pci_power_mgmt=1

I''m a bit stomped, because ubuntu.cfg and the network config used to
work nicely before I did a dom0 reinstall

- OJ

Ian Campbell

2013-May-22 09:43 UTC

head link

Re: Xen does not find bridge device

On Wed, 2013-05-22 at 05:10 +0200, Ole Johan Væringstad
wrote:> Xen 4.2.0-r1, xen-tools 4.2.0-r3 from portage
> Kernel 3.8.13-gentoo
> 
> /etc/conf.d/net:
> config_eth0="null"
> config_eth1="dhcp"
> bridge_xenbr0="eth0"
> config_xenbr0="dhcp"
> brctl_xenbr0="setfd 0"
> brctl_xenbr0="sethello 10"
> brctl_xenbr0="stp on"
> rc_net_xenbr0_need="net.eth0"
> rc_net_xenbr0_provide="!net"
> rc_net_xenbr0_provide="xenbridge"
> carrier_timeout_xenbr0="0"
> 
> # brctl show
> bridge name     bridge id               STP        enabled interfaces
> xenbr0          8000.902b34599a01       yes             eth0
> 
> # ping -c 3 -I xenbr0 192.168.0.1
> PING 192.168.0.1 (192.168.0.1) from 192.168.0.104 xenbr0: 56(84) bytes
> of data.
> 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.78 ms
> 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.92 ms
> 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.88 ms
> 
> # xl create /etc/xen/ubuntu.cfg
Can you try "xl -vvv ..." for more debugging. Also have a look
under /var/log/xen for any relevant logs.

Is /etc/xen/scripts/vif-bridge present? If so then a useful debug
technique can be to add to the top
	exec >>/tmp/hotplug.log 2>&1
which will cause the script output to be logged to /tmp/hotplug.log
which might give a clue.

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Ole Johan Væringstad

2013-May-22 13:18 UTC

head link

Re: Xen does not find bridge device

On Wed, May 22, 2013 at 11:43 AM, Ian Campbell <Ian.Campbell@citrix.com>
wrote:> On Wed, 2013-05-22 at 05:10 +0200, Ole Johan Væringstad wrote:
>> Xen 4.2.0-r1, xen-tools 4.2.0-r3 from portage
>> Kernel 3.8.13-gentoo
>>
>> /etc/conf.d/net:
>> config_eth0="null"
>> config_eth1="dhcp"
>> bridge_xenbr0="eth0"
>> config_xenbr0="dhcp"
>> brctl_xenbr0="setfd 0"
>> brctl_xenbr0="sethello 10"
>> brctl_xenbr0="stp on"
>> rc_net_xenbr0_need="net.eth0"
>> rc_net_xenbr0_provide="!net"
>> rc_net_xenbr0_provide="xenbridge"
>> carrier_timeout_xenbr0="0"
>>
>> # brctl show
>> bridge name     bridge id               STP        enabled interfaces
>> xenbr0          8000.902b34599a01       yes             eth0
>>
>> # ping -c 3 -I xenbr0 192.168.0.1
>> PING 192.168.0.1 (192.168.0.1) from 192.168.0.104 xenbr0: 56(84) bytes
>> of data.
>> 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.78 ms
>> 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.92 ms
>> 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.88 ms
>>
>> # xl create /etc/xen/ubuntu.cfg
>
> Can you try "xl -vvv ..." for more debugging. Also have a look
> under /var/log/xen for any relevant logs.
>
> Is /etc/xen/scripts/vif-bridge present? If so then a useful debug
> technique can be to add to the top
>         exec >>/tmp/hotplug.log 2>&1
> which will cause the script output to be logged to /tmp/hotplug.log
> which might give a clue.
>
> Ian.
>
# xl -vvv create /etc/xen/ubuntu.cfg:

libxl: debug: libxl_create.c:1173:do_domain_create: ao 0x1664890:
create: how=(nil) callback=(nil) poller=0x16648f0
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk
vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk
vdev=hda, using backend phy
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk
vdev=hdd spec.backend=unknown
libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=hdd,
backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:184:disk_try_backend: Disk vdev=hdd,
backend tap unsuitable because blktap not available
libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk
vdev=hdd, using backend qdisk
libxl: debug: libxl_create.c:677:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:321:libxl__bootloader_run: not a PV
domain, skipping bootloader
libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch
w=0x1665280: deregister unregistered
libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best
NUMA placement candidate found: nr_nodes=1, nr_cpus=8, nr_vcpus=4,
free_memkb=28191
libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement
candidate with 1 nodes, 8 cpus and 28191 KB free selected
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9df48
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19df48
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019df48
  TOTAL:         0000000000000000->00000000ff800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fb
  1GB PAGES: 0x0000000000000002
xc: detail: elf_load_binary: phdr 0 at 0x0x7f36b190c000 -> 0x0x7f36b19a0dd5
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk
vdev=hda spec.backend=phy
libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch
w=0x16668c8 wpath=/local/domain/0/backend/vbd/14/768/state token=3/0:
register slotnum=3
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk
vdev=hdd spec.backend=qdisk
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk
vdev=hdd spec.backend=qdisk
libxl: debug: libxl_create.c:1186:do_domain_create: ao 0x1664890:
inprogress: poller=0x16648f0, flags=i
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x16668c8
wpath=/local/domain/0/backend/vbd/14/768/state token=3/0: event
epath=/local/domain/0/backend/vbd/14/768/state
libxl: debug: libxl_event.c:596:devstate_watch_callback: backend
/local/domain/0/backend/vbd/14/768/state wanted state 2 ok
libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch
w=0x16668c8 wpath=/local/domain/0/backend/vbd/14/768/state token=3/0:
deregister slotnum=3
libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch
w=0x16668c8: deregister unregistered
libxl: debug: libxl_device.c:916:device_hotplug: calling hotplug
script: /etc/xen/scripts/block add
libxl: debug: libxl_event.c:426:watchfd_callback: watch
epath=/local/domain/0/backend/vbd/14/768/state token=3/0: empty slot
libxl: debug: libxl_dm.c:1142:libxl__spawn_local_dm: Spawning
device-model /usr/lib/xen/bin/qemu-dm with arguments:
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   /usr/lib/xen/bin/qemu-dm
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -d
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   14
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -domain-name
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   ubuntu
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -vnc
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   0.0.0.0:4
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -vncunused
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -videoram
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   8
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -boot
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   dc
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -usb
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -usbdevice
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   tablet
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -acpi
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -vcpus
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   2
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -vcpu_avail
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   0x03
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -net
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:
nic,vlan=0,macaddr=00:16:3e:00:00:02,model=rtl8139
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -net
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:
tap,vlan=0,ifname=vif14.0-emu,bridge=xenbr0,script=no,downscript=no
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   -M
libxl: debug: libxl_dm.c:1144:libxl__spawn_local_dm:   xenfv
libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch
w=0x16654b8 wpath=/local/domain/0/device-model/14/state token=3/1:
register slotnum=3
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x16654b8
wpath=/local/domain/0/device-model/14/state token=3/1: event
epath=/local/domain/0/device-model/14/state
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x16654b8
wpath=/local/domain/0/device-model/14/state token=3/1: event
epath=/local/domain/0/device-model/14/state
libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch
w=0x16654b8 wpath=/local/domain/0/device-model/14/state token=3/1:
deregister slotnum=3
libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch
w=0x16654b8: deregister unregistered
libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch
w=0x1669dd8 wpath=/local/domain/0/backend/vif/14/0/state token=3/2:
register slotnum=3
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x1669dd8
wpath=/local/domain/0/backend/vif/14/0/state token=3/2: event
epath=/local/domain/0/backend/vif/14/0/state
libxl: debug: libxl_event.c:600:devstate_watch_callback: backend
/local/domain/0/backend/vif/14/0/state wanted state 2 still waiting
state 1
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x1669dd8
wpath=/local/domain/0/backend/vif/14/0/state token=3/2: event
epath=/local/domain/0/backend/vif/14/0/state
libxl: debug: libxl_event.c:596:devstate_watch_callback: backend
/local/domain/0/backend/vif/14/0/state wanted state 2 ok
libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch
w=0x1669dd8 wpath=/local/domain/0/backend/vif/14/0/state token=3/2:
deregister slotnum=3
libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch
w=0x1669dd8: deregister unregistered
libxl: debug: libxl_device.c:916:device_hotplug: calling hotplug
script: /etc/xen/scripts/vif-bridge online
+ exec
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge online [13555] exited with error status 1
libxl: error: libxl_device.c:978:device_hotplug_child_death_cb:
script: Could not find bridge device xenbr0
libxl: error: libxl_create.c:1096:domcreate_attach_pci: unable to add
nic devices
libxl: debug: libxl_dm.c:1248:libxl__destroy_device_model: Device Model signaled
libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch
w=0x166aa58 wpath=/local/domain/0/backend/vbd/14/768/state token=3/3:
register slotnum=3
libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch
w=0x166b208 wpath=/local/domain/0/backend/vif/14/0/state token=2/4:
register slotnum=2
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x166aa58
wpath=/local/domain/0/backend/vbd/14/768/state token=3/3: event
epath=/local/domain/0/backend/vbd/14/768/state
libxl: debug: libxl_event.c:596:devstate_watch_callback: backend
/local/domain/0/backend/vbd/14/768/state wanted state 6 ok
libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch
w=0x166aa58 wpath=/local/domain/0/backend/vbd/14/768/state token=3/3:
deregister slotnum=3
libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch
w=0x166aa58: deregister unregistered
libxl: debug: libxl_device.c:916:device_hotplug: calling hotplug
script: /etc/xen/scripts/block remove
libxl: debug: libxl_event.c:426:watchfd_callback: watch
epath=/local/domain/0/backend/vbd/14/768/state token=3/3: empty slot
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x166b208
wpath=/local/domain/0/backend/vif/14/0/state token=2/4: event
epath=/local/domain/0/backend/vif/14/0/state
libxl: debug: libxl_event.c:600:devstate_watch_callback: backend
/local/domain/0/backend/vif/14/0/state wanted state 6 still waiting
state 5
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x166b208
wpath=/local/domain/0/backend/vif/14/0/state token=2/4: event
epath=/local/domain/0/backend/vif/14/0/state
libxl: debug: libxl_event.c:596:devstate_watch_callback: backend
/local/domain/0/backend/vif/14/0/state wanted state 6 ok
libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch
w=0x166b208 wpath=/local/domain/0/backend/vif/14/0/state token=2/4:
deregister slotnum=2
libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch
w=0x166b208: deregister unregistered
libxl: debug: libxl_device.c:916:device_hotplug: calling hotplug
script: /etc/xen/scripts/vif-bridge offline
+ exec
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge offline [13595] exited with error status 1
libxl: error: libxl_device.c:978:device_hotplug_child_death_cb:
script: Could not find bridge device xenbr0
libxl: debug: libxl_device.c:916:device_hotplug: calling hotplug
script: /etc/xen/scripts/vif-bridge remove
+ exec
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge remove [13648] exited with error status 1
libxl: error: libxl_device.c:978:device_hotplug_child_death_cb:
script: Could not find bridge device xenbr0
libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0x1664890:
complete, rc=-3
libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0x1664890: destroy
xc: debug: hypercall buffer: total allocations:1593 total releases:1593
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:1585 misses:4 toobig:4
Parsing config from /etc/xen/ubuntu.cfg

=== /tmp/hotplug.log (exec >>/tmp/hotplug.log 2>&1 did not produce
any
output, added -x to shebang):
++ dirname /etc/xen/scripts/vif-bridge
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
+++ dirname /etc/xen/scripts/vif-bridge
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ ''['' -n 1 '']''
+++ xenstore-read libxl/disable_udev
+++ exit 0
++ dirname /etc/xen/scripts/vif-bridge
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
+++ dirname /etc/xen/scripts/vif-bridge
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ ''['' -n '''' '']''
++++ dirname /etc/xen/scripts/vif-bridge
++ dirname /etc/xen/scripts/vif-bridge
+++ dir=/etc/xen/scripts
+++ . /etc/xen/scripts/hotplugpath.sh
++++ SBINDIR=/usr/sbin
++++ BINDIR=/usr/bin
++++ LIBEXEC=/usr/lib/xen/bin
++++ LIBDIR=/usr/lib64
++++ SHAREDIR=/usr/share
++++ PRIVATE_BINDIR=/usr/lib64/xen/bin
++++ XENFIRMWAREDIR=/usr/lib/xen/boot
++++ XEN_CONFIG_DIR=/etc/xen
++++ XEN_SCRIPT_DIR=/etc/xen/scripts
++++ XEN_LOCK_DIR=/var/lock
++++ XEN_RUN_DIR=/var/run/xen
++++ XEN_PAGING_DIR=/var/lib/xen/xenpaging
+++ . /etc/xen/scripts/logging.sh
+++ . /etc/xen/scripts/xen-script-common.sh
++++ set -e
+++ . /etc/xen/scripts/locking.sh
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
++++ LOCK_BASEDIR=/var/run/xen-hotplug
+++ exec
+++ dirname /etc/xen/scripts/vif-bridge
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ ''['' -n 1 '']''
+++ xenstore-read libxl/disable_udev
+++ exit 0
++ dirname /etc/xen/scripts/vif-bridge
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
+++ dirname /etc/xen/scripts/vif-bridge
++ dirname /etc/xen/scripts/vif-bridge
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ ''['' -n 1 '']''
+++ xenstore-read libxl/disable_udev
+++ dirname /etc/xen/scripts/vif-bridge
+++ exit 0
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ ''['' -n '''' '']''
++++ dirname /etc/xen/scripts/vif-bridge
+++ dir=/etc/xen/scripts
+++ . /etc/xen/scripts/hotplugpath.sh
++++ SBINDIR=/usr/sbin
++++ BINDIR=/usr/bin
++++ LIBEXEC=/usr/lib/xen/bin
++++ LIBDIR=/usr/lib64
++++ SHAREDIR=/usr/share
++++ PRIVATE_BINDIR=/usr/lib64/xen/bin
++++ XENFIRMWAREDIR=/usr/lib/xen/boot
++++ XEN_CONFIG_DIR=/etc/xen
++++ XEN_SCRIPT_DIR=/etc/xen/scripts
++++ XEN_LOCK_DIR=/var/lock
++++ XEN_RUN_DIR=/var/run/xen
++++ XEN_PAGING_DIR=/var/lib/xen/xenpaging
+++ . /etc/xen/scripts/logging.sh
+++ . /etc/xen/scripts/xen-script-common.sh
++++ set -e
+++ . /etc/xen/scripts/locking.sh
++++ LOCK_BASEDIR=/var/run/xen-hotplug
+++ exec
++ dirname /etc/xen/scripts/vif-bridge
+ dir=/etc/xen/scripts
+ . /etc/xen/scripts/vif-common.sh
+++ dirname /etc/xen/scripts/vif-bridge
++ dir=/etc/xen/scripts
++ . /etc/xen/scripts/xen-hotplug-common.sh
+++ ''['' -n '''' '']''
++++ dirname /etc/xen/scripts/vif-bridge
+++ dir=/etc/xen/scripts
+++ . /etc/xen/scripts/hotplugpath.sh
++++ SBINDIR=/usr/sbin
++++ BINDIR=/usr/bin
++++ LIBEXEC=/usr/lib/xen/bin
++++ LIBDIR=/usr/lib64
++++ SHAREDIR=/usr/share
++++ PRIVATE_BINDIR=/usr/lib64/xen/bin
++++ XENFIRMWAREDIR=/usr/lib/xen/boot
++++ XEN_CONFIG_DIR=/etc/xen
++++ XEN_SCRIPT_DIR=/etc/xen/scripts
++++ XEN_LOCK_DIR=/var/lock
++++ XEN_RUN_DIR=/var/run/xen
++++ XEN_PAGING_DIR=/var/lib/xen/xenpaging
+++ . /etc/xen/scripts/logging.sh
+++ . /etc/xen/scripts/xen-script-common.sh
++++ set -e
+++ . /etc/xen/scripts/locking.sh
++++ LOCK_BASEDIR=/var/run/xen-hotplug
+++ exec

=== /var/log/xen/qemu-dm-ubuntu.log:
domid: 14
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
Using file /dev/ssdraid/gentoo in read-write mode
Strip off blktap sub-type prefix to
/export/media/Installs/ubuntu-13.04-desktop-amd64.iso (drv
''aio'')
Using file /export/media/Installs/ubuntu-13.04-desktop-amd64.iso in
read-only mode
Watching /local/domain/0/device-model/14/logdirty/cmd
Watching /local/domain/0/device-model/14/command
Watching /local/domain/14/cpu
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 7227a926-9e41-4297-90a0-8ae9acba8b62
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/14/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/7227a926-9e41-4297-90a0-8ae9acba8b62/vncpasswd.
medium change watch on `hdd'' (index: 1):
aio:/export/media/Installs/ubuntu-13.04-desktop-amd64.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
vcpu-set: watch node error.
xs_read(/local/domain/14/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/14/log-throttling''
medium change watch on `/local/domain/14/log-throttling'' - unknown
device, ignored

=== /var/log/xen/xen-hotplug.log:
+++ export
PATH=/usr/bin:/usr/sbin:/usr/lib/xen/bin:/usr/lib64/xen/bin:/sbin:/bin:/usr/bin:/usr/sbin:/root/.gem/ruby/1.9.1/bin:/opt/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/sbin:/bin:/root/.bash:/root/.python:/root/.ruby:/root/.tcl:/usr/sbin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3
+++
PATH=/usr/bin:/usr/sbin:/usr/lib/xen/bin:/usr/lib64/xen/bin:/sbin:/bin:/usr/bin:/usr/sbin:/root/.gem/ruby/1.9.1/bin:/opt/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/sbin:/bin:/root/.bash:/root/.python:/root/.ruby:/root/.tcl:/usr/sbin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3
+++ export LANG=POSIX
+++ LANG=POSIX
++++ set
++++ cut -d= -f1
++++ grep ''^LC_''
+++ unset
+++ trap sigerr ERR
+++ log debug remove type_if=tap XENBUS_PATH=backend/vif/14/0
+++ local level=debug
+++ shift
+++ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: remove
type_if=tap XENBUS_PATH=backend/vif/14/0
++ . /etc/xen/scripts/xen-network-common.sh
+++ which ifup
++ findCommand remove type_if=tap
++ for arg in ''"$@"''
++ expr index remove ++ command=remove
++ return
++ ''['' remove ''!='' online
'']''
++ ''['' remove ''!='' offline
'']''
++ ''['' remove ''!='' add '']''
++ ''['' remove ''!='' remove
'']''
++ evalVariables remove type_if=tap
++ for arg in ''"$@"''
++ expr index remove = ''>'' 1
++ for arg in ''"$@"''
++ expr index type_if=tap = ''>'' 1
++ eval type_if=tap
+++ type_if=tap
++ : tap
++ case "$type_if" in
++ dev=vif14.0-emu
++ case "$command" in
++ test tap ''!='' tap
++ ''['' tap = vif '']''
++ ''['' tap = tap '']''
++ : vif14.0-emu
++ dev_=14.0-emu
++ dev_=14.0
++ domid=14
++ devid=0
++ XENBUS_PATH=/local/domain/0/backend/vif/14/0
+++ xenstore_read_default /local/domain/0/backend/vif/14/0/vifname
''''
+++ xenstore-read /local/domain/0/backend/vif/14/0/vifname
+++ echo ''''
++ vifname++ ''['' '''' '']''
++ ip+++ xenstore_read_default /local/domain/0/backend/vif/14/0/ip
''''
+++ xenstore-read /local/domain/0/backend/vif/14/0/ip
+++ echo ''''
++ ip+ bridge++ xenstore_read_default /local/domain/0/backend/vif/14/0/bridge
''''
++ xenstore-read /local/domain/0/backend/vif/14/0/bridge
+ bridge=xenbr0
+ ''['' -z xenbr0 '']''
+ ''['' ''!'' -e /sys/class/net/xenbr0
'']''
+ RET=0
+ ip link show xenbr0
+ RET=1
+ ''['' 1 -eq 1 '']''
+ fatal ''Could not find bridge device xenbr0''
+ _xenstore_write /local/domain/0/backend/vif/14/0/hotplug-error
''Could not find bridge device xenbr0''
/local/domain/0/backend/vif/14/0/hotplug-status error
+ log debug ''Writing
/local/domain/0/backend/vif/14/0/hotplug-error''
''Could not find bridge device xenbr0''
/local/domain/0/backend/vif/14/0/hotplug-status ''error to
xenstore.''
+ local level=debug
+ shift
+ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: ''Writing
/local/domain/0/backend/vif/14/0/hotplug-error'' ''Could not
find bridge
device xenbr0'' /local/domain/0/backend/vif/14/0/hotplug-status
''error
to xenstore.''
+ xenstore-write /local/domain/0/backend/vif/14/0/hotplug-error ''Could
not find bridge device xenbr0''
/local/domain/0/backend/vif/14/0/hotplug-status error
+ log err ''Could not find bridge device xenbr0''
+ local level=err
+ shift
+ logger -p daemon.err -- /etc/xen/scripts/vif-bridge: ''Could not find
bridge device xenbr0''
+ exit 1

- OJ

Ian Campbell

2013-May-22 15:32 UTC

head link

Re: Xen does not find bridge device

On Wed, 2013-05-22 at 15:18 +0200, Ole Johan Væringstad
wrote:> ++ xenstore-read /local/domain/0/backend/vif/14/0/bridge
> + bridge=xenbr0
> + '[' -z xenbr0 ']'
> + '[' '!' -e /sys/class/net/xenbr0 ']'
> + RET=0
> + ip link show xenbr0
> + RET=1
> + '[' 1 -eq 1 ']'
> + fatal 'Could not find bridge device xenbr0'
This is a new failure mode for me.

Does /sys/class/net/xenbr0 exist?

What does "ip link show xenbr0; echo $?" produce?

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Ian Campbell

2013-May-22 15:34 UTC

head link

Re: Xen does not find bridge device

On Wed, 2013-05-22 at 16:32 +0100, Ian Campbell wrote:> On Wed, 2013-05-22 at 15:18 +0200, Ole Johan Væringstad wrote:
> > ++ xenstore-read /local/domain/0/backend/vif/14/0/bridge
> > + bridge=xenbr0
> > + '[' -z xenbr0 ']'
> > + '[' '!' -e /sys/class/net/xenbr0 ']'
> > + RET=0
> > + ip link show xenbr0
> > + RET=1
> > + '[' 1 -eq 1 ']'
> > + fatal 'Could not find bridge device xenbr0'
> 
> This is a new failure mode for me.
> 
> Does /sys/class/net/xenbr0 exist?
> 
> What does "ip link show xenbr0; echo $?" produce?
BTW, I assume you have the iproute package (or ebuild or whatever)
installed?



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Ole Johan Væringstad

2013-May-22 17:00 UTC

head link

Re: Xen does not find bridge device

On Wed, May 22, 2013 at 5:34 PM, Ian Campbell <Ian.Campbell@citrix.com>
wrote:> On Wed, 2013-05-22 at 16:32 +0100, Ian Campbell wrote:
>> On Wed, 2013-05-22 at 15:18 +0200, Ole Johan Væringstad wrote:
>> > ++ xenstore-read /local/domain/0/backend/vif/14/0/bridge
>> > + bridge=xenbr0
>> > + ''['' -z xenbr0 '']''
>> > + ''['' ''!'' -e
/sys/class/net/xenbr0 '']''
>> > + RET=0
>> > + ip link show xenbr0
>> > + RET=1
>> > + ''['' 1 -eq 1 '']''
>> > + fatal ''Could not find bridge device xenbr0''
>>
>> This is a new failure mode for me.
>>
>> Does /sys/class/net/xenbr0 exist?
>>
>> What does "ip link show xenbr0; echo $?" produce?
>
> BTW, I assume you have the iproute package (or ebuild or whatever)
> installed?
I figured it out.

I had iproute2 3.8.0 installed, but I also have the global "minimal"
use flag, with which the iproute2 ebuild only installs tc.
Ironically, the iproute2 package was the only installed package to be
modified by the minimal use flag, so it only saved me
something I actually needed.

It''s working fine now, sorry for posting something that was not a xen
issue.

- OJ

Xen users - May 2013 - Xen does not find bridge device

Xen does not find bridge device

Re: Xen does not find bridge device

Re: Xen does not find bridge device

Re: Xen does not find bridge device

Re: Xen does not find bridge device

Re: Xen does not find bridge device