[10:49] hws, hello [16:47] rharper, hey - have 5 mins to help me debug a libvirt/qemu problem? [16:47] sure [16:48] rharper, ok - so I nearly have instances booting under openstack - they do the normal startup -> paused whilst the networking is all being setup... [16:48] but then nova unpauses them and they just go straight to shutdown - not quite sure how to debug what's going on [16:49] that's nova state saying shutdown ? [16:49] versus actual console log ? [16:49] rharper, no that virsh list --all [16:49] libvirt will always start the guest in stop mode (-S); then when all devices are attached, libvirt will send the cont signal to start the qemu machine [16:49] nova reflects that once it notices it [16:50] rharper, so I see [16:50] - instance-00000006 shut off [16:50] type stuff from virsh [16:50] do we have the machine qemu.log file ? [16:51] rharper, the qemu log file for the instance - 2016-04-08T16:42:22.595065Z qemu-system-s390x: terminating on signal 15 from pid 260989 [16:51] that's likely to have info on why libvirt wants to shut it down [16:51] ah [16:51] rharper, http://paste.ubuntu.com/15692628/ [16:51] i bet it's misconfigured and qemu is aborting [16:51] can you enable libvirtd debugging and get a log from there? [16:52] rharper, I have the daemon running with the -v flag [16:52] lemme get you a decent log config for libvirtd (less you have the qemu exec bits in our output) [16:53] is that paste from your debug output or the instance.log file from var/lib/libvirt/qemu/$machine_instance.log [16:53] I'm looking to see if qemu spit anything out on stderr [16:55] rharper, from the instance log file [16:55] hrm, ok [16:56] jamespage: I'm playing with the command line invoccation on another s390x box to see what qemu says; [16:57] rharper, okies - I can give you access to this one if you like [16:57] sure