[libvirt] Segmentation fault when shutting down VMs
Hi, I'm facing another problem with latest git. This happens regularly when shutting down VM(s): http://pastebin.com/m4ef1d93f It doesn't depend on which or how many VM is/are shut down, or if I have a VNC connection to a VM that is shutting down. Sometimes after a segv, I get this: http://pastebin.com/m5260bf21 It seems to me that libvirt tries to query a qemu monitor that is no longer alive? kr,tom
On Fri, Nov 13, 2009 at 11:42:46AM +0100, Thomas Treutner wrote:
Hi,
I'm facing another problem with latest git.
This happens regularly when shutting down VM(s):
It doesn't depend on which or how many VM is/are shut down, or if I have a VNC connection to a VM that is shutting down. Sometimes after a segv, I get this:
It seems to me that libvirt tries to query a qemu monitor that is no longer alive?
This second problem is fixed by http://www.redhat.com/archives/libvir-list/2009-November/msg00458.html I'm still trying to figure out what's going on with the first problem Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
On Friday 13 November 2009 12:46:24 Daniel P. Berrange wrote:
I'm still trying to figure out what's going on with the first problem
Uhm, it's getting stranger. When trying to do: # export LIBVIRT_DEBUG=1 # strace -o libvirt.log -s 1000 -ff libvirtd -l -v strace crashes with: *** glibc detected *** strace: malloc(): memory corruption (fast): 0x0000000000af75b0 *** during startup, although /usr/local/var/run/libvirt/qemu/ is wiped out and no stale pids or kvms running. http://pastebin.com/m45c03cfb strace's logs until crash: http://tt.scripty.at/tmp/glibc_mem_corrupt.log.tar.bz2 Time for doing a memtest? -t
On Friday 13 November 2009 12:46:24 Daniel P. Berrange wrote:
On Fri, Nov 13, 2009 at 11:42:46AM +0100, Thomas Treutner wrote:
Hi,
I'm facing another problem with latest git.
This happens regularly when shutting down VM(s):
It doesn't depend on which or how many VM is/are shut down, or if I have a VNC connection to a VM that is shutting down. Sometimes after a segv, I get this:
It seems to me that libvirt tries to query a qemu monitor that is no longer alive?
This second problem is fixed by
http://www.redhat.com/archives/libvir-list/2009-November/msg00458.html
I'm still trying to figure out what's going on with the first problem
I found some time to pull latest git, build, and test a little bit today, and it seems to me that the problem has vanished away! -t
2009/12/10 Thomas Treutner <thomas@scripty.at>:
On Friday 13 November 2009 12:46:24 Daniel P. Berrange wrote:
On Fri, Nov 13, 2009 at 11:42:46AM +0100, Thomas Treutner wrote:
Hi,
I'm facing another problem with latest git.
This happens regularly when shutting down VM(s):
It doesn't depend on which or how many VM is/are shut down, or if I have a VNC connection to a VM that is shutting down. Sometimes after a segv, I get this:
It seems to me that libvirt tries to query a qemu monitor that is no longer alive?
This second problem is fixed by
http://www.redhat.com/archives/libvir-list/2009-November/msg00458.html
I'm still trying to figure out what's going on with the first problem
I found some time to pull latest git, build, and test a little bit today, and it seems to me that the problem has vanished away!
-t
The problem has been fixed by the combination of this two commits: http://libvirt.org/git/?p=libvirt.git;a=commit;h=79533da1b36cc16e0f3f8aea798... http://libvirt.org/git/?p=libvirt.git;a=commit;h=8e7d14953ca6ef047112bc6ac17... Matthias
participants (3)
-
Daniel P. Berrange -
Matthias Bolte -
Thomas Treutner