I just tried again with two logical CPUs and the core set to "Westmere"
(I think that was the default), and didn't see the bug. So this seems
related specifically to "[x] Copy host CPU configuration" being checked.
Here's the /proc/cpuinfo from the "virtual Westmere" where it works:
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1524069
Title:
Xenial KVM: updating Trusty guest from 3.13.0-68 to
Also, the hypervisor's /proc/cpuinfo reports the following CPU
configuration (8 cores of the same):
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz
stepping: 3
microcode : 0x1e
For what it's worth, unchecking "[ ] Copy host CPU configuration" in
virt-manager and selecting "Hypervisor default" for the CPU is a
workaround. (/proc/cpuinfo reports "QEMU Virtual CPU version 2.4.0")
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags added: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1524069
Title:
Xenial KVM: updating Trusty guest from 3.13.0-68 to 3.13.0-71 causes
kernel exception
Status
5 matches
Mail list logo