Fermín Galán Márquez
2007-Feb-22 12:24 UTC
[Xen-users] Problem creating domU: "Device 2049 (vbd) could not be connected. Hotplug scripts not working."
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. Hotplug scripts not working. I''ve goolgled for the error message, but nothing I''ve found seems to apply to my case. Any idea of what can be the meaning, possible solution or further test that can be performed in order to diagnose the problem? Thanks in advance! Reference stuff follows. The /etc/xen/test.cfg files is: kernel = ''/boot/vmlinuz-2.6.18-3-xen-686'' ramdisk = ''/boot/initrd.img-2.6.18-3-xen-686'' memory = ''32'' root = ''/dev/sda1 ro'' disk = [ ''file:/root/xen-test/domains/test/disk.img,sda1,w'', ''file:/root/xen-test/domains/test/swap.img,sda2,w'' ] name = ''test'' vif = [ ''mac=00:0C:29:11:22:33, ip=192.168.247.140'' ] on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' The test.cfg configuration file and the disk files (/root/xen-test/domains/test/disk.img and /root/xen-test/domains/test/swap.img) were created using: xen-create-image --hostname=test --ip=192.168.247.140 --passwd --debootstrap Last lines in /var/log/xen/xend.log (note the around 2 minutes waiting interval after the hotplugStatusCallback /local/domain/0/backend/vbd/3/2049/hotplug-status line): [2007-02-22 13:01:41 xend 2681] DEBUG (__init__:1072) Waiting for devices vif. [2007-02-22 13:01:41 xend.XendDomainInfo 2681] DEBUG (__init__:1072) XendDomainInfo.handleShutdownWatch [2007-02-22 13:01:41 xend 2681] DEBUG (__init__:1072) Waiting for 0. [2007-02-22 13:01:41 xend 2681] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vif/3/0/hotplug-status. [2007-02-22 13:01:44 xend 2681] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vif/3/0/hotplug-status. [2007-02-22 13:01:44 xend 2681] DEBUG (__init__:1072) hotplugStatusCallback 1. [2007-02-22 13:01:44 xend 2681] DEBUG (__init__:1072) Waiting for devices usb. [2007-02-22 13:01:44 xend 2681] DEBUG (__init__:1072) Waiting for devices vbd. [2007-02-22 13:01:44 xend 2681] DEBUG (__init__:1072) Waiting for 2049. [2007-02-22 13:01:44 xend 2681] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vbd/3/2049/hotplug-status. [2007-02-22 13:03:24 xend.XendDomainInfo 2681] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=3 [2007-02-22 13:03:24 xend.XendDomainInfo 2681] DEBUG (__init__:1072) XendDomainInfo.destroyDomain(3) [2007-02-22 13:03:31 xend 2681] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vbd/3/2049/hotplug-status. [2007-02-22 13:03:31 xend 2681] DEBUG (__init__:1072) hotplugStatusCallback 2. Last lines in /var/log/xen/xen-hotplug.log: Nothing to flush. xenstore-read: couldn''t read path backend/vbd/3/2050/node xenstore-read: couldn''t read path backend/vbd/3/2049/node Detail of my Xen related packages (I''m using Debian/Testing): tornado:~# dpkg -l | grep xen | cut -c 1-69 ii libc6-xen 2.3.6.ds1-11 ii linux-image-2.6-xen-686 2.6.18+5 ii linux-image-2.6.18-3-xen-686 2.6.18-7 ii linux-image-xen-686 2.6.18+5 ii linux-modules-2.6.18-3-xen-686 2.6.18-7 ii xen-hypervisor-3.0.3-1-i386 3.0.3-0-2 ii xen-tools 2.8-2 ii xen-utils-3.0.3-1 3.0.3-0-2 ii xen-utils-common 3.0.3-0-2 Detail of my kernel: tornado:~# uname -ra Linux tornado 2.6.18-3-xen-686 #1 SMP Mon Dec 4 20:48:20 UTC 2006 i686 GNU/Linux I''m running Xen in a 288MB physical RAM system, booting with dom0_mem=256M (in fact, I''m not using a physical PC but one running as VMware virtual machine, but I guess that it doesn''t matter, does it?) Best regards, -------------------- Fermín Galán Márquez CTTC - Centre Tecnològic de Telecomunicacions de Catalunya Parc Mediterrani de la Tecnologia, Av. del Canal Olímpic s/n, 08860 Castelldefels, Spain Room 1.02 Tel : +34 93 645 29 12 Fax : +34 93 645 29 01 Email address: fermin dot galan at cttc dot es _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Rendon, Curtis
2007-Feb-22 18:52 UTC
RE: [Xen-users] Problem creating domU: "Device 2049 (vbd) could not be connected. Hotplug scripts not working."
> Date: Thu, 22 Feb 2007 13:24:10 +0100 > From: Ferm?n Gal?n M?rquez <fermin.galan@CTTC.ES> > Subject: [Xen-users] Problem creating domU: "Device 2049 (vbd) could > not be connected. Hotplug scripts not working." > To: <xen-users@lists.xensource.com> > Message-ID: <010e01c7567c$5edf3b90$303d5854@cttc.es> > Content-Type: text/plain; charset="iso-8859-1" > > 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. Hotplug scripts not > working. > ...As a test try commenting out the vif= line in your config file. Curtis -- XEN of AMD Curtis W. Rendon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fermín Galán Márquez
2007-Feb-27 12:30 UTC
RE: [Xen-users] Problem creating domU:"Device 2049 (vbd) could not be connected. Hotplug scripts notworking."
Dear Curtis, First of all, thanks for your answer!>> 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. Hotplug scripts not >> working. >> ... > > As a test try commenting out the vif= line in your config file.Two new facts: 1. I''ve done what you said (commenting out the vif= line), but the result is the same :( 2. Sometimes, I get a slightly different error message than the one I reported originally ("Backend device not found" instead of "Hotplug scripts not working"). tornado:~# xm create test.cfg -c Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Backend device not found. The error message type doesn''t seem related with the vif= line. In other words, I''ve get both of them either commenting or not commenting the vifline, although "Backend device not found" seems to be less frequent (see typescript of the test at the end of the mail). What is the exact meaning of each one of this error messages? What is the device number 2049? Any new piece of information/test ideas is very welcome... Thanks again! Best regards, -------------------- Fermín Galán Márquez CTTC - Centre Tecnològic de Telecomunicacions de Catalunya Parc Mediterrani de la Tecnologia, Av. del Canal Olímpic s/n, 08860 Castelldefels, Spain Room 1.02 Tel : +34 93 645 29 12 Fax : +34 93 645 29 01 Email address: fermin dot galan at cttc dot es PD. Detail of the test follows: tornado:~# cat /etc/xen/test.cfg | grep vif tornado:~# xm create test.cfg -c ; xm create test.cfg -c ; xm create test.cfg -c ; xm create test.cfg -c ; xm create test.cfg -c Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Backend device not found. Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. tornado:~# vi /etc/xen/test.cfg tornado:~# cat /etc/xen/test.cfg | grep vif #vif = [ ''mac=00:0C:29:11:22:33, ip=192.168.247.140'' ] tornado:~# xm create test.cfg -c ; xm create test.cfg -c ; xm create test.cfg -c ; xm create test.cfg -c ; xm create test.cfg -c Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Backend device not found. Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniele Palumbo
2007-Mar-01 13:31 UTC
Re: [Xen-users] Problem creating domU: "Device 2049 (vbd) could not be connected. Hotplug scripts not working."
On Thursday 22 February 2007 13:24, Fermín Galán Márquez wrote:> tornado:~# xm create test.cfg -c > Using config file "/etc/xen/test.cfg". > Error: Device 2049 (vbd) could not be connected. Hotplug scripts not > working.i have the same problem. now on: my setup is sightly different. i have clvm, but this is always with local lv. sometimes mounting the volume and unmounting it can resolve the problem. other times, it is resolved only by waiting one minute or two. i am suspecting something about ''sync'', but seems strange... logs cannot help at all (AFAIK). i am also curious about wtf is vbd 2049. anyone else? bye d. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jordi Segues
2007-Mar-07 14:12 UTC
Re: [Xen-users] Problem creating domU: "Device 2049 (vbd) could not be connected. Hotplug scripts not working."
Hello, I have exactly the same problem: xm create /etc/xen/VM1.cfg Using config file "/etc/xen/VM1.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working I use LVM partitions for the disk. There''s my VM1.cfg: kernel = ''/boot/vmlinuz-2.6.18-4-xen-686'' ramdisk = ''/boot/initrd.img-2.6.18-4-xen-686'' memory = ''128'' root = ''/dev/sda1 ro'' disk = [ ''phy:lvm/VM1-disk,sda1,w'', ''phy:lvm/VM1-swap,sda2,w'' ] name = ''VM1'' vif = [ ''ip=172.16.100.202'' ] on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' And that''s what logs say: /var/log/xen/xend.log -------------------------------------- [2007-03-07 16:17:22 xend.XendDomainInfo 16300] DEBUG (__init__:1072) XendDomainInfo.handleShutdownWatch [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) Waiting for devices vif. [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) Waiting for devices usb. [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) Waiting for devices vbd. [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) Waiting for 2049. [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. [2007-03-07 16:17:30 xend 16300] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vbd/3/2049/hotplug-status. [2007-03-07 16:17:30 xend 16300] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vbd/3/2049/hotplug-status. [2007-03-07 16:18:47 xend.XendDomainInfo 16300] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=4 [2007-03-07 16:18:47 xend.XendDomainInfo 16300] DEBUG (__init__:1072) XendDomainInfo.destroyDomain(4) [2007-03-07 16:20:42 xend 16300] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. [2007-03-07 16:20:42 xend 16300] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vbd/4/2049/hotplug-status. [2007-03-07 16:20:42 xend 16300] DEBUG (__init__:1072) hotplugStatusCallback /local/domain/0/backend/vbd/3/2049/hotplug-status. /var/log/xen/syslog ------------------------- Mar 7 16:18:47 virtualx logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/4/2050 Mar 7 16:18:48 virtualx logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/4/2050 Mar 7 16:19:06 virtualx logger: /etc/xen/scripts/block: Forced to steal lock on /var/run/xen-hotplug/block from 18525: /etc/xen/scripts/block! Mar 7 16:19:06 virtualx logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/4/2049 Mar 7 16:19:06 virtualx logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/4/2049 Mar 7 16:20:41 virtualx logger: /etc/xen/scripts/xen-hotplug-cleanup: Forced to steal lock on /var/run/xen-hotplug/block from 18518: /etc/xen/scripts/block!Mar 7 16:20:42 virtualx logger: /etc/xen/scripts/xen-hotplug-cleanup: Forced to steal lock on /var/run/xen-hotplug/block from unknown! /var/log/xen/xen-hotplug.log ------------------------------------------- Nothing to flush. stat: cannot stat `/dev/lvm/VM1-disk'': Not a directory stat: cannot stat `/dev/lvm/VM1-disk'': Not a directory stat: cannot stat `/dev/lvm/VM1-swap'': Not a directory stat: cannot stat `/dev/lvm/VM1-swap'': Not a directory stat: cannot stat `/dev/lvm/VM1-disk'': Not a directory stat: cannot stat `/dev/lvm/VM1-disk'': Not a directory So where''s the problem? I don"t really understand the messages in logs. Is there a problem with bridge? with logical volumes? I don''t think it''s the config file since it worked, and after reboot it stoped working ;) Some time ago, I had this problem with lvm disks, and not with images based domU. Strange... I''ve read all related messages in google and xen-users mailing list, and haven''t found a solution... Any help would be appreciated Thanks a lot! Jordi S On 3/1/07, Daniele Palumbo <daniele@retaggio.net> wrote:> On Thursday 22 February 2007 13:24, Fermín Galán Márquez wrote: > > tornado:~# xm create test.cfg -c > > Using config file "/etc/xen/test.cfg". > > Error: Device 2049 (vbd) could not be connected. Hotplug scripts not > > working. > > i have the same problem. > > now on: my setup is sightly different. > i have clvm, but this is always with local lv. > > sometimes mounting the volume and unmounting it can resolve the problem. > other times, it is resolved only by waiting one minute or two. > > i am suspecting something about ''sync'', but seems strange... > > logs cannot help at all (AFAIK). i am also curious about wtf is vbd 2049. > anyone else? > > bye > d. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jordi Segues
2007-Mar-09 15:17 UTC
Re: [Xen-users] Problem creating domU: "Device 2049 (vbd) could not be connected. Hotplug scripts not working."
Ok, I''ve found how to solve this. I''ve tried xm create with a loopback image and it worked perfectly. So I realized that the problem was not from the bridge, but from LVM. I forced the lvm cache rebuild after manually removing it. Here''s the commands: rm /dev/lvm vgscan --mknodes Reading all physical volumes. This may take a while... Found volume group "lvm" using metadata type lvm2 *where "lvm" is my volume group name. You can also try vgchange -ay So I hope it may help to someone else. Jordi Segues On 3/7/07, Jordi Segues <jordisd.mailing@gmail.com> wrote:> Hello, > > I have exactly the same problem: > > xm create /etc/xen/VM1.cfg > Using config file "/etc/xen/VM1.cfg". > > Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working > > I use LVM partitions for the disk. > > There''s my VM1.cfg: > > kernel = ''/boot/vmlinuz-2.6.18-4-xen-686'' > ramdisk = ''/boot/initrd.img-2.6.18-4-xen-686'' > memory = ''128'' > root = ''/dev/sda1 ro'' > disk = [ ''phy:lvm/VM1-disk,sda1,w'', ''phy:lvm/VM1-swap,sda2,w'' ] > name = ''VM1'' > vif = [ ''ip=172.16.100.202'' ] > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > > And that''s what logs say: > > /var/log/xen/xend.log > -------------------------------------- > > [2007-03-07 16:17:22 xend.XendDomainInfo 16300] DEBUG (__init__:1072) > XendDomainInfo.handleShutdownWatch > [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) Waiting for devices vif. > [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) Waiting for devices usb. > [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) Waiting for devices vbd. > [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) Waiting for 2049. > [2007-03-07 16:17:22 xend 16300] DEBUG (__init__:1072) > hotplugStatusCallback > /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2007-03-07 16:17:30 xend 16300] DEBUG (__init__:1072) > hotplugStatusCallback > /local/domain/0/backend/vbd/3/2049/hotplug-status. > [2007-03-07 16:17:30 xend 16300] DEBUG (__init__:1072) > hotplugStatusCallback > /local/domain/0/backend/vbd/3/2049/hotplug-status. > [2007-03-07 16:18:47 xend.XendDomainInfo 16300] DEBUG (__init__:1072) > XendDomainInfo.destroy: domid=4 > [2007-03-07 16:18:47 xend.XendDomainInfo 16300] DEBUG (__init__:1072) > XendDomainInfo.destroyDomain(4) > [2007-03-07 16:20:42 xend 16300] DEBUG (__init__:1072) > hotplugStatusCallback > /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2007-03-07 16:20:42 xend 16300] DEBUG (__init__:1072) > hotplugStatusCallback > /local/domain/0/backend/vbd/4/2049/hotplug-status. > [2007-03-07 16:20:42 xend 16300] DEBUG (__init__:1072) > hotplugStatusCallback > /local/domain/0/backend/vbd/3/2049/hotplug-status. > > /var/log/xen/syslog > ------------------------- > > Mar 7 16:18:47 virtualx logger: /etc/xen/scripts/block: remove > XENBUS_PATH=backend/vbd/4/2050 > Mar 7 16:18:48 virtualx logger: /etc/xen/scripts/xen-hotplug-cleanup: > XENBUS_PATH=backend/vbd/4/2050 > Mar 7 16:19:06 virtualx logger: /etc/xen/scripts/block: Forced to > steal lock on /var/run/xen-hotplug/block from 18525: > /etc/xen/scripts/block! > Mar 7 16:19:06 virtualx logger: /etc/xen/scripts/block: remove > XENBUS_PATH=backend/vbd/4/2049 > Mar 7 16:19:06 virtualx logger: /etc/xen/scripts/xen-hotplug-cleanup: > XENBUS_PATH=backend/vbd/4/2049 > Mar 7 16:20:41 virtualx logger: /etc/xen/scripts/xen-hotplug-cleanup: > Forced to steal lock on /var/run/xen-hotplug/block from 18518: > /etc/xen/scripts/block!Mar 7 16:20:42 virtualx logger: > /etc/xen/scripts/xen-hotplug-cleanup: Forced to steal lock on > /var/run/xen-hotplug/block from unknown! > > /var/log/xen/xen-hotplug.log > ------------------------------------------- > > Nothing to flush. > stat: cannot stat `/dev/lvm/VM1-disk'': Not a directory > stat: cannot stat `/dev/lvm/VM1-disk'': Not a directory > stat: cannot stat `/dev/lvm/VM1-swap'': Not a directory > stat: cannot stat `/dev/lvm/VM1-swap'': Not a directory > stat: cannot stat `/dev/lvm/VM1-disk'': Not a directory > stat: cannot stat `/dev/lvm/VM1-disk'': Not a directory > > > So where''s the problem? > I don"t really understand the messages in logs. > > Is there a problem with bridge? with logical volumes? > I don''t think it''s the config file since it worked, and after reboot > it stoped working ;) > > Some time ago, I had this problem with lvm disks, and not with images > based domU. > Strange... > > I''ve read all related messages in google and xen-users mailing list, > and haven''t found a solution... > Any help would be appreciated > > Thanks a lot! > > Jordi S > > On 3/1/07, Daniele Palumbo <daniele@retaggio.net> wrote: > > On Thursday 22 February 2007 13:24, Fermín Galán Márquez wrote: > > > tornado:~# xm create test.cfg -c > > > Using config file "/etc/xen/test.cfg". > > > Error: Device 2049 (vbd) could not be connected. Hotplug scripts not > > > working. > > > > i have the same problem. > > > > now on: my setup is sightly different. > > i have clvm, but this is always with local lv. > > > > sometimes mounting the volume and unmounting it can resolve the problem. > > other times, it is resolved only by waiting one minute or two. > > > > i am suspecting something about ''sync'', but seems strange... > > > > logs cannot help at all (AFAIK). i am also curious about wtf is vbd 2049. > > anyone else? > > > > bye > > d. > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users