WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Problem creating domU: "Device 2049 (vbd) could not be conne

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Problem creating domU: "Device 2049 (vbd) could not be connected. Hotplug scripts not working."
From: Fermín Galán Márquez <fermin.galan@xxxxxxx>
Date: Thu, 22 Feb 2007 13:24:10 +0100
Delivery-date: Thu, 22 Feb 2007 04:24:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdWfFoM2YRdCGUnTYeTetPLhhimjQ==
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Problem creating domU: "Device 2049 (vbd) could not be connected. Hotplug scripts not working.", Fermín Galán Márquez <=