From: Zdenek Kaspar <zkaspar82@gmail.com>
To: kvm@vger.kernel.org
Subject: linux-4.4: qemu starting VM emits vmwrite error
Date: Mon, 11 Jan 2016 19:19:33 +0100 [thread overview]
Message-ID: <5693F235.5010309@gmail.com> (raw)
Hi, today I compiled linux-4.4 kernel on older machine and noticed qemu
complains:
Jan 11 14:28:58 HOST kernel: vmwrite error: reg 401e value 10 (err 12)
Jan 11 14:28:58 HOST kernel: CPU: 0 PID: 6004 Comm: qemu-build Not
tainted 4.4.0-0-core2 #1
Jan 11 14:28:58 HOST kernel: Hardware name: /DG35EC,
BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010
Jan 11 14:28:58 HOST kernel: ffff88007be68000 ffffffff8116e2b9
0000000000000000 ffffffffa020b88d
Jan 11 14:28:58 HOST kernel: ffff88007be68000 ffff880061173d80
fffffffffffffff2 ffffffffa01d8fdc
Jan 11 14:28:58 HOST kernel: 0000000000000000 00007f7ff40008c0
ffffffffa01b8363 ffffffff81608c98
Jan 11 14:28:58 HOST kernel: Call Trace:
Jan 11 14:28:58 HOST kernel: [<ffffffff8116e2b9>] ? dump_stack+0x40/0x57
Jan 11 14:28:58 HOST kernel: [<ffffffffa020b88d>] ?
vmx_cpuid_update+0x5d/0x150 [kvm_intel]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01d8fdc>] ?
kvm_vcpu_ioctl_set_cpuid2+0x4c/0x70 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01b8363>] ?
kvm_arch_vcpu_ioctl+0x903/0xfa0 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffff810d1401>] ?
vunmap_page_range+0x211/0x330
Jan 11 14:28:58 HOST kernel: [<ffffffffa02088ab>] ?
vmx_vcpu_load+0x14b/0x1b0 [kvm_intel]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01b78a5>] ?
kvm_arch_vcpu_load+0x55/0x210 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01ad29b>] ?
kvm_vcpu_ioctl+0xbb/0x510 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01d9260>] ?
kvm_dev_ioctl_get_cpuid+0x210/0x2b0 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffff810f3a53>] ? do_vfs_ioctl+0x293/0x470
Jan 11 14:28:58 HOST kernel: [<ffffffff81034556>] ?
__do_page_fault+0x146/0x380
Jan 11 14:28:58 HOST kernel: [<ffffffff810f3c66>] ? SyS_ioctl+0x36/0x70
Jan 11 14:28:58 HOST kernel: [<ffffffff812d4eee>] ?
entry_SYSCALL_64_fastpath+0x12/0x71
Jan 11 14:28:58 HOST kernel: vmwrite error: reg 401e value 10 (err 12)
Jan 11 14:28:58 HOST kernel: CPU: 0 PID: 6005 Comm: qemu-build Not
tainted 4.4.0-0-core2 #1
Jan 11 14:28:58 HOST kernel: Hardware name: /DG35EC,
BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010
Jan 11 14:28:58 HOST kernel: ffff88004af40000 ffffffff8116e2b9
0000000000000000 ffffffffa020b88d
Jan 11 14:28:58 HOST kernel: ffff88004af40000 ffff88007bc83d80
fffffffffffffff2 ffffffffa01d8fdc
Jan 11 14:28:58 HOST kernel: 0000000000000000 00007f7fec0008c0
ffffffffa01b8363 ffffffff81608c98
Jan 11 14:28:58 HOST kernel: Call Trace:
Jan 11 14:28:58 HOST kernel: [<ffffffff8116e2b9>] ? dump_stack+0x40/0x57
Jan 11 14:28:58 HOST kernel: [<ffffffffa020b88d>] ?
vmx_cpuid_update+0x5d/0x150 [kvm_intel]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01d8fdc>] ?
kvm_vcpu_ioctl_set_cpuid2+0x4c/0x70 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01b8363>] ?
kvm_arch_vcpu_ioctl+0x903/0xfa0 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffff810d1401>] ?
vunmap_page_range+0x211/0x330
Jan 11 14:28:58 HOST kernel: [<ffffffffa02088ab>] ?
vmx_vcpu_load+0x14b/0x1b0 [kvm_intel]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01b78a5>] ?
kvm_arch_vcpu_load+0x55/0x210 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01ad29b>] ?
kvm_vcpu_ioctl+0xbb/0x510 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffffa01d9260>] ?
kvm_dev_ioctl_get_cpuid+0x210/0x2b0 [kvm]
Jan 11 14:28:58 HOST kernel: [<ffffffff810f3a53>] ? do_vfs_ioctl+0x293/0x470
Jan 11 14:28:58 HOST kernel: [<ffffffff81034556>] ?
__do_page_fault+0x146/0x380
Jan 11 14:28:58 HOST kernel: [<ffffffff810f3c66>] ? SyS_ioctl+0x36/0x70
Jan 11 14:28:58 HOST kernel: [<ffffffff812d4eee>] ?
entry_SYSCALL_64_fastpath+0x12/0x71
# uname -r; cat /proc/cpuinfo | grep -E -m 2 "(flags|name)"
4.4.0-0-core2
model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl
aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm
lahf_lm dtherm tpr_shadow
# uname -r; cat /proc/cpuinfo | grep -E -m 2 "(flags|name)"
4.4.0-0-core2
model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx lm
constant_tsc arch_perfmon nopl pni ssse3 cx16 x2apic tsc_deadline_timer
hypervisor lahf_lm tsc_adjust
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.479.el6_7.3.x86_64
Not sure if it's something new, HOST with 4.1 kernel didn't complain...
TIA Z.
next reply other threads:[~2016-01-11 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 18:19 Zdenek Kaspar [this message]
2016-01-12 8:25 ` linux-4.4: qemu starting VM emits vmwrite error Han, Huaitong
2016-01-12 10:42 ` Paolo Bonzini
2016-01-12 17:58 ` Zdenek Kaspar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5693F235.5010309@gmail.com \
--to=zkaspar82@gmail.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).