qemu-system-x86_64 crashed with SIGABRT in qemu_memalign()

[Jack Wasey]

just trying to start a virtual machine.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: qemu-kvm 1.0+noroms-0ubuntu6
Uname: Linux 3.3.0-030300rc5-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 1 15:55:58 2012
ExecutablePath: /usr/bin/qemu-system-x86_64
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100709)
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
MachineType: Foxconn P35
ProcCmdline: /usr/bin/kvm -S -M pc-0.14 -cpu core2duo,+lahf_lm,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+pbe,+tm,+ht,+ss,+acpi,+ds -enable-kvm -m 2000 -smp 2,sockets=2,cores=1,threads=1 -name Windows7 -uuid d5f3243c-18cc-c2a8-37d1-83997ddfd487 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/media/tank/VirtualBox/HardDisks/Win7UltimateExpandable.qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,cache=none -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -drive file=/media/tank/vm/virtio-win7.img,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=18,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:12:22:89,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x6 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.3.0-030300rc5-generic root=UUID=8eb006d2-27c5-4e10-ae7d-1ff8d4ee8d9a ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: qemu-kvm
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: qemu-system-x86_64 crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-02-28 (2 days ago)
UserGroups:

dmi.bios.date: 06/26/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.name: P35AX-S
dmi.board.vendor: Foxconn
dmi.board.version: 1.0
dmi.chassis.type: 6
dmi.chassis.vendor: Foxconn
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd06/26/2009:svnFoxconn:pnP35:pvrA02:rvnFoxconn:rnP35AX-S:rvr1.0:cvnFoxconn:ct6:cvr:
dmi.product.name: P35
dmi.product.version: A02
dmi.sys.vendor: Foxconn

[Apport retracing service (apport)]

StacktraceTop:
 qemu_memalign (alignment=<optimized out>, size=2097152000) at oslib-posix.c:82
 qemu_ram_alloc_from_ptr (dev=<optimized out>, name=<optimized out>, size=2097152000, host=<optimized out>) at /build/buildd/qemu-kvm-1.0+noroms/exec.c:2978
 memory_region_init_ram (mr=0x7ff8319844f0, dev=0x0, name=0x7ff8305befcc "pc.ram", size=2097152000) at /build/buildd/qemu-kvm-1.0+noroms/memory.c:979
 pc_memory_init (system_memory=0x7ff8318a00c0, kernel_filename=0x0, kernel_cmdline=0x7ff830590d60 "", initrd_filename=0x0, below_4g_mem_size=2097152000, above_4g_mem_size=0, rom_memory=0x7ff831984410, ram_memory=0x7fff581d6f20) at /build/buildd/qemu-kvm-1.0+noroms/hw/pc.c:992
 pc_init1 (system_memory=0x7ff8318a00c0, system_io=0x7ff8318a01c0, ram_size=2097152000, boot_device=0x7fff581d7210 "cad", kernel_filename=0x0, kernel_cmdline=0x7ff830590d60 "", initrd_filename=0x0, cpu_model=0x7fff581d7a54 "core2duo,+lahf_lm,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+pbe,+tm,+ht,+ss,+acpi,+ds", pci_enabled=1, kvmclock_enabled=1) at /build/buildd/qemu-kvm-1.0+noroms/hw/pc_piix.c:134

[Launchpad Janitor (janitor)]

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

[Serge Hallyn (serge-hallyn)]

Thanks for submitting this bug. Can you tell me if this happens every time you try to boot from a windows cd, or only once in awhile? Have you gotten this with anything other than windows?

I will try to reproduce.

[Serge Hallyn (serge-hallyn)]

Hi,

I'm running win7 professional N x64 under kvm with 1224M ram right now, ubt haven't crashed it yet. Can you tell me how quickly it crashes, and anything in particular you might do in the guest which reliably triggers this (i.e. watching youtube, etc)?

thanks!

[Matthew J. Ballard (sapphiretiger)]

I don't know about jack but (assuming from his op, its the same behavior) the guest doesn't even start before the crash occurs. In other words its the act of starting the guest that blows up.