Error Device 2048 Vbd Could Not Be Connected
could not be connected Date: Tue, 2 Sep 2008 10:04:14 +0530 Hi, --- On Mon, Sep 1, 2008 at 9:04 PM, Samuel Thibault
to Milestone xen-3.2 (Ubuntu) Edit Confirmed Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: xen-3.2 (Ubuntu) Filed here by: Andrew Shugg When: 2008-03-23 Confirmed: 2008-03-24 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Confirmed Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report xen-tools (Ubuntu) Edit Confirmed Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: xen-tools (Ubuntu) Filed here by: Todd Deshane https://lists.gnu.org/archive/html/bug-hurd/2008-09/msg00006.html When: 2008-03-24 Confirmed: 2013-01-03 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Confirmed Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description I have been having troubles with Xen https://bugs.launchpad.net/bugs/205450 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: sysadmin@dom0:~$ sudo xm create -c /etc/xen/domU.cfg Using config file
Log In [x] | Forgot Password Login: [x] First Last Prev Next This bug is not in your last search results. Bug20481 https://forge.univention.org/bugzilla/show_bug.cgi?id=20481 - xend.err 'Device 768 (vbd) could not be connected. Hotplug scripts not working. Summary: xend.err 'Device 768 (vbd) could not be connected. Hotplug scripts not working. Status: CLOSED FIXED Product: UCS http://gnu.hurd.bug.narkive.com/P4TtlllH/xen-hurd-error-device-768-vbd-could-not-be-connected Classification: Unclassified Component: Virtualization - Xen Version: UCS 3.2 Hardware: Other Linux Importance: P5 normal (vote) TargetMilestone: UCS 3.2-0-errata Assigned To: Philipp Hahn QA Contact: Erik Damrose URL: Keywords: Depends on: error device 33924 Blocks: 35531 Show dependency tree /graph Reported: 2010-10-22 09:56 CEST by Arvid Requate Modified: 2014-07-31 09:22 CEST (History) CC List: 6 users (show) buesching damrose gohmann hahn jmm walkenhorst See Also: What kind of report is it?: --- What type of bug is this?: --- Who will be affected by this bug?: --- How will those affected feel error device 2048 about the bug?: --- User Pain: Enterprise Customer affected?: School Customer affected?: ISV affected?: Ticket number: Bug group (optional): Attachments /var/log/xen/qemu-dm-winxp-test001.log (875 bytes, text/plain) 2010-10-22 09:59 CEST, Arvid Requate Details /var/log/xen/xen-hotplug.log (36 bytes, text/plain) 2010-10-22 10:01 CEST, Arvid Requate Details /var/log/xen/xend.log (31.90 KB, text/plain) 2010-10-22 10:01 CEST, Arvid Requate Details Debug logs von libvirt und xend (539.49 KB, application/x-gtar) 2010-10-22 12:38 CEST, Arvid Requate Details View All Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description Arvid Requate 2010-10-22 09:56:48 CEST Beim Starten eines frisch kopieren XP-Images im UMC Modul UVMM erschien das Popup: Error managing domain "bdb3a479-6e16-7427-09d3-f88271d29bcd": POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 768 (vbd) could not be connected. Hotplug scripts not working.') Nach einem erneuten Startversuch der VM blieb das UMC Modul im Reload hängen. Nach erneutem Einloggen in die UMC wurde die VM nicht mehr im UVMM Modul angezeigt. Ein restart von uvmm-daemon und uvmm-node-common hat daran nichts geändert. UCS 2.4 mit Scope uvmm: python-univention-virtual-machine-manager 0.10.4-5.97.201010191625 univention-virtual-machine-manager-daemon 0.9.106-1.92.201008230911 univention-virtual-machine-manager-node-common 0.1.13-1.14.2
HP Compaq nx7400 laptop running Debian GNU/Linux (Lenny/sid). Ihave installed all the .deb from the above URL as well asxen-hypervisor-3.2-1-i386-nonpae. Copied gnumach-xen, hurd-modules to/boot. My /etc/xen/hurd is as follows:=== Hurd ===kernel = "/boot/gnumach-xen"memory = 256disk = ['phy:hda1,hda,w']extra = "root=device:hd0"# vif = [ 'dhcp' ]ramdisk = "/boot/hurd-modules"=== END ===I booted into the Xen 3.2-1-i386-nonpae / Debian GNU/Linux, kernel2.6.18-6-xen-686-nonpae. When running 'sudo xm create -c hurd', I getthe following output:=== OUTPUT ===Using config file "/etc/xen/hurd".Error: Device 768 (vbd) could not be connected. Hotplug scripts not working.=== END ===Is the value of disk in /etc/xen/hurd file correct? I have / in/dev/sda1, /home in /dev/sda2, swap in /dev/sda3. Appreciate any helpin this regard,Thanks!SK--Shakthi Kannanhttp://www.shakthimaan.com Samuel Thibault 2008-08-31 20:04:30 UTC PermalinkRaw Message Post by Shakthi KannanUsing config file "/etc/xen/hurd".Error: Device 768 (vbd) could not be connected. Hotplug scripts not working.Check xend logs.Just to make sure: hda1 is not mounted in dom0, right?Samuel Shakthi Kannan 2008-09-01 08:40:27 UTC PermalinkRaw Message Hi,--- On Mon, Sep 1, 2008 at 1:34 AM, Samuel Thibault<***@ens-lyon.org> wrote:| hda1 is not mounted in dom0, right?\--There is no hda1 on the system, only sda1 (/), sda2 (/home), sda3(swap). Do we need to specify a mounted partition or what does thisdisk signify in /etc/xen/hurd?SK--Shakthi Kannanhttp://www.shakthimaan.com Samuel Thibault 2008-09-01 15:34:15 UTC PermalinkRaw Message Post by Shakthi Kannan--- On Mon, Sep 1, 2008 at 1:34 AM, Samuel Thibault| hda1 is not mounted in dom0, right?\--There is no hda1 on the system, only sda1 (/), sda2 (/home), sda3(swap).Then specify sda1...Post by Shakthi KannanDo we need to specify a mounted partition or what does this disksignify in /etc/xen/hurd?If you could read the xen doc that could help :)disk = ['phy:hda1,hda,w']means /dev/hda1 in the host system, hda in the guest system.Samuel Shakthi Kannan 2008-09-02 04:34:14 UTC PermalinkRaw Message Hi,--- On Mon, Sep 1, 2008 at 9:04 PM, Samuel Thibault<***@ens-lyon.org