Hi. Finally I was able to get it running with IDE instead of SATA. That works,... fine... no ATA errors.
As you already expected,.. I still get the: [20424.793207] kvm [20947]: vcpu0 unhandled wrmsr: 0x6c1 data 0 [20424.793211] kvm [20947]: vcpu0 unhandled wrmsr: 0x682 data 0 [20424.793215] kvm [20947]: vcpu0 unhandled wrmsr: 0x6c2 data 0 [20424.793218] kvm [20947]: vcpu0 unhandled wrmsr: 0x683 data 0 [20424.793222] kvm [20947]: vcpu0 unhandled wrmsr: 0x6c3 data 0 [20424.793226] kvm [20947]: vcpu0 unhandled wrmsr: 0x684 data 0 [20424.793229] kvm [20947]: vcpu0 unhandled wrmsr: 0x6c4 data 0 [20425.946617] kvm [20947]: vcpu0 unhandled rdmsr: 0xe8 [20425.946623] kvm [20947]: vcpu0 unhandled rdmsr: 0xe7 [20425.946625] kvm [20947]: vcpu0 unhandled rdmsr: 0xce [20425.946628] kvm [20947]: vcpu0 unhandled rdmsr: 0xce So that seems to be unrelated... nevertheless.. I haven't seen these before with 1.5.0. Anyway...I will try to get it running with virtio as well, as you suggested... but I have troubles to convince libvirt of using it. btw: Might be unrealted... but with 1.5.1 and IDE now... when I do an update-initramfs -u inside the guest I gues these: [ 276.130974] traps: ld-linux-x32.so[5642] general protection ip:f7788e8d sp:ffe12528 error:0 in ld-2.17.so[f7772000+21000] [ 276.141129] traps: ld-linux-x32.so[5656] general protection ip:f77b8e8d sp:ff978458 error:0 in ld-2.17.so[f77a2000+21000] [ 276.151444] traps: ld-linux-x32.so[5670] general protection ip:f7721e8d sp:ffd44cc8 error:0 in ld-2.17.so[f770b000+21000] [ 276.207037] traps: ld-linux-x32.so[5714] general protection ip:f7770e8d sp:ff92cce8 error:0 in ld-2.17.so[f775a000+21000] [ 276.278651] traps: ld-linux-x32.so[5775] general protection ip:f76fbe8d sp:ffe73048 error:0 in ld-2.17.so[f76e5000+21000] [ 276.319277] traps: ld-linux-x32.so[5805] general protection ip:f76fee8d sp:fff486f8 error:0 in ld-2.17.so[f76e8000+21000] [ 276.329552] traps: ld-linux-x32.so[5819] general protection ip:f77a8e8d sp:ffc9b448 error:0 in ld-2.17.so[f7792000+21000] [ 276.338671] traps: ld-linux-x32.so[5833] general protection ip:f77bfe8d sp:ffe597b8 error:0 in ld-2.17.so[f77a9000+21000] [ 276.347835] traps: ld-linux-x32.so[5847] general protection ip:f77b9e8d sp:ffcb1f08 error:0 in ld-2.17.so[f77a3000+21000] [ 276.356548] traps: ld-linux-x32.so[5861] general protection ip:f77d1e8d sp:ffee16d8 error:0 in ld-2.17.so[f77bb000+21000] [ 313.662052] do_general_protection: 24 callbacks suppressed [ 313.662371] traps: ld-linux-x32.so[8926] general protection ip:f77e9e8d sp:ffa443a8 error:0 in ld-2.17.so[f77d3000+21000] [ 313.670615] traps: ld-linux-x32.so[8940] general protection ip:f7796e8d sp:ff879cf8 error:0 in ld-2.17.so[f7780000+21000] [ 313.677952] traps: ld-linux-x32.so[8954] general protection ip:f7791e8d sp:ffa25948 error:0 in ld-2.17.so[f777b000+21000] [ 313.708061] traps: ld-linux-x32.so[8998] general protection ip:f7724e8d sp:ffe6b858 error:0 in ld-2.17.so[f770e000+21000] [ 313.750866] traps: ld-linux-x32.so[9059] general protection ip:f77c7e8d sp:ff8a32a8 error:0 in ld-2.17.so[f77b1000+21000] [ 313.771839] traps: ld-linux-x32.so[9089] general protection ip:f77b0e8d sp:ffdfa038 error:0 in ld-2.17.so[f779a000+21000] [ 313.780747] traps: ld-linux-x32.so[9103] general protection ip:f777ae8d sp:ffc699a8 error:0 in ld-2.17.so[f7764000+21000] [ 313.789250] traps: ld-linux-x32.so[9117] general protection ip:f778de8d sp:ffce6358 error:0 in ld-2.17.so[f7777000+21000] [ 313.797782] traps: ld-linux-x32.so[9131] general protection ip:f7794e8d sp:ffcc8a38 error:0 in ld-2.17.so[f777e000+21000] [ 313.806169] traps: ld-linux-x32.so[9145] general protection ip:f7703e8d sp:ff9e61a8 error:0 in ld-2.17.so[f76ed000+21000] Seems also kinda weird.... never seen that before in that context. Cheers, Chris. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1204697 Title: guest disk accesses lead to ATA errors + host vcpu0 unhandled wrmsr/rdmsr Status in QEMU: New Status in “qemu” package in Debian: Confirmed Bug description: Hi. This is from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717724. Using Debian sid with 1.5.0-5 my Linux VMs (also Debian sid) are broken. When they boot I get gazillions of ATA errors inside the guest, as well as: [ 242.479951] kvm [7790]: vcpu0 unhandled rdmsr: 0x345 [ 242.483683] kvm [7790]: vcpu0 unhandled wrmsr: 0x680 data 0 [ 242.483687] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c0 data 0 [ 242.483689] kvm [7790]: vcpu0 unhandled wrmsr: 0x681 data 0 [ 242.483691] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c1 data 0 [ 242.483693] kvm [7790]: vcpu0 unhandled wrmsr: 0x682 data 0 [ 242.483696] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c2 data 0 [ 242.483698] kvm [7790]: vcpu0 unhandled wrmsr: 0x683 data 0 [ 242.483700] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c3 data 0 [ 242.483702] kvm [7790]: vcpu0 unhandled wrmsr: 0x684 data 0 [ 242.483704] kvm [7790]: vcpu0 unhandled wrmsr: 0x6c4 data 0 [ 242.988307] kvm [7790]: vcpu0 unhandled rdmsr: 0xe8 [ 242.988312] kvm [7790]: vcpu0 unhandled rdmsr: 0xe7 [ 242.988314] kvm [7790]: vcpu0 unhandled rdmsr: 0xce [ 242.988316] kvm [7790]: vcpu0 unhandled rdmsr: 0xce [ 242.988318] kvm [7790]: vcpu0 unhandled rdmsr: 0x1ad [ 242.988320] kvm [7790]: vcpu0 unhandled rdmsr: 0xce [ 242.988322] kvm [7790]: vcpu0 unhandled rdmsr: 0xe8 [ 242.988324] kvm [7790]: vcpu0 unhandled rdmsr: 0xe7 [ 242.988598] kvm [7790]: vcpu0 unhandled rdmsr: 0xce in the host. Please have a look at the Debian bug, for screenshots and more info. The problem didn't occur in 1.5.0-4 and there were basically no changes inside the VM (i.e. no kernel upgrade or so). Thanks, Chris. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1204697/+subscriptions
