Ubuntu
qemu-kvm package

kvm crashed when using the vmvga driver

Bug #1004965 reported by Simon Déziel on 2012-05-26

10

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	qemu-kvm (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

After changing the resolution of the guest, I tried removing a few icons from the launcher (unlock them) and the guest suddenly froze. Dmesg showed this error :

May 26 14:18:17 simon-laptop kernel: [67078.083077] kvm[6460]: segfault at 7f53010c7c08 ip 00007f52f838e7da sp 00007fff3f625c60 error 6 in libc-2.15.so[7f52f830e000+1b3000]

# apt-cache policy qemu-kvm
qemu-kvm:
  Installed: 1.0+noroms-0ubuntu13
  Candidate: 1.0+noroms-0ubuntu13
  Version table:
*** 1.0+noroms-0ubuntu13 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

# lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: qemu-kvm 1.0+noroms-0ubuntu13
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Sat May 26 15:10:57 2012
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 005: ID 17ef:480f Lenovo Integrated Webcam [R5U877]
MachineType: LENOVO 2516CTO
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic root=/dev/mapper/crypt-root ro quiet splash vt.handoff=7
SourcePackage: qemu-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/12/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET83WW (1.43 )
dmi.board.name: 2516CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6IET83WW(1.43):bd04/12/2012:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2516CTO
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO

Tags:

Revision history for this message

Simon Déziel (sdeziel) wrote on 2012-05-26:

#1

BootDmesg.txt Edit (65.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (57.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.4 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.6 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (1.9 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (144.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (332.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Simon Déziel (sdeziel) wrote on 2012-05-26:

#2

Apport-bug doesn't seem to be able to upload the .crash file maybe because it's fairly large (135MB). Is there another way to upload the crash file ?

Revision history for this message

Serge Hallyn (serge-hallyn) wrote on 2012-05-28:

#3

Thanks for reporting this bug.

If you were using libvirt, can you post the .xml file for the guest? If not, can you post the kvm command line you were using?

Which OS and release was the guest running?

Revision history for this message

Simon Déziel (sdeziel) wrote on 2012-05-28:

#4

Libvirt guest definition Edit (2.3 KiB, text/xml)

The host and the guest are both running Precise 64 bit.

Serge Hallyn (serge-hallyn) on 2012-05-28

Changed in qemu-kvm (Ubuntu):
status:	New → Incomplete

Revision history for this message

Simon Déziel (sdeziel) wrote on 2012-05-28:

#5

When trying to reproduce this, the guest just freezes after a couple of screen resolution changes. Here is the content of /var/log/libvirt/qemu/precise.log :

2012-05-28 14:03:40.590+0000: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 384 -smp 1,sockets=1,cores=1,threads=1 -name precise -uuid a27289c9-2c2a-4fd2-7480-1f70b24a966f -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/precise.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/dev/vg0/precise-desktop,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=18,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e2:ce:f2,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:0 -vga vmware -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
char device redirected to /dev/pts/9
kvm: -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e2:ce:f2,bus=pci.0,addr=0x3: pci_add_option_rom: failed to find romfile "pxe-virtio.rom"
vmsvga_update_rect: update x was < 0 (-65, w 1366)
*** glibc detected *** /usr/bin/kvm: malloc(): memory corruption: 0x00007f21f83bde40 ***

Revision history for this message

Serge Hallyn (serge-hallyn) wrote on 2012-05-28:

#6

Thanks. Can you tell us what you changed the resolution from->to?

Both host and guest are up-to-date right?

There were recently bugs in the vga+vnc combination, so won't be entirely surprised to find more, but will try to reproduce.

Changed in qemu-kvm (Ubuntu):
status:	Incomplete → New
importance:	Undecided → Medium

Revision history for this message

Simon Déziel (sdeziel) wrote on 2012-05-28:

#7

libvirt/qemu/precise.log including backtrack and memory map Edit (56.3 KiB, text/plain)

The host is fully up to date and I just pulled this in the guest :

xserver-xorg-video-vmware 1:12.0.1-1ubuntu1.1

While trying to reproduce this with the guest updated it crashed right after attempting to open a session. The guest did a resolution change itself while at the login screen. Judging by the size the screen, the resolution was initially ~1360x768 and was resized to the largest one offered by the driver. This time more information was loged in the libvirt/qemu/precise.log (attached).

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-06-23:

#8

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in qemu-kvm (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.