kvm crashed on precise - memory corruption

[Serge Hallyn]

Kvm on precise crashed while rebooting a quantal desktop guest. On console I saw:

Msg: 192
Msg: 192
*** glibc detected *** kvm: malloc(): memory corruption: 0x00007f1aab021ec0 ***

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: qemu-kvm 1.0+noroms-0ubuntu14.1
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Thu Sep 6 15:44:30 2012
KvmCmdLine:
 UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
 serge 4365 4364 9 725017 908976 0 14:58 pts/5 00:04:17 kvm -drive file=quantal-desk.img,if=virtio,cache=none -m 1024 -net nic,model=virtio -net tap,script=no,downscript=no,ifname=tap0 -vga cirrus -vnc :1
MachineType: Dell Inc. Vostro 1220
ProcEnviron:
 LANGUAGE=en_US:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-30-generic root=UUID=42cf5a74-4059-42ed-adf1-e89186f4750d ro quiet splash vt.handoff=7
SourcePackage: qemu-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0X482M
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/15/2009:svnDellInc.:pnVostro1220:pvr:rvnDellInc.:rn0X482M:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Vostro 1220
dmi.sys.vendor: Dell Inc.

[Serge Hallyn (serge-hallyn)]

/proc/$$/maps of the kvm process

[Serge Hallyn (serge-hallyn)]

I'm trying to reproduce with an upstart job that immediately reboots, but it's not working. Could be (a) there was actually a memory error on the host, or (b) reproducing it requires interacting with lightdm/unity before rebooting.

[Serge Hallyn (serge-hallyn)]

Reboots have been running for a few hours now. Can't reproduce. Will mark invalid, but reopen if i see it again.

[Serge Hallyn (serge-hallyn)]

Actually, marked incomplete since I can't get more information. (THe laptop now has qemu-kvm-dbgsym installed so hopefully i'll run into it again and be able to attach gdb to it)

[Launchpad Janitor (janitor)]

[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.]

[Chun-Hung Chen (arnose)]

Recently I also encounter this issue. I am running reboot stress test with ubuntu desktop. After 2xxx times, the VM shutdown then reboot to have the same memory corruption information in qemu.log. It also causes my libvirt responds wierd. After kill the VM, libvirtd works well.

[Serge Hallyn (serge-hallyn)]

Quoting Chun-Hung Chen (<email address hidden>):
> Recently I also encounter this issue. I am running reboot stress test

Thanks for the information.

> with ubuntu desktop. After 2xxx times, the VM shutdown then reboot to

Does this mean "more than 2000 times"?

> have the same memory corruption information in qemu.log. It also causes
> my libvirt responds wierd. After kill the VM, libvirtd works well.

Can you show the tail end of /var/log/libvirt/qemu/$vm.log, as well as
anything informative from syslog or /var/log/libvirt/libvirtd.log?

 status: incomplete
 priority: medium

[Chun-Hung Chen (arnose)]

Actually, I have encounter twice with the same VM at two different hardware configuration.
One is running for more than two thousand times and another is about twenty times.

[Chun-Hung Chen (arnose)]

It seems that I have a VM image which could cause this issue definitely in a small round of reboot stress. The same VM would totally shutdown if failed in free() and lock libvirtd if failed in malloc().

[Serge Hallyn (serge-hallyn)]

@arnose

was this image a simple installation of quantal? Can you reproduce this by creating images int he same way?

[Chun-Hung Chen (arnose)]

@serge-hallyn
this image is provided by others. It is a qcow2 image file.

[Serge Hallyn (serge-hallyn)]

Can you give us the URL?

[Chun-Hung Chen (arnose)]

@serge-hallyn
Sorry for the late respond. The image file is provided by internal colleague in my company. I am not sure if it is suitable to provide it to others other than the one in our company. However, it seems behaves differently on different hardware configuration. The VM was crashed always on some 1U or 2U server. But it seems work fine in my personal desktop.

[Serge Hallyn (serge-hallyn)]

Please reply if you can still reproduce this bug.

[Launchpad Janitor (janitor)]

[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.]