Re: [Xen-devel] block-iscsi with Xen 4.5 / 4.6

[Roger Pau Monné <roger.pau@xxxxxxxxxx>]

On Fri, Apr 15, 2016 at 06:20:56PM +1000, Steven Haigh wrote:
[...]
> I might have spoken too soon here... I updated this system to 4.6.1 and
> created the DomU again - still seems to fail - although it does actually
> call the block-iscsi script this time:
> 
> # xl -vvv create /etc/xen/test1.vm
> Parsing config from /etc/xen/test1.vm
> libxl: debug: libxl_create.c:1560:do_domain_create: ao 0x24ad330: create:
> how=(nil) callback=(nil) poller=0x24b7070
> libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
> vdev=xvda spec.backend=unknown
> libxl: debug: libxl_device.c:207:disk_try_backend: Disk vdev=xvda, uses
> script=... assuming phy backend
> libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk
> vdev=xvda, using backend phy
> libxl: debug: libxl_create.c:945:initiate_domain_create: running bootloader
> libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
> vdev=(null) spec.backend=phy
> libxl: debug: libxl_device.c:207:disk_try_backend: Disk vdev=(null), uses
> script=... assuming phy backend
> libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk
> vdev=xvde spec.backend=phy
> libxl: debug: libxl_device.c:207:disk_try_backend: Disk vdev=xvde, uses
> script=... assuming phy backend
> libxl: debug: libxl_event.c:639:libxl__ev_xswatch_register: watch
> w=0x24ada00 wpath=/local/domain/0/backend/vbd/0/51776/state token=3/0:
> register slotnum=3
> libxl: debug: libxl_create.c:1583:do_domain_create: ao 0x24ad330:
> inprogress: poller=0x24b7070, flags=i
> libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0x24ada00
> wpath=/local/domain/0/backend/vbd/0/51776/state token=3/0: event
> epath=/local/domain/0/backend/vbd/0/51776/state
> libxl: debug: libxl_event.c:884:devstate_callback: backend
> /local/domain/0/backend/vbd/0/51776/state wanted state 2 still waiting state
> 1
> libxl: debug: libxl_event.c:576:watchfd_callback: watch w=0x24ada00
> wpath=/local/domain/0/backend/vbd/0/51776/state token=3/0: event
> epath=/local/domain/0/backend/vbd/0/51776/state
> libxl: debug: libxl_event.c:880:devstate_callback: backend
> /local/domain/0/backend/vbd/0/51776/state wanted state 2 ok
> libxl: debug: libxl_event.c:677:libxl__ev_xswatch_deregister: watch
> w=0x24ada00 wpath=/local/domain/0/backend/vbd/0/51776/state token=3/0:
> deregister slotnum=3
> libxl: debug: libxl_device.c:937:device_backend_callback: calling
> device_backend_cleanup
> libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
> w=0x24ada00: deregister unregistered
> libxl: debug: libxl_linux.c:229:libxl__hotplug_disk: Args and environment
> ready
> libxl: debug: libxl_device.c:1034:device_hotplug: calling hotplug script:
> /etc/xen/scripts/block-iscsi add
> libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to
> execute: /etc/xen/scripts/block-iscsi add
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
> /etc/xen/scripts/block-iscsi add [2126] exited with error status 1
> libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
> w=0x24adb00: deregister unregistered
> libxl: error: libxl_device.c:1084:device_hotplug_child_death_cb: script:
> Device already opened

The message indicates that you have this device already opened in this 
system, this is detected by the following check, that you can also run from 
a shell:

# iscsiadm -m session 2>&1 | grep -q "$iqn" && fatal "Device already opened"

You will have to perform a logout in order for the hotplug script to 
correctly attach it.

Roger.

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