On 14.10.2013 17:38, Francois Gaudreault wrote: > Hi Michal, > > Looking in the logs, it looks like the libvirt process sent a sigkill to > the qemu process: > 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerAcquire:358 : > lock=0x7f6bc80de170 state='(null)' flags=3 action=0 fd=0x7f6bdf3bf074 > 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerFree:395 : > lock=0x7f6bc80de170 > 2013-10-11 19:59:22.132+0000: 10212: debug : virObjectUnref:256 : > OBJECT_UNREF: obj=0x7f6bd000f890 > 2013-10-11 19:59:22.132+0000: 10212: debug : qemuProcessHook:2573 : Hook > complete ret=0 > 2013-10-11 19:59:22.132+0000: 10212: debug : virExec:632 : Done hook 0 > 2013-10-11 19:59:22.132+0000: 10212: debug : virExec:669 : Setting child > uid:gid to 108:115 with caps 0 > 2013-10-11 19:59:22.132+0000: 10212: debug : > virCommandHandshakeChild:360 : Notifying parent for handshake start on 37 > 2013-10-11 19:59:22.132+0000: 10212: debug : > virCommandHandshakeChild:368 : Waiting on parent for handshake complete > on 38 > 2013-10-11 19:59:22.137+0000: 10212: debug : virFileClose:90 : Closed fd 37 > 2013-10-11 19:59:22.137+0000: 10212: debug : virFileClose:90 : Closed fd 38 > 2013-10-11 19:59:22.137+0000: 10212: debug : > virCommandHandshakeChild:388 : Handshake with parent is done > W: kvm binary is deprecated, please use qemu-system-x86_64 instead > char device redirected to /dev/pts/3 (label charserial0) > qemu: terminating on signal 15 from pid 1437 > 2013-10-11 20:00:26.427+0000: shutting down > > ps output: > 1437 ? Sl 0:15 /usr/sbin/libvirtd -d -l > > Any way to troubleshoot deeper? > Well, what says the libvirtd.log then? http://wiki.libvirt.org/page/DebugLogs Michal _______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
