[Xen-devel] Cleaning up qemu-xen with passed-through devices

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

When I pass through devices to a VM with qemu-xen, after I shut down
the VM, the log has the following errors:

Waiting for domain E0 (domid 2) to die [pid 2470]
Domain 2 has shut down, reason code 0 0x0
Action for shutdown reason code 0 is destroy
Domain 2 needs to be cleaned up: destroying the domain
libxl: error: libxl_qmp.c:448:qmp_next: Socket read error: Connection
reset by peer
libxl: error: libxl_qmp.c:706:libxl__qmp_initialize: Failed to connect to QMP
libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error:
Connection refused
libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error:
Connection refused
libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error:
Connection refused
libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error:
Connection refused
libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error:
Connection refused
libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error:
Connection refused
libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error:
Connection refused
libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already exited
Done. Exiting now

I don't see this if I don't have anything passed through; I also don't
see it with qemu-traditional.

The qmp messages appear to be from libxl__qmp_pci_del().

It looks like perhaps qemu is shutting down of its own accord before
libxl has taken the initiative to kill it?  The qemu log doesn't have
anything strange at the shutdown:

char device redirected to /dev/pts/5 (label serial0)
[00:05.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:05.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:05.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:05.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:05.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:05.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:05.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:09.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:09.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:09.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:09.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:09.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:09.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
[00:09.0] xen_pt_pci_config_access_check: Error: Failed to access
register with invalid access size alignment. (addr: 0x0e, len: 4)
xen be: qdisk-768: error: unknown operation (255)
xen be: qdisk-768: error: unknown operation (255)
xen be: qdisk-5632: initialise() failed
Issued domain 13 poweroff

Any ideas?

 -George

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