Public bug reported: I have been having troubles with Xen simply being unable to run paravirt domUs since I built a gutsy server a while ago. When booting a domU it would bomb out to the initrd busybox shell because it could not find its root device. (The same config works fine on an Ubuntu 7.04 Xen server.) Used dist-upgrade to track hardy, trying xen-3.1 and then xen-3.2 packges. After a while I blamed the problems on EVMS because I was using EVMS volumes for the root and swap devices for domUs. However then after trying the loopback file method I couldn't get the domU to start either. The error message is the same that is posted in another bug report:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/199533/comments/31 So, today I put in a new system disk into this problem server and installed from scratch using hardy i386 alpha 2008-03-16 CD. Then apt- get update to current (2008-03-23) packages. Installed ubuntu-xen- server, rebooted to Xen dom0 kernel. System is an oldPentium 4, no HVM, no x86_64; single IDE 80Gb hard drive partitioned by Ubuntu installer. Linux dom0 2.6.24-12-xen #1 SMP Thu Mar 13 01:23:51 UTC 2008 i686 GNU/Linux Built a test domU system: sudo xen-create-image --verbose --accounts --cache --image=full --size=4Gb --swap=1024Mb --memory=256Mb --dhcp --dir=/xen --hostname=domU Trying to start it up gives this error: [EMAIL PROTECTED]:~$ sudo xm create -c /etc/xen/domU.cfg Using config file "/etc/xen/domU.cfg". Error: Device 2049 (vbd) could not be connected. losetup /dev/loop0 /xen/domains/domU/swap.img failed However Xen seems to be fibbing: [EMAIL PROTECTED]:~$ sudo losetup -a /dev/loop0: [fe00]:1015812 (/xen/domains/domU/swap.img) /dev/loop1: [fe00]:1015813 (/xen/domains/domU/disk.img) With the default xen-tools.conf the device names are sdX, I tried changing them to xvdX but this did not fix the problem. Of course before trying an 'xm create' again I ran sudo losetup -d /dev/loop0 sudo losetup -d /dev/loop1 So losetup works, and I can loopback-mount the disk.img filesystem onto /mnt without any problems. The following are xen-related entries from /var/log/syslog at the time I was trying to start this domU. Mar 23 17:30:59 dom0 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/2049 Mar 23 17:30:59 dom0 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/2050 Mar 23 17:30:59 dom0 logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/1/0 Mar 23 17:31:00 dom0 logger: /etc/xen/scripts/block: Writing backend/vbd/1/2049/hotplug-error losetup /dev/loop0 /xen/domains/domU/swap.img failed backend/vbd/1/2049/hotplug-status error to xenstore. Mar 23 17:31:00 dom0 logger: /etc/xen/scripts/block: losetup /dev/loop0 /xen/domains/domU/swap.img failed Mar 23 17:31:00 dom0 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif1.0, bridge eth1. Mar 23 17:31:00 dom0 logger: /etc/xen/scripts/vif-bridge: Writing backend/vif/1/0/hotplug-status connected to xenstore. Mar 23 17:31:01 dom0 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/console/1/0 Mar 23 17:31:01 dom0 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/2049 Mar 23 17:31:01 dom0 logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/1/0 Mar 23 17:31:01 dom0 logger: /etc/xen/scripts/block: Writing backend/vbd/1/2049/hotplug-error xenstore-read backend/vbd/1/2049/node failed. backend/vbd/1/2049/hotplug-status error to xenstore. Mar 23 17:31:02 dom0 logger: /etc/xen/scripts/block: xenstore-read backend/vbd/1/2049/node failed. Mar 23 17:31:02 dom0 logger: /etc/xen/scripts/block: Writing backend/vbd/1/2049/hotplug-error /etc/xen/scripts/block failed; error detected. backend/vbd/1/2049/hotplug-status error to xenstore. Mar 23 17:31:02 dom0 logger: /etc/xen/scripts/block: /etc/xen/scripts/block failed; error detected. Mar 23 17:31:02 dom0 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/1/2049 Mar 23 17:31:03 dom0 logger: /etc/xen/scripts/vif-bridge: brctl delif eth1 vif1.0 failed Mar 23 17:31:03 dom0 logger: /etc/xen/scripts/vif-bridge: ifconfig vif1.0 down failed Mar 23 17:31:03 dom0 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif1.0, bridge eth1. Mar 23 17:31:03 dom0 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/1/0 /var/log/xen/xen-hotplug.log tells me unhelpful things like this: xenstore-read: couldn't read path backend/vbd/8/2049/node xenstore-read: couldn't read path backend/vbd/8/2050/node And the last section of /var/log/xen/xend.log: [2008-03-23 17:31:00 4665] DEBUG (DevController:150) Waiting for devices vif. [2008-03-23 17:31:00 4665] DEBUG (DevController:155) Waiting for 0. [2008-03-23 17:31:00 4665] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2008-03-23 17:31:00 4665] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2008-03-23 17:31:00 4665] DEBUG (DevController:608) hotplugStatusCallback 1. [2008-03-23 17:31:00 4665] DEBUG (DevController:150) Waiting for devices vbd. [2008-03-23 17:31:00 4665] DEBUG (DevController:155) Waiting for 2049. [2008-03-23 17:31:01 4665] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vbd/1/2049/hotplug-status. [2008-03-23 17:31:01 4665] DEBUG (DevController:608) hotplugStatusCallback 2. [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:1913) XendDomainInfo.destroy: domid=1 [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:1930) XendDomainInfo.destroyDomain(1) [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:1548) Destroying device model [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:1555) Releasing devices [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:1561) Removing vif/0 [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:590) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:1561) Removing vbd/2049 [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:590) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049 [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:1561) Removing vbd/2050 [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:590) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050 [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:1561) Removing console/0 [2008-03-23 17:31:01 4665] DEBUG (XendDomainInfo:590) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 So I'm not really sure where my problem is. xenstore? /etc/xen/scripts/block? /etc/xen/scripts/xen-hotplug-common.sh? Can someone please help. It is driving me seriously up the wall that I cannot build a working Xen server with Ubuntu. Andrew S. ** Affects: xen-3.2 (Ubuntu) Importance: Undecided Status: New -- xend fails to connect guest to dom0 block device or loopback file https://bugs.launchpad.net/bugs/205450 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
