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] Error: Device 2049 (vbd) could not be connected. Hotplug scr

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working
From: Vinogratzky <vinogratzky@xxxxxx>
Date: Tue, 16 Jun 2009 14:33:27 +0200
Delivery-date: Tue, 16 Jun 2009 05:34:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: vinogratzky@xxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Contiki/1.0 (Commodore 64)
Hi,

have a debian 5.0 with all patches and xen 4.3.1 (debian repo)
installed. If I use a VM with paravirtualizing it works fine.
But a full virtualized image doesn't boot.

Message:
---8<---
# xm create deb50.cfg:
Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working.
---8<---

That is my deb50.cfg
---8<---
# Debian 5.0
import os, re
arch = os.uname()[4]
if re.search('64', arch):
        arch_libdir = 'lib64'
else:
        arch_libdir = 'lib'
kernel = "/usr/lib/xen-3.2-1/boot/hvmloader"
device_model = '/usr/lib/xen-3.2-1/bin/qemu-dm'
builder = 'hvm'

name = "deb50"
memory = 256
disk        = [
                  'phy:/dev/vol_xen/vm6-swap,sda1,w',
                  'phy:/dev/vol_xen/vm6-disk,sda2,w',
                'file:/share/data1/iso/debian_i386_5.0.iso,sdc:cdrom,r',
              ]
boot = 'd'
vif = [ 'type=ioemu' ]

on_poweroff = 'destroy'
on_reboot   = 'destroy'
on_crash    = 'destroy'

sdl = 1
vnc = 0
vncviewer = 0

extra= "role=udev" #  clocksource=jiffies independent_wallclock=1"
---8<---

After xm create:
---8<---
# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  1496     2     r-----     28.5
deb50                                        3   256     1     --p---      0.0
vm3                                          1   256     1     -b----      2.8
---8<---

but the console doesn't work:
---8<---
# xm console deb50
xenconsole: Could not read tty from store: No such file or directory
---8<---

CPU: Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz
If I boot a non xen-kernel, I get the "vmx" cpu flag.


Google didn't help me either.

syslog:
---8<---
Jun 15 09:30:28 debian init: Id "x0" respawning too fast: disabled for 5 minutes
Jun 15 09:30:28 debian logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/4/2050
Jun 15 09:30:28 debian logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/4/2049
Jun 15 09:30:28 debian logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/4/2080
Jun 15 09:30:29 debian logger: /etc/xen/scripts/vif-bridge: online 
XENBUS_PATH=backend/vif/4/0
Jun 15 09:30:29 debian logger: /etc/xen/scripts/block: Writing 
backend/vbd/4/2050/physical-device fe:2 to xenstore.
Jun 15 09:30:29 debian logger: /etc/xen/scripts/block: Writing 
backend/vbd/4/2050/hotplug-status connected to xenstore.
Jun 15 09:30:29 debian kernel: [  968.121845] device vif4.0 entered promiscuous 
mode
Jun 15 09:30:29 debian kernel: [  968.123411] eth0: port 3(vif4.0) entering 
learning state
Jun 15 09:30:29 debian kernel: [  968.123496] eth0: topology change detected, 
propagating
Jun 15 09:30:29 debian kernel: [  968.123568] eth0: port 3(vif4.0) entering 
forwarding state
Jun 15 09:30:29 debian logger: /etc/xen/scripts/vif-bridge: Successful 
vif-bridge online for vif4.0, bridge eth0.
Jun 15 09:30:29 debian logger: /etc/xen/scripts/vif-bridge: Writing 
backend/vif/4/0/hotplug-status connected to xenstore.
Jun 15 09:30:39 debian kernel: [  978.465844] vif4.0: no IPv6 routers present
Jun 15 09:32:03 debian logger: /etc/xen/scripts/block: Forced to steal lock on 
/var/run/xen-hotplug/block from 10591: /etc/xen/scripts/block!
Jun 15 09:32:04 debian logger: /etc/xen/scripts/block: Writing 
backend/vbd/4/2080/node /dev/loop10 to xenstore.
Jun 15 09:32:04 debian logger: /etc/xen/scripts/block: Writing 
backend/vbd/4/2080/physical-device 7:a to xenstore.
Jun 15 09:32:04 debian logger: /etc/xen/scripts/block: Writing 
backend/vbd/4/2080/hotplug-status connected to xenstore.
Jun 15 09:32:09 debian logger: /etc/xen/scripts/xen-hotplug-cleanup: 
XENBUS_PATH=backend/console/4/0
Jun 15 09:32:09 debian logger: /etc/xen/scripts/block: remove 
XENBUS_PATH=backend/vbd/4/2050
Jun 15 09:32:09 debian logger: /etc/xen/scripts/block: remove 
XENBUS_PATH=backend/vbd/4/2080
Jun 15 09:32:09 debian kernel: [ 1068.419783] eth0: port 3(vif4.0) entering 
disabled state
Jun 15 09:32:09 debian logger: /etc/xen/scripts/block: remove 
XENBUS_PATH=backend/vbd/4/2049
Jun 15 09:32:09 debian logger: /etc/xen/scripts/vif-bridge: offline 
XENBUS_PATH=backend/vif/4/0
Jun 15 09:32:09 debian kernel: [ 1068.447920] eth0: port 3(vif4.0) entering 
disabled state
Jun 15 09:32:09 debian logger: /etc/xen/scripts/xen-hotplug-cleanup: 
XENBUS_PATH=backend/vbd/4/2050
Jun 15 09:32:09 debian logger: /etc/xen/scripts/xen-hotplug-cleanup: 
XENBUS_PATH=backend/vbd/4/2049
Jun 15 09:32:09 debian logger: /etc/xen/scripts/xen-hotplug-cleanup: 
XENBUS_PATH=backend/vbd/4/2080
Jun 15 09:32:09 debian logger: /etc/xen/scripts/vif-bridge: brctl delif eth0 
vif4.0 failed
Jun 15 09:32:09 debian logger: /etc/xen/scripts/vif-bridge: ifconfig vif4.0 
down failed
Jun 15 09:32:09 debian logger: /etc/xen/scripts/vif-bridge: Successful 
vif-bridge offline for vif4.0, bridge eth0.
Jun 15 09:32:09 debian logger: /etc/xen/scripts/xen-hotplug-cleanup: 
XENBUS_PATH=backend/vif/4/0
---8<---

What am i doning wrong here?
Txs,
Chris

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working, Vinogratzky <=