[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Driver/Backend Domains

Forgot to mention - I also put the option "blkif=1" in the configuration file for the intended driver domain.
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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.