Re: [Xen-users] storage driver domains

[Kuba <kuba.0000@xxxxx>]

W dniu 2014-07-25 13:44, Roger Pau Monnà pisze:
> On 25/07/14 12:56, Kuba wrote:
> > Dear List,
> >
> > is the storage driver domain idea still alive? I'm particularly
> > interested in a combination where HVM/PVHVM DomUs (FreeBSD, Linux)
> > provide storage to other HVM/PVHVM DomUs (Linux, Windows). I can't find
> > any recent information about it. I would be very grateful for any
> > pointers or clues.
> Hello,
>
> There's a wikipage that contains the information need in order to setup
> storage driver domains for both FreeBSD and Linux:
>
> http://wiki.xen.org/wiki/Storage_driver_domains
>
> If you want to use driver domains to provide disks to HVM/PVHVM guests
> you will have to use qemu stubdomains, since Qemu needs access to the
> disk in order to boot the domain.
>
> Roger.
Thank you for your help, but unfortunately I cannot get it to work (Xen
4.4 compiled from sources with Debian 7 Dom0 with kernel 3.10.33). I'm
trying to provide storage from one FreeBSD 10 DomU (provider.conf) to
another FreeBSD 10 DomU (consumer.conf). I boot provider DomU in livecd
mode and create a zvol (tank/test). Long story short, I can get consumer
DomU's kernel to see the storage (when booted in livecd mode), but
cannot get the bios to see it too (and boot from it).

When I try to boot consumer DomU with this in consumer.conf:

#device_model_version="qemu-xen-traditional"
device_model_stubdomain_override=0
disk=[
'format=raw,backendtype=phy,backend=provider,vdev=xvdb,target=/dev/zvol/tank/test',
'file:/root/fbsd.iso,xvda,r,devtype=cdrom'
]
boot='d'

I get:

# xl create consumer.conf
Parsing config from consumer.conf
libxl: error: libxl_dm.c:1371:device_model_spawn_outcome: domain 47
device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1186:domcreate_devmodel_started: device
model did not start: -3
libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already exited
libxl: error: libxl_device.c:1115:device_destroy_be_timeout_cb: timed
out while waiting for /local/domain/31/backend/vbd/47/51728 to be removed
libxl: error: libxl.c:1457:devices_destroy_cb: libxl__devices_destroy
failed for 47


And in qemu-dm-consumer.log:
qemu-system-i386: -drive
file=/dev/zvol/tank/test,if=ide,index=1,media=disk,format=raw,cache=writeback:
could not open disk image /dev/zvol/tank/test: No such file or directory


But when I use a stubdomain:

#device_model_version="qemu-xen-traditional"
device_model_stubdomain_override=1

consumer DomU boots fine and I see /dev/xbd1 properly (and I'm sure its
the tank/test zvol from provider DomU). However qemu-dm-consumer.log
contains:

frontend `/local/domain/49/device/vbd/51728' devtype `vbd' expected
backend `/local/domain/0/backend/qdisk/49/51728' got
`/local/domain/31/backend/vbd/49/51728', ignoring
frontend `/local/domain/49/device/vbd/51728' devtype `vbd' expected
backend `/local/domain/0/backend/qdisk/49/51728' got
`/local/domain/31/backend/vbd/49/51728', ignoring

I can also install FreeBSD just fine, but I cannot get it to boot. With
boot='c' no combination of device_model_version and
device_model_stubdomain_override makes consumer DomU's bios detect the
zvol and boot from it.

I'm sure I'm missing something, but I can't figure it out. I'd be very
grateful for any ideas.

Best regards,
Kuba

Attachment: consumer.conf
Description: Text document

Attachment: provider.conf
Description: Text document

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users