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

Re: [Xen-devel] [TESTDAY] Test report

Hi Ian and Roger,

   thank you for your help.

On 30.10.2014 15:39, Ian Campbell wrote:
On Thu, 2014-10-30 at 11:54 +0100, Jan Vejvalka wrote:
Won't boot windows over iSCSI (not new in 4.5), says in
qemu-system-i386: -drive
could not open disk image portal=(IP):3260: Unknown protocol

What xl.cfg syntax did you use for this disk?

I'm not seeing the file=portal=(IP):3260 syntax in the qemu manpage,
where did it come from?

This is what I have in PV guest config (and it works fine):
disk = [ 'script=block-iscsi,vdev=xvda1,target=portal=(IP):3260,iqn=(iqn),w' ] ... so I put the same in the HVM guest config (just substituting hda for xvda1).
If I use iscsiadm to map the iscsi drive locally and then I put
disk = [ 'phy:/dev/sdf,hda,w' ]
in my guest config, it works.

One of the examples given in the qemu docs is:
         -drive file=iscsi://
which I would expect to correspond to an xl.cfg disk spec line which

Sorry to ask further... how should it begin ?
I tried several variants, e.g.
disk = [ 'vdev=hda,target=file=iscsi://(IP):3260/(iqn)' ], but then
I get
libxl: error: libxl_device.c:283:libxl__device_disk_set_backend: Disk vdev=hda failed to stat: file=iscsi://(IP):3260/(iqn): No such file or directory.

On 30.10.2014 15:58, Roger Pau Monnà wrote:
> If you want to use iSCSI disks with an HVM domain you should use a
> stubdomain. Adding the following to your config file should solve it:
> device_model_stubdomain_override=1

Did not. Using that and the 'original'
disk = [ 'script=block-iscsi,vdev=hda,target=portal=(IP):3260,iqn=(iqn),w'],
I get

Parsing config from xen/w7c.xenconf
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block-iscsi add [-1] exited with error status 1 libxl: error: libxl_device.c:1078:device_hotplug_child_death_cb: script: Device already opened libxl: error: libxl_dm.c:1118:spawn_stub_launch_dm: error connecting disk devices libxl: error: libxl_dm.c:1233:stubdom_pvqemu_cb: error connecting nics devices: Interrupted system call

on the console and

Waiting for domain example.hvm (domid 30) to die [pid 6556]
Domain 30 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 30 needs to be cleaned up: destroying the domain
libxl: error: libxl.c:1542:libxl__destroy_domid: non-existant domain 31
libxl: error: libxl.c:1480:stubdom_destroy_callback: unable to destroy stubdom with domid 31 libxl: error: libxl_aoutils.c:464:async_exec_timeout: killing execution of /etc/xen/scripts/block-iscsi remove because of timeout libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block-iscsi remove [-1] died due to fatal signal Killed libxl: error: libxl.c:1433:domain_destroy_cb: destruction of domain 30 failed
Done. Exiting now

in /var/log/xen/xl-example.hvm.log.

Grateful for any further advice,


Xen-devel mailing list



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