Re: [Xen-users] Problem creating domU: "Device 2049 (vbd) could not be connected. Hotplug scripts not working."

["Jordi Segues" <jordisd.mailing@xxxxxxxxx>]

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@xxxxxxxxx> 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@xxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users