Thanks, please re-open this bug (or file a new one) if you do manage
to reproduce.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Invalid
--
qemu-system-x86_64 crashed with SIGSEGV
https://bugs.launchpad.net/bugs/590232
You received this bug notification because you are a member
Thanks for taking the time to make Ubuntu better.
Is qemu hogging the cpu itself easily repeatable?
How long had qemu been running? There is a known memory leak (with fix
hopefully to be committed soon) which would explain both the failure to
malloc memory with GFP_ALLOC in your current_dmesg,
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/49743556/BootDmesg.txt
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/49743557/CoreDump.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/49743558/CurrentDmesg.txt
** Attachment
StacktraceTop: qcow2_alloc_cluster_offset (bs=0xea2010,
ThreadStacktrace:
--
qemu-system-x86_64 crashed with SIGSEGV
https://bugs.launchpad.net/bugs/590232
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
** Attachment added: Stacktrace.txt
http://launchpadlibrarian.net/49744690/Stacktrace.txt
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/49743557/CoreDump.gz
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
** Tags removed: need-amd64-retrace
--