search for: qemuprocessstop

...txt but the backtrace is simply: Breakpoint 1, 0x00007fffc72a0240 in qemuProcessKill () from /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so (gdb) bt #0 0x00007fffc72a0240 in qemuProcessKill () from /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so #1 0x00007fffc72a19cd in qemuProcessStop () from /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so #2 0x00007fffc72a27d6 in ?? () from /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so #3 0x00007ffff74b6882 in ?? () from /usr/lib64/libvirt.so.0 #4 0x00007ffff5722ce2 in start_thread () from /lib64/libpthread.so.0 #5...

...> info about where it is coming from. > > Oh, by the way, are these perhaps transient domains started with > virDomainCreate*? Or are they standard persistent domains defined with > virDomainDefineXML? > > (Also, I'll just mention that qemuProcessKill() is called from > qemuProcessStop(), and 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...) Laine, First, thanks for yo...

...> > Breakpoint 1, 0x00007fffc72a0240 in qemuProcessKill () from > /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so > (gdb) bt > #0 0x00007fffc72a0240 in qemuProcessKill () from > /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so > #1 0x00007fffc72a19cd in qemuProcessStop () from > /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so > #2 0x00007fffc72a27d6 in ?? () from > /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so > #3 0x00007ffff74b6882 in ?? () from /usr/lib64/libvirt.so.0 > #4 0x00007ffff5722ce2 in start_thread () from /...

...debug : qemuDomainObjEndJob:1542 : Stopping job: modify (async=none vm=0x7fb8cc0d8510 name=test) 2015-04-20 23:50:20.387+0000: 25373: info : virObjectRef:296 : OBJECT_REF: obj=0x7fb8cc0155b0 2015-04-20 23:50:20.387+0000: 25373: debug : qemuProcessStop:5089 : Shutting down vm=0x7fb8cc0d8510 name=test id=6 pid=25245 flags=0 2015-04-20 23:50:20.387+0000: 25373: info : virObjectRef:296 : OBJECT_REF: obj=0x7fb8cc0155b0 2015-04-20 23:50:20.387+0000: 25373: info : virObjectUnref:259 : OBJ...

On 04/28/2015 05:13 PM, Laine Stump wrote: > Bah. Your debug symbols aren't enough to give a full stack trace - what > I was really looking for was those things marked as ??. > > However, your debug output shows several things leading up tothe > qemuProcessStop that might have been the reason for it being called: > > 1) virStorageFileBackendFileReadHeader() complains that there is no > medium in /dev/sr0 (i.e. no disk in the CD drive) (this was actually in > your much more abbreviated log in an earlier message, but for some > reason I skip...

...t/qemu/p1p1_vf0': No such file or directory Oct 15 15:25:48 dcswitch85 libvirtd[17709]: 2012-10-15 22:25:48.146+0000: 17713: error : qemuRemoveCgroup:740 : internal error Unable to find cgroup for exp85-1 Oct 15 15:25:48 dcswitch85 libvirtd[17709]: 2012-10-15 22:25:48.146+0000: 17713: warning : qemuProcessStop:4136 : Failed to remove cgroup for exp85-1 I was wondering if anyone else has faced this problem or has a solution to this. I'm using Fedora17, KVM, and an 82599EB Intel NIC. Thanks much in advance. With best regards Radhika -------------- next part -------------- An HTML attachment was scr...

...ob:1542 : > Stopping job: modify (async=none vm=0x7fb8cc0d8510 name=test) > 2015-04-20 23:50:20.387+0000: 25373: info : virObjectRef:296 : > OBJECT_REF: > obj=0x7fb8cc0155b0 > 2015-04-20 23:50:20.387+0000: 25373: debug : qemuProcessStop:5089 : > Shutting down vm=0x7fb8cc0d8510 name=test id=6 pid=25245 > flags=0 > 2015-04-20 23:50:20.387+0000: 25373: info : virObjectRef:296 : > OBJECT_REF: > obj=0x7fb8cc0155b0 > 2015-04-20 23:50:20.387+0000: 25373: i...

...coming from. >> >> Oh, by the way, are these perhaps transient domains started with >> virDomainCreate*? Or are they standard persistent domains defined with >> virDomainDefineXML? >> >> (Also, I'll just mention that qemuProcessKill() is called from >> qemuProcessStop(), and 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...) > Laine, >...

...not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules. Aug 27 13:28:35 localhost libvirtd: 9937: error : qemuRemoveCgroup:768 : internal error Unable to find cgroup for one-8 Aug 27 13:28:35 localhost libvirtd: 9937: warning : qemuProcessStop:4349 : Failed to remove cgroup for one-8 - On XCP hypervisor: [root at xenserver2 ~]# egrep '(vmx|svm)' --color=always /proc/cpuinfo flags: fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc aperfmperf pni vmx est ssse3 ss...

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