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/
Home Products Support Community News


[Xen-users] Driver/Backend Domains

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Driver/Backend Domains
From: Matthew Mallozzi <matt.mallozzi@xxxxxxxxxx>
Date: Thu, 02 Jul 2009 16:00:07 -0700
Delivery-date: Mon, 06 Jul 2009 07:49:58 -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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090608)
What is required for a PV domU to act as a driver domain for a block device? My goal is to attach a disk image file located within the domU to dom0 as a block device. The command I am running in dom0 is
   xm block-attach 0 file:/root/hdisk.img /dev/xvdb w 2,
where hdisk.img is the disk image file in domU, xvdb is the name of the intended device node in dom0, and 2 is the domain ID of the domU.

My domU is a PV guest with its kernel replaced by the kernel from dom0, and I have copied over both /etc/xen/scripts and /usr/lib/python2.4/site-packages/xen from dom0 to the guest. However, whenever I attempt the above command, it sits for a while and then returns with "Error: Device 51744 (vbd) could not be connected. Hotplug scripts not working.", which is quite vague.

Thank you!

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>