search for: virprocesskillpain

Displaying 4 results from an estimated 4 matches for "virprocesskillpain".

2014 Feb 08
1
Failed to terminate process X with SIGKILL: Device or resource busy
...evice or resource busy # lsof -p 61222 # ps -f -p 61222 UID PID PPID C STIME TTY TIME CMD 107 61222 1 68 Jan24 ? 9-23:06:19 [qemu-system-x86] <defunct> The log in /var/log/libvirt/libvirtd.log: 2014-02-08 03:21:31.597+0000: 2177: error : virProcessKillPainfully:315 : Failed to terminate process 61222 with SIGKILL: Device or resource busy Restart libvirt-bin service did not solve the problem. virsh shutdown/reboot just hang. Maybe that is because the CPU in vm is stalled. I wonder if there is some way to destroy (or rebuild) dead instance without r...
2015 Apr 21
2
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
...info : virObjectUnref:259 : OBJECT_UNREF: obj=0x7fb8d0000bd0 2015-04-20 23:50:20.387+0000: 25373: debug : qemuProcessKill:5047 : vm=0x7fb8cc0d8510 name=test pid=25245 flags=5 2015-04-20 23:50:20.387+0000: 25373: debug : virProcessKillPainfully:352 : vpid=25245 force=1 2015-04-20 23:50:20.387+0000: 25298: debug : virEventPollRunOnce:650 : Poll got 2 event(s) 2015-04-20 23:50:20.387+0000: 25298: debug : virEventPollDispatchTimeou...
2015 Apr 21
0
Re: QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
...d I notice that is called in a couple places related to snapshot create and revert which you mentioned in the original message. Since this isn't normal behavior, and the snapshot stuff is under active development, I wonder if this is related...) > 2015-04-20 23:50:20.387+0000: 25373: debug : virProcessKillPainfully:352 > : vpid=25245 force=1 > 2015-04-20 23:50:20.387+0000: 25298: debug : virEventPollRunOnce:650 : > Poll got 2 event(s) > 2015-04-20 23:50:20.387+0000: 25298: debug : > v...
2015 Apr 21
2
QemuDomainObjEndJob called when libvirtd is started and libvirt insists qemu is using the wrong disk source.
List, I was under the impression that I could restart libvirtd without it destroying my VMs, but am not finding that to be true. When I killall libvirtd then my VM's keep running, but then when I start libvirtd it calls qemuDomainObjEndJob:1542 : Stopping job: modify (async=none vm=0x7fb8cc0d8510 name=test) and my domain gets whacked. Any way to disable this behavior? Also, while I'm