similar to: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > >

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 5:25 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Mon, Dec 05, 2005 at 03:03:54PM -0500, Dave Thompson > (davetho) wrote: > > > >

Searching the archives and web i''ve learned that this error has occured for other users as well. I already did quite a bit of debugging but can''t figure out what the problem might be. I''m running Xen unstable (changeset 8002) on an AMD64 server (rented from 1&1). I''ve patched the 2.6.12.6 kernel with a custom patch to get network and disk adapter running,

Hello, My name is Fermín Galán. I have started recently to use Xen (so please forgive me in advance if I''m too "newbie" :) and I''m facing my first problems... I''m trying to create a domU, but I''m getting an error: tornado:~# xm create test.cfg -c Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected.

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: normal Rebooting from inside domU hangs in initrd: Begin: Waiting for root file system... ... Root file system is not available because underlying DRBD device got deactivated during reboot: $ cat /proc/drbd version: 8.0.13 (api:86/proto:86) GIT-hash: ee3ad77563d2e87171a3da17cc002ddfd1677dbe build by phil at fat-tyre, 2008-08-04

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m using vif-route as my network script. I''ve added set -x to the xen hotplug script change. I''ve also added a command to do a listing of the xenstore directory. Here''s the snippet: == ++ ip= +++ xenstore_read_default backend/vif/4/0/ip '''' +++ xenstore-read backend/vif/4/0/ip xenstore-read: couldn''t read path backend/vif/4/0/ip +++

I am having the same problem, however on RHEL 2.6.16. I have tried setting up the bridge manually but it does not work. Can someone give some clues on what we should do to solve this problem in RHEL Thanks P. Krishna -------------- Original message -------------- From: Jens Nachtigall <nachtigall@web.de> > I found this at http://julien.danjou.info/xen.html > > Set up the

After a few times of building xen by source, I can''t start domU anyway. I tried "yum erase xen kernel-xen" and "yum install xen kernel-xen" again, but the problem is still exist. There are xenstore-write errors in /var/log/xen/xen-hotplug.log: xenstore-write: could not write path backend/vbd/1/2050/hotplug-error xenstore-write: could not write path

Hi, everyone I have some questions with the OCFS2 when using it as vm-store. With Ubuntu 1204, kernel version is 3.2.40, and ocfs2-tools version is 1.6.4. As the network configure change, there are some issues as the log below. Why is there the information of "Node 255 (he) is the Recovery Master for the dead node 255" in the syslog? Why the host ZHJD-VM6 is blocked until it reboot

Hi, everyone I have some questions with the OCFS2 when using it as vm-store. With Ubuntu 1204, kernel version is 3.2.40, and ocfs2-tools version is 1.6.4. As the network configure change, there are some issues as the log below. Why is there the information of "Node 255 (he) is the Recovery Master for the dead node 255" in the syslog? Why the host ZHJD-VM6 is blocked until it reboot

Hi all When I have a domU that resides in the auto directory I get ''Error: Device 2049 (vbd) could not be connected'' and the domain starts in a paused mode. Shutting it down and restarting has the same effect. Following is some output from the xm log and an attempted restart. Directly after dom0 reboot: xen0:/etc/xen/scripts # xm list Name ID

Error: Device 2051 (vbd) could not be connected. Hotplug scripts not working. Hello xen users,                  i got the following error Device 2051 (vbd) could not be connected. Hotplug scripts not working. my xend log (last part)looks like this [2007-06-06 12:49:44 32539] DEBUG (__init__:1094) Storing domain details: {''console/ring-ref'': ''187566'',

Hello all, I''m doing some testing with Xen and NPIV disk on the platform SLES 10 SP2 and SLES 11 (xen 3.3). On SLES 10 sp2, I have not encountered major problems during the tests (exept with live migration). I was able to attach a disk with the command "xm block-attach npiv:..." an I am also able to start a VM using a bootable NPIV disk. On sles11, after changing the script

Hi, i have seen a post with the same title, but didn''t help a lot -it mentioned, that the image was for LVM, which i don''t think is my case. I downloaded the debian31 image from http://jailtime.org. Initially, i had some problems and changed the configuration file a little. Here it is now: ----------- kernel = "/boot/vmlinuz-2.6-xenU" memory = 256 name =

Package: xen-utils-common Version: 4.0.0-1 Severity: normal After upgrading xen-utils-common from 3.4.2-4 to 4.0.0-1, I could not create a guest domain defined with a DRBD file type. The xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was

I am trying various config files to get some kind of guest start and they all seem to get stuck with the error, Error: Device 768 (vbd) could not be connected. Hotplug scripts not working. xen is 3.3.1 and Dom0 is 2.6.29. Here''s an example of one such config that reproduces this error. kernel = "/usr/lib/xen/boot/hvmloader" builder = ''hvm'' device_model =

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [

Hi, I''m new to Xen and I''ve set up a few domUs using Debian (I suspect there may be a problem there, see at end). To begin with everything worked OK, I rebooted domUs without any problems, but twice now when I try when I try to restart or shutdown a domain, the xm command locks up. # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information