KVM Guest gets general protection fault on two CPUs

Bug #836119 reported by Endre Stølsvik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kvm (Ubuntu)
Invalid
High
Unassigned

Bug Description

Got the following errors (listed below) when trying to enter a KVM Guest running Ubuntu desktop 11.04 on top of a KVM Host running Ubuntu server 11.04 install.
This was done from a virt-manager running on a 11.04 desktop using ssh over to the server.
The "entering" mentioned was merely to move the mouse to within the VM viewer.

I could still login to the KVM guest with ssh, though.

I tried shutting down the KVM guest from within using 'shutdown -h NOW', but while this took down the OS, it apparently didn't properly shut down the actual VM instance.

When trying to use virt-manager (remotely, as mentioned) to forcefully shut it down, this didn't work out either - just hanging the GUI for a little while, then stating that the operation timed out.

When using virsh when logged into the Host, I get:
  virsh # destroy Store
  error: Failed to destroy domain Store
  error: Timed out during operation: cannot acquire state change lock

Then, after following some ideas from..
  https://bugzilla.redhat.com/show_bug.cgi?id=676205
.. I now have a situation where virsh list doesn't even return:

endre@SixCore:~$ virsh
Welcome to virsh, the virtualization interactive terminal.
  ..
virsh # list
 Id Name State
----------------------------------
 17 NewDisk running
[.. hanging .. "Store" should have been printed here ..]

Today (the next day), I tried virsh list again, and this time it worked out, with Store listed as "running". I then tried connecting via virt-manager, but when trying to go into the machine (virt-viewer?) I get "Connecting to to graphical console for Guest", just hanging.

I then tried to forcefully kill the VM again ("Force off" in virt-manager), but this yields the following traceback. Notice the "libvirtError: Timed out during operation: cannot acquire state change lock".

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 908, in _do_destroy_domain
    vm.destroy()
  File "/usr/share/virt-manager/virtManager/domain.py", line 1087, in destroy
    self._backend.destroy()
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 346, in destroy
    if ret == -1: raise libvirtError ('virDomainDestroy() failed', dom=self)
libvirtError: Timed out during operation: cannot acquire state change lock

Aug 27 11:10:36 Store kernel: [36104.328903] general protection fault: 0000 [#2] SMP
Aug 27 11:10:36 Store kernel: [36104.328915] last sysfs file: /sys/devices/system/cpu/cpu5/cache/index2/shared_cpu_map
Aug 27 11:10:36 Store kernel: [36104.328923] CPU 1
Aug 27 11:10:36 Store kernel: [36104.328926] Modules linked in: binfmt_misc parport_pc ppdev vesafb joydev psmouse virtio_balloon seri
o_raw i2c_piix4 lp parport usbhid hid virtio_net virtio_blk floppy virtio_pci virtio_ring virtio
Aug 27 11:10:36 Store kernel: [36104.328965]
Aug 27 11:10:36 Store kernel: [36104.328972] Pid: 873, comm: Xorg Tainted: G D 2.6.38-11-generic #48-Ubuntu Bochs Bochs
Aug 27 11:10:36 Store kernel: [36104.328983] RIP: 0010:[<ffffffff8104ba86>] [<ffffffff8104ba86>] __wake_up_common+0x56/0x90
Aug 27 11:10:36 Store kernel: [36104.329002] RSP: 0018:ffff880078701b08 EFLAGS: 00010096
Aug 27 11:10:36 Store kernel: [36104.329008] RAX: ffff880053cf1c18 RBX: d4d5281e29fedeed RCX: 00000000000000c3
Aug 27 11:10:36 Store kernel: [36104.329014] RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff880053cf1c18
Aug 27 11:10:36 Store kernel: [36104.329020] RBP: ffff880078701b48 R08: 00000000000000c3 R09: 0000000000000246
Aug 27 11:10:36 Store kernel: [36104.329025] R10: ffff88007d00c800 R11: 0000000000000000 R12: 00000000627812c6
Aug 27 11:10:36 Store kernel: [36104.329031] R13: ffff880054826148 R14: 00000000000000c3 R15: 0000000000000001
Aug 27 11:10:36 Store kernel: [36104.329052] FS: 00007f55818758a0(0000) GS:ffff88007fc40000(0000) knlGS:00000000f69a4880
Aug 27 11:10:36 Store kernel: [36104.329058] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 27 11:10:36 Store kernel: [36104.329064] CR2: 00007f5b0ad2aa30 CR3: 000000007844d000 CR4: 00000000000006e0
Aug 27 11:10:36 Store kernel: [36104.329085] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 27 11:10:36 Store kernel: [36104.329105] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 27 11:10:36 Store kernel: [36104.329113] Process Xorg (pid: 873, threadinfo ffff880078700000, task ffff8800792cadc0)
Aug 27 11:10:36 Store kernel: [36104.329118] Stack:
Aug 27 11:10:36 Store kernel: [36104.329121] ffff880017e39f00 0000000100000001 ffff880078701b28 ffff880054826140
Aug 27 11:10:36 Store kernel: [36104.329130] 0000000000000001 0000000000000282 0000000000000001 00000000000000c3
Aug 27 11:10:36 Store kernel: [36104.329140] ffff880078701b88 ffffffff8104e373 ffff880078701b78 ffff880054bc49c0
Aug 27 11:10:36 Store kernel: [36104.329148] Call Trace:
Aug 27 11:10:36 Store kernel: [36104.329160] [<ffffffff8104e373>] __wake_up_sync_key+0x53/0x80
Aug 27 11:10:36 Store kernel: [36104.329172] [<ffffffff814c15fe>] sock_def_readable+0x3e/0x70
Aug 27 11:10:36 Store kernel: [36104.329254] [<ffffffff8155e32c>] unix_stream_sendmsg+0x2cc/0x470
Aug 27 11:10:36 Store kernel: [36104.329265] [<ffffffff814bafee>] sock_aio_write+0x14e/0x160
Aug 27 11:10:36 Store kernel: [36104.329274] [<ffffffff814baea0>] ? sock_aio_write+0x0/0x160
Aug 27 11:10:36 Store kernel: [36104.329284] [<ffffffff811653d3>] do_sync_readv_writev+0xd3/0x110
Aug 27 11:10:36 Store kernel: [36104.329319] [<ffffffff812ae958>] ? apparmor_file_permission+0x18/0x20
Aug 27 11:10:36 Store kernel: [36104.329331] [<ffffffff81279c8c>] ? security_file_permission+0x2c/0xb0
Aug 27 11:10:36 Store kernel: [36104.329339] [<ffffffff81164b01>] ? rw_verify_area+0x61/0xf0
Aug 27 11:10:36 Store kernel: [36104.329347] [<ffffffff811656a4>] do_readv_writev+0xd4/0x1e0
Aug 27 11:10:36 Store kernel: [36104.329356] [<ffffffff81279cf3>] ? security_file_permission+0x93/0xb0
Aug 27 11:10:36 Store kernel: [36104.329364] [<ffffffff81164b01>] ? rw_verify_area+0x61/0xf0
Aug 27 11:10:36 Store kernel: [36104.329372] [<ffffffff811657f8>] vfs_writev+0x48/0x60
Aug 27 11:10:36 Store kernel: [36104.329379] [<ffffffff81165981>] sys_writev+0x51/0xc0
Aug 27 11:10:36 Store kernel: [36104.329387] [<ffffffff81086251>] ? posix_ktime_get_ts+0x11/0x20
Aug 27 11:10:36 Store kernel: [36104.329396] [<ffffffff8100c002>] system_call_fastpath+0x16/0x1b
Aug 27 11:10:36 Store kernel: [36104.329401] Code: 39 d5 48 8d 42 e8 48 8b 1a 74 40 48 83 eb 18 eb 0b 0f 1f 40 00 48 89 d8 48 8d 5a e8 44 8b 20 4c 89 f1 44 89 fa 8b 75 cc 48 89 c7 <ff> 50 10 85 c0 74 0c 41 83 e4 01 74 06 83 6d c8 01 74 0d 48 8d
Aug 27 11:10:36 Store kernel: [36104.329468] RIP [<ffffffff8104ba86>] __wake_up_common+0x56/0x90
Aug 27 11:10:36 Store kernel: [36104.329478] RSP <ffff880078701b08>
Aug 27 11:10:36 Store kernel: [36104.329486] ---[ end trace 6a7ca2093395d464 ]---
Aug 27 11:10:37 Store kernel: [36104.872159] general protection fault: 0000 [#3] SMP
Aug 27 11:10:37 Store kernel: [36104.872173] last sysfs file: /sys/devices/system/cpu/cpu5/cache/index2/shared_cpu_map
Aug 27 11:10:37 Store kernel: [36104.872182] CPU 0
Aug 27 11:10:37 Store kernel: [36104.872187] Modules linked in: binfmt_misc parport_pc ppdev vesafb joydev psmouse virtio_balloon serio_raw i2c_piix4 lp parport usbhid hid virtio_net virtio_blk floppy virtio_pci virtio_ring virtio
Aug 27 11:10:37 Store kernel: [36104.872223]
Aug 27 11:10:37 Store kernel: [36104.872230] Pid: 873, comm: Xorg Tainted: G D 2.6.38-11-generic #48-Ubuntu Bochs Bochs
Aug 27 11:10:37 Store kernel: [36104.872280] RIP: 0010:[<ffffffff814c017c>] [<ffffffff814c017c>] sock_def_wakeup+0x1c/0x40
Aug 27 11:10:37 Store kernel: [36104.872301] RSP: 0000:ffff880078701798 EFLAGS: 00010286
Aug 27 11:10:37 Store kernel: [36104.872307] RAX: fffb880054826508 RBX: ffff880054bc5040 RCX: 0000000000000000
Aug 27 11:10:37 Store kernel: [36104.872313] RDX: ffff880054bc42c8 RSI: 0000000000000286 RDI: fffb880054826500
Aug 27 11:10:37 Store kernel: [36104.872319] RBP: ffff880078701798 R08: 0000000000000000 R09: 0000000000000000
Aug 27 11:10:37 Store kernel: [36104.872324] R10: ffff880078265c10 R11: 0000000000000008 R12: ffff880054bc50b0
Aug 27 11:10:37 Store kernel: [36104.872330] R13: 0000000000000001 R14: ffff880054bc4000 R15: 0000000000000000
Aug 27 11:10:37 Store kernel: [36104.872348] FS: 00007f55818758a0(0000) GS:ffff88007fc00000(0000) knlGS:00000000f69a4880
Aug 27 11:10:37 Store kernel: [36104.872355] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 27 11:10:37 Store kernel: [36104.872361] CR2: 00000000004002a8 CR3: 0000000079ad4000 CR4: 00000000000006f0
Aug 27 11:10:37 Store kernel: [36104.872382] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 27 11:10:37 Store kernel: [36104.872403] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 27 11:10:37 Store kernel: [36104.872411] Process Xorg (pid: 873, threadinfo ffff880078700000, task ffff8800792cadc0)
Aug 27 11:10:37 Store kernel: [36104.872416] Stack:
Aug 27 11:10:37 Store kernel: [36104.872420] ffff880078701808 ffffffff8155bf78 ffff8800787017c8 ffffffff81178d3f
Aug 27 11:10:37 Store kernel: [36104.872429] ffff8800390d1600 ffff880054bc42c8 00000000787017e8 0000000000000000
Aug 27 11:10:37 Store kernel: [36104.872439] ffff880078265c10 ffff8800626a9e40 0000000000000000 ffff88004b7d2180
Aug 27 11:10:37 Store kernel: [36104.872448] Call Trace:
Aug 27 11:10:37 Store kernel: [36104.872462] [<ffffffff8155bf78>] unix_release_sock+0x208/0x250
Aug 27 11:10:37 Store kernel: [36104.872474] [<ffffffff81178d3f>] ? __d_free+0x4f/0x70
Aug 27 11:10:37 Store kernel: [36104.872484] [<ffffffff8155bfe6>] unix_release+0x26/0x30
Aug 27 11:10:37 Store kernel: [36104.872492] [<ffffffff814bb8d9>] sock_release+0x29/0x90
Aug 27 11:10:37 Store kernel: [36104.872499] [<ffffffff814bb957>] sock_close+0x17/0x30
Aug 27 11:10:37 Store kernel: [36104.872508] [<ffffffff811661fe>] __fput+0xbe/0x200
Aug 27 11:10:37 Store kernel: [36104.872515] [<ffffffff81166365>] fput+0x25/0x30
Aug 27 11:10:37 Store kernel: [36104.872523] [<ffffffff81162c40>] filp_close+0x60/0x90
Aug 27 11:10:37 Store kernel: [36104.872534] [<ffffffff81069e08>] put_files_struct+0x88/0xf0
Aug 27 11:10:37 Store kernel: [36104.872542] [<ffffffff81069f34>] exit_files+0x54/0x70
Aug 27 11:10:37 Store kernel: [36104.872576] [<ffffffff8106a425>] do_exit+0x175/0x410
Aug 27 11:10:37 Store kernel: [36104.872588] [<ffffffff815c484f>] oops_end+0xaf/0xf0
Aug 27 11:10:37 Store kernel: [36104.872597] [<ffffffff810100eb>] die+0x5b/0x90
Aug 27 11:10:37 Store kernel: [36104.872605] [<ffffffff815c4342>] do_general_protection+0x162/0x170
Aug 27 11:10:37 Store kernel: [36104.872613] [<ffffffff815c3b65>] general_protection+0x25/0x30
Aug 27 11:10:37 Store kernel: [36104.872624] [<ffffffff8104ba86>] ? __wake_up_common+0x56/0x90
Aug 27 11:10:37 Store kernel: [36104.872633] [<ffffffff8104ba89>] ? __wake_up_common+0x59/0x90
Aug 27 11:10:37 Store kernel: [36104.872642] [<ffffffff8104e373>] __wake_up_sync_key+0x53/0x80
Aug 27 11:10:37 Store kernel: [36104.872651] [<ffffffff814c15fe>] sock_def_readable+0x3e/0x70
Aug 27 11:10:37 Store kernel: [36104.872661] [<ffffffff8155e32c>] unix_stream_sendmsg+0x2cc/0x470
Aug 27 11:10:37 Store kernel: [36104.872670] [<ffffffff814bafee>] sock_aio_write+0x14e/0x160
Aug 27 11:10:37 Store kernel: [36104.872679] [<ffffffff814baea0>] ? sock_aio_write+0x0/0x160
Aug 27 11:10:37 Store kernel: [36104.872687] [<ffffffff811653d3>] do_sync_readv_writev+0xd3/0x110
Aug 27 11:10:37 Store kernel: [36104.872700] [<ffffffff812ae958>] ? apparmor_file_permission+0x18/0x20
Aug 27 11:10:37 Store kernel: [36104.872710] [<ffffffff81279c8c>] ? security_file_permission+0x2c/0xb0
Aug 27 11:10:37 Store kernel: [36104.872719] [<ffffffff81164b01>] ? rw_verify_area+0x61/0xf0
Aug 27 11:10:37 Store kernel: [36104.872727] [<ffffffff811656a4>] do_readv_writev+0xd4/0x1e0
Aug 27 11:10:37 Store kernel: [36104.872736] [<ffffffff81279cf3>] ? security_file_permission+0x93/0xb0
Aug 27 11:10:37 Store kernel: [36104.872744] [<ffffffff81164b01>] ? rw_verify_area+0x61/0xf0
Aug 27 11:10:37 Store kernel: [36104.872752] [<ffffffff811657f8>] vfs_writev+0x48/0x60
Aug 27 11:10:37 Store kernel: [36104.872759] [<ffffffff81165981>] sys_writev+0x51/0xc0
Aug 27 11:10:37 Store kernel: [36104.872767] [<ffffffff81086251>] ? posix_ktime_get_ts+0x11/0x20
Aug 27 11:10:37 Store kernel: [36104.872775] [<ffffffff8100c002>] system_call_fastpath+0x16/0x1b
Aug 27 11:10:37 Store kernel: [36104.872780] Code: 5c 41 5d c9 c3 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 66 66 66 66 90 48 8b bf b8 00 00 00 0f ae f0 48 85 ff 74 18 48 8d 47 08 <48> 39 47 08 74 0e 31 c9 31 d2 be 01 00 00 00 e8 30 e2 b8 ff c9
Aug 27 11:10:37 Store kernel: [36104.872848] RIP [<ffffffff814c017c>] sock_def_wakeup+0x1c/0x40
Aug 27 11:10:37 Store kernel: [36104.872857] RSP <ffff880078701798>
Aug 27 11:10:37 Store kernel: [36104.872866] ---[ end trace 6a7ca2093395d465 ]---
Aug 27 11:10:37 Store kernel: [36104.872872] Fixing recursive fault but reboot is needed!
---
Architecture: amd64
DistroRelease: Ubuntu 11.04
InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426)
KvmCmdLine:
 UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
 103 1787 1 1 325928 293584 2 Aug30 ? 00:01:37 /usr/bin/kvm -S -M pc-0.14 -cpu phenom,+wdt,+skinit,+osvw,+3dnowprefetch,+misalignsse,+sse4a,+abm,+cr8legacy,+extapic,+cmp_legacy,+lahf_lm,+rdtscp,+pdpe1gb,+popcnt,+cx16,+ht,+vme -enable-nesting -enable-kvm -m 1024 -smp 4,sockets=4,cores=1,threads=1 -name NewDisk -uuid e8248de8-adde-3f92-37ef-29846c155803 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/NewDisk.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=utc -boot order=c,menu=off -drive file=/dev/SixCoreVG/NewDisk_Root,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/dev/SixCoreVG/NewDisk_Data,if=none,id=drive-virtio-disk2,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=virtio-disk2 -drive file=/dev/SixCoreVG/NewDisk_Swap,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=14,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e7:c4:03,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:0 -vga std -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
 103 1836 1 0 592299 401676 4 Aug30 ? 00:01:10 /usr/bin/kvm -S -M pc-0.14 -cpu phenom,+wdt,+skinit,+osvw,+3dnowprefetch,+misalignsse,+sse4a,+abm,+cr8legacy,+extapic,+cmp_legacy,+lahf_lm,+rdtscp,+pdpe1gb,+popcnt,+cx16,+ht,+vme -enable-nesting -enable-kvm -m 2048 -smp 6,sockets=6,cores=1,threads=1 -name Store -uuid 843a7cad-5c09-06a8-c0a2-df163897448e -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Store.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=utc -boot order=c,menu=off -drive file=/dev/SixCoreVG/Store_Root,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/dev/SixCoreVG/Store_Swap,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=/dev/SixCoreVG/Store_Data,if=none,id=drive-virtio-disk2,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk2,id=virtio-disk2 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=14,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e1:14:d4,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 std -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7
MachineType: System manufacturer System Product Name
Package: kvm 1:84+dfsg-0ubuntu16+0.14.0+noroms+0ubuntu4.4
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-11-server root=/dev/mapper/hostnameVG-hostnameLV_Root ro
ProcVersionSignature: Ubuntu 2.6.38-11.48-server 2.6.38.8
Tags: natty
Uname: Linux 2.6.38-11-server x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
dmi.bios.date: 06/13/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2201
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A89GTD-PRO/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/13/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for taking the time to submit this bug and helping to make Ubuntu better.

Do I understand right that the kernel oops you pasted at the end of the bug description is from the natty guest?

Can you run 'apport-collect 836119' on the server, to provide some more details to help us debug this issue?

Changed in kvm (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Endre Stølsvik (stolsvik) wrote :

You do understand correctly - the oops is from the natty guest.

Today when I came home, the server had completely frozen. I took a physical screenshot, which I've included - and there was no trace of this in the syslog og kern, the log just stopped at some point, then the next log entry was many hours later starting at boot.

I will try to apport.

Revision history for this message
Endre Stølsvik (stolsvik) wrote : BootDmesg.txt

apport information

tags: added: apport-collected natty
description: updated
Revision history for this message
Endre Stølsvik (stolsvik) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote : Dependencies.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote : Lspci.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote : Lsusb.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote : ProcModules.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote : UdevDb.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote : UdevLog.txt

apport information

Revision history for this message
Endre Stølsvik (stolsvik) wrote :

Note: The "server" refers to the HOST physical box.

Revision history for this message
Endre Stølsvik (stolsvik) wrote :

Do you want an apport from the Guest too?

Revision history for this message
Endre Stølsvik (stolsvik) wrote :

I don't know how interesting the following messages are? - "Google says" that they are not to be bothered about, but that was apparently several years ago?

Aug 30 21:38:29 SixCore kernel: [ 38.115972] kvm_get_msr_common: 21 callbacks suppressed
Aug 30 21:38:29 SixCore kernel: [ 38.115976] kvm: 1836: cpu0 unhandled rdmsr: 0xc0010112
Aug 30 21:38:29 SixCore kernel: [ 38.116054] kvm: 1836: cpu0 unhandled rdmsr: 0xc0010048
Aug 30 21:38:29 SixCore kernel: [ 38.252871] kvm: 1836: cpu0 unhandled rdmsr: 0xc0010001
Aug 30 21:38:29 SixCore kernel: [ 38.265889] kvm: 1836: cpu1 unhandled rdmsr: 0xc0010048
Aug 30 21:38:29 SixCore kernel: [ 38.278651] kvm: 1836: cpu2 unhandled rdmsr: 0xc0010048
Aug 30 21:38:29 SixCore kernel: [ 38.291914] kvm: 1836: cpu3 unhandled rdmsr: 0xc0010048
Aug 30 21:38:29 SixCore kernel: [ 38.304421] kvm: 1836: cpu4 unhandled rdmsr: 0xc0010048
Aug 30 21:38:29 SixCore kernel: [ 38.319441] kvm: 1836: cpu5 unhandled rdmsr: 0xc0010048
Aug 30 21:38:30 SixCore kernel: [ 39.229501] kvm: 1787: cpu0 unhandled rdmsr: 0xc0010112
Aug 30 21:38:30 SixCore kernel: [ 39.232666] kvm: 1787: cpu0 unhandled rdmsr: 0xc0010048

Aug 30 23:15:18 SixCore kernel: [ 5847.802123] kvm: 1787: cpu0 unhandled rdmsr: 0xc0010112
Aug 30 23:15:18 SixCore kernel: [ 5847.805278] kvm: 1787: cpu0 unhandled rdmsr: 0xc0010048
Aug 30 23:15:18 SixCore kernel: [ 5847.951054] kvm: 1787: cpu0 unhandled rdmsr: 0xc0010001
Aug 30 23:15:18 SixCore kernel: [ 5847.967210] kvm: 1787: cpu1 unhandled rdmsr: 0xc0010048
Aug 30 23:15:18 SixCore kernel: [ 5847.984448] kvm: 1787: cpu2 unhandled rdmsr: 0xc0010048
Aug 30 23:15:18 SixCore kernel: [ 5848.002153] kvm: 1787: cpu3 unhandled rdmsr: 0xc0010048

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for the info - on need for apport from the guest.

Changed in kvm (Ubuntu):
status: Incomplete → New
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Can you guide me through precisely how you created the guest which causes the server to crash, so that I can try to reproduce?

Changed in kvm (Ubuntu):
status: New → Incomplete
Revision history for this message
Endre Stølsvik (stolsvik) wrote :

Sorry for delay.

This seems to have been a physical problem with the RAM. It is a six-core AMD system with 4 sticks of 4 GB RAM, specced to 1600 MHz. Apprarently the mainboard doesn't overvolt the RAM to its needed 1.65V when running at 1600MHz (even though the BIOS actually asks whether it should do this when you apply the RAM-stick-specified settings..) And then, even when setting the voltage to 1.65 manually, the system still isn't stable at 1600 MHz RAM speed.

But when I clocked the RAM down to ca. 1450 MHz instead (currently at 1.60v), the system seems fully stable (even with a slight overclock of the CPU - so this was definitely a RAM issue).

This bug can be closed. Sorry for the noise.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for the update.

Changed in kvm (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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