Source: qemu Version: 1.5.0+dfsg-5 Severity: grave Justification: renders package unusable
Hi. Seems since the -5 update, any disk accesses in the VMs lead to errors. An I also get pty starting errors (in the VMs). In the HOST, the kernel log shows: [ 232.110748] Bridge firewalling registered [ 232.139083] tun: Universal TUN/TAP device driver, 1.6 [ 232.139085] tun: (C) 1999-2004 Max Krasnyansky <m...@qualcomm.com> [ 232.329819] device virbr1-nic entered promiscuous mode [ 232.579756] virbr1: topology change detected, propagating [ 232.579760] virbr1: port 1(virbr1-nic) entered forwarding state [ 232.579772] virbr1: port 1(virbr1-nic) entered forwarding state [ 232.612300] virbr1: port 1(virbr1-nic) entered disabled state [ 237.889048] device vnet0 entered promiscuous mode [ 237.933074] virbr1: topology change detected, propagating [ 237.933083] virbr1: port 2(vnet0) entered forwarding state [ 237.933105] virbr1: port 2(vnet0) entered forwarding state [ 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 [ 849.180661] virbr1: port 2(vnet0) entered disabled state [ 849.180769] device vnet0 left promiscuous mode [ 849.180772] virbr1: port 2(vnet0) entered disabled state [ 964.618958] device vnet0 entered promiscuous mode [ 964.650976] virbr1: topology change detected, propagating [ 964.650987] virbr1: port 2(vnet0) entered forwarding state [ 964.651009] virbr1: port 2(vnet0) entered forwarding state [ 968.654130] kvm_get_msr_common: 5 callbacks suppressed [ 968.654132] kvm [22296]: vcpu0 unhandled rdmsr: 0x345 [ 968.656979] kvm_set_msr_common: 22 callbacks suppressed [ 968.656981] kvm [22296]: vcpu0 unhandled wrmsr: 0x680 data 0 [ 968.656983] kvm [22296]: vcpu0 unhandled wrmsr: 0x6c0 data 0 [ 968.656986] kvm [22296]: vcpu0 unhandled wrmsr: 0x681 data 0 [ 968.656988] kvm [22296]: vcpu0 unhandled wrmsr: 0x6c1 data 0 [ 968.656990] kvm [22296]: vcpu0 unhandled wrmsr: 0x682 data 0 [ 968.656992] kvm [22296]: vcpu0 unhandled wrmsr: 0x6c2 data 0 [ 968.656994] kvm [22296]: vcpu0 unhandled wrmsr: 0x683 data 0 [ 968.656996] kvm [22296]: vcpu0 unhandled wrmsr: 0x6c3 data 0 [ 968.656998] kvm [22296]: vcpu0 unhandled wrmsr: 0x684 data 0 [ 968.657009] kvm [22296]: vcpu0 unhandled wrmsr: 0x6c4 data 0 [ 969.151358] kvm [22296]: vcpu0 unhandled rdmsr: 0xe8 [ 969.151363] kvm [22296]: vcpu0 unhandled rdmsr: 0xe7 [ 969.151366] kvm [22296]: vcpu0 unhandled rdmsr: 0xce [ 969.151368] kvm [22296]: vcpu0 unhandled rdmsr: 0xce [ 969.151370] kvm [22296]: vcpu0 unhandled rdmsr: 0x1ad [ 969.151373] kvm [22296]: vcpu0 unhandled rdmsr: 0xce [ 969.151375] kvm [22296]: vcpu0 unhandled rdmsr: 0xe8 [ 969.151377] kvm [22296]: vcpu0 unhandled rdmsr: 0xe7 [ 969.151672] kvm [22296]: vcpu0 unhandled rdmsr: 0xce [ 1117.807946] virbr1: port 2(vnet0) entered disabled state [ 1117.808244] device vnet0 left promiscuous mode [ 1117.808247] virbr1: port 2(vnet0) entered disabled state Example screenshot of the guest attached. Cheers, Chris.
<<attachment: image.png>>
