The bug exists upstream:
# uname -srv
Linux 3.7.0-030700rc2-generic #201210220428 SMP Mon Oct 22 08:29:33 UTC 2012
>From dmesg after a virsh start:
[ 62.697771] vmwrite error: reg 401e value a067a000 (err 12)
[ 62.714425] Pid: 3843, comm: kvm Tainted: G C
3.7.0-030700rc2-generic #201210220428
[ 62.714428] Call Trace:
[ 62.714443] [<ffffffffa0669c43>] vmwrite_error+0x2c/0x2e [kvm_intel]
[ 62.714449] [<ffffffffa065fd30>] vmcs_writel+0x20/0x30 [kvm_intel]
[ 62.714454] [<ffffffffa06611c9>] vmx_cpuid_update+0x79/0x160 [kvm_intel]
[ 62.714485] [<ffffffffa05a6959>] kvm_vcpu_ioctl_set_cpuid2+0x99/0xb0 [kvm]
[ 62.714500] [<ffffffffa0586ca7>] kvm_arch_vcpu_ioctl+0x677/0xc30 [kvm]
[ 62.714507] [<ffffffff8117d41b>] ? kfree+0x3b/0x150
[ 62.714514] [<ffffffffa06641fe>] ? vmx_vcpu_load+0x3e/0x1c0 [kvm_intel]
[ 62.714519] [<ffffffff811677e4>] ? __vunmap.part.15+0x84/0xc0
[ 62.714534] [<ffffffffa05864d7>] ? kvm_arch_vcpu_load+0x57/0x1b0 [kvm]
[ 62.714545] [<ffffffffa0572028>] kvm_vcpu_ioctl+0x138/0x6b0 [kvm]
[ 62.714559] [<ffffffffa058634e>] ? kvm_arch_dev_ioctl+0x6e/0x1a0 [kvm]
[ 62.714571] [<ffffffff811a334a>] do_vfs_ioctl+0x8a/0x340
[ 62.714575] [<ffffffff811a3691>] sys_ioctl+0x91/0xb0
[ 62.714580] [<ffffffff816cff59>] system_call_fastpath+0x16/0x1b
[ 62.715298] vmwrite error: reg 401e value a067a000 (err 12)
[ 62.731941] Pid: 3844, comm: kvm Tainted: G C
3.7.0-030700rc2-generic #201210220428
[ 62.731948] Call Trace:
[ 62.731970] [<ffffffffa0669c43>] vmwrite_error+0x2c/0x2e [kvm_intel]
[ 62.731988] [<ffffffffa065fd30>] vmcs_writel+0x20/0x30 [kvm_intel]
[ 62.731994] [<ffffffffa06611c9>] vmx_cpuid_update+0x79/0x160 [kvm_intel]
[ 62.732009] [<ffffffffa05a6959>] kvm_vcpu_ioctl_set_cpuid2+0x99/0xb0 [kvm]
[ 62.732029] [<ffffffffa0586ca7>] kvm_arch_vcpu_ioctl+0x677/0xc30 [kvm]
[ 62.732033] [<ffffffff8117d41b>] ? kfree+0x3b/0x150
[ 62.732039] [<ffffffffa06641fe>] ? vmx_vcpu_load+0x3e/0x1c0 [kvm_intel]
[ 62.732043] [<ffffffff811677e4>] ? __vunmap.part.15+0x84/0xc0
[ 62.732058] [<ffffffffa05864d7>] ? kvm_arch_vcpu_load+0x57/0x1b0 [kvm]
[ 62.732069] [<ffffffffa0572028>] kvm_vcpu_ioctl+0x138/0x6b0 [kvm]
[ 62.732084] [<ffffffffa058634e>] ? kvm_arch_dev_ioctl+0x6e/0x1a0 [kvm]
[ 62.732087] [<ffffffff811a334a>] do_vfs_ioctl+0x8a/0x340
[ 62.732090] [<ffffffff811a3691>] sys_ioctl+0x91/0xb0
[ 62.732094] [<ffffffff816cff59>] system_call_fastpath+0x16/0x1b
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071322
Title:
Quantal kernel for precise: starting KVM VM causes 'vmwrite error'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071322/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
