Public bug reported:
Starting a KVM VM (via libvirt) on 12.04.1 running linux-image-generic-
lts-quantal/linux-image-3.5.0-18-generic causes the following in dmesg:
[ 35.818137] vmwrite error: reg 401e value a050a000 (err 12)
[ 35.834818] Pid: 3714, comm: kvm Tainted: G C 3.5.0-18-generic
#29~precise1-Ubuntu
[ 35.834822] Call Trace:
[ 35.834850] [<ffffffffa04f9c10>] vmwrite_error+0x2c/0x2e [kvm_intel]
[ 35.834855] [<ffffffffa04ef7b0>] vmcs_writel+0x20/0x30 [kvm_intel]
[ 35.834862] [<ffffffffa04f0d39>] vmx_cpuid_update+0x79/0x160 [kvm_intel]
[ 35.834895] [<ffffffffa016ecf9>] kvm_vcpu_ioctl_set_cpuid2+0x99/0xb0 [kvm]
[ 35.834912] [<ffffffffa01517ec>] kvm_arch_vcpu_ioctl+0x68c/0xcf0 [kvm]
[ 35.834919] [<ffffffff8115b0ca>] ? lazy_max_pages+0x1a/0x30
[ 35.834924] [<ffffffff81173f0b>] ? kfree+0x3b/0x140
[ 35.834941] [<ffffffffa04f426e>] ? vmx_vcpu_load+0x3e/0x1c0 [kvm_intel]
[ 35.834945] [<ffffffff8115dd14>] ? __vunmap.part.16+0x84/0xc0
[ 35.834962] [<ffffffffa0151007>] ? kvm_arch_vcpu_load+0x57/0x1b0 [kvm]
[ 35.834974] [<ffffffffa013d379>] kvm_vcpu_ioctl+0xb9/0x6c0 [kvm]
[ 35.834989] [<ffffffffa0150e7e>] ? kvm_arch_dev_ioctl+0x6e/0x1a0 [kvm]
[ 35.834994] [<ffffffff8119931a>] do_vfs_ioctl+0x8a/0x340
[ 35.834998] [<ffffffff81199661>] sys_ioctl+0x91/0xa0
[ 35.835004] [<ffffffff816a6a69>] system_call_fastpath+0x16/0x1b
[ 35.835966] vmwrite error: reg 401e value a050a000 (err 12)
[ 35.852638] Pid: 3715, comm: kvm Tainted: G C 3.5.0-18-generic
#29~precise1-Ubuntu
[ 35.852640] Call Trace:
[ 35.852649] [<ffffffffa04f9c10>] vmwrite_error+0x2c/0x2e [kvm_intel]
[ 35.852655] [<ffffffffa04ef7b0>] vmcs_writel+0x20/0x30 [kvm_intel]
[ 35.852661] [<ffffffffa04f0d39>] vmx_cpuid_update+0x79/0x160 [kvm_intel]
[ 35.852676] [<ffffffffa016ecf9>] kvm_vcpu_ioctl_set_cpuid2+0x99/0xb0 [kvm]
[ 35.852691] [<ffffffffa01517ec>] kvm_arch_vcpu_ioctl+0x68c/0xcf0 [kvm]
[ 35.852695] [<ffffffff8115b0ca>] ? lazy_max_pages+0x1a/0x30
[ 35.852699] [<ffffffff81173f0b>] ? kfree+0x3b/0x140
[ 35.852705] [<ffffffffa04f426e>] ? vmx_vcpu_load+0x3e/0x1c0 [kvm_intel]
[ 35.852709] [<ffffffff8115dd14>] ? __vunmap.part.16+0x84/0xc0
[ 35.852723] [<ffffffffa0151007>] ? kvm_arch_vcpu_load+0x57/0x1b0 [kvm]
[ 35.852735] [<ffffffffa013d379>] kvm_vcpu_ioctl+0xb9/0x6c0 [kvm]
[ 35.852750] [<ffffffffa0150e7e>] ? kvm_arch_dev_ioctl+0x6e/0x1a0 [kvm]
[ 35.852754] [<ffffffff8119931a>] do_vfs_ioctl+0x8a/0x340
[ 35.852758] [<ffffffff81199661>] sys_ioctl+0x91/0xa0
[ 35.852762] [<ffffffff816a6a69>] system_call_fastpath+0x16/0x1b
** Affects: linux-lts-quantal (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: quantal
** Attachment added: "dmesg and lspci output"
https://bugs.launchpad.net/bugs/1071322/+attachment/3413013/+files/dmesg%2Blspci.tar
--
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-lts-quantal/+bug/1071322/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
