I've hit this bug as well, OpenStack Nova Compute
2:12.0.4-0ubuntu1~cloud1, KVM 1:2.3+dfsg-5ubuntu9.4~cloud1. Hypervisor
is running Ubuntu 14.04.4 with CPU flags:
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
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) => (unassigned)
--
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 trusty guest 3.13.0-68
Hit this issue when booting Ubuntu Trusty VM on an Ubuntu host, worked
around via editing VM XML by adding this in section:
This + destroy->start the VM and it booted fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Just hit this same issue with nova-compute on Xenial and creating a
Xenial instance in nova. I worked around the issue with:
juju set-config nova-compute cpu-mode=host-passthrough
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I am seeing the same issue on some of my OpenStack compute nodes,
interestingly those which seem to have a newer CPU than others.
Affected CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
Mapped in guest to: Intel Core i7 9xx (Nehalem Class Core i7)
Unaffected Host CPU: Intel(R) Xeon(R) CPU
** Tags removed: kernel-key
** Tags added: kernel-da-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 trusty guest 3.13.0-68 raid6-pq panic in
** No longer affects: kvm (Ubuntu)
--
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 trusty guest 3.13.0-68 raid6-pq panic in
raid6_avx21_gen_syndrome() while
One could argue that libvirt should exclude x2apic from the host-model
checks, as it's emulated by qemu whether or not the host supports it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If you need avx2 support, --cpu Haswell-noTSX,-x2apic works on Haswell
desktop/laptop chips.
The most confusing problem is that qemu's definition of "Haswell" is
actually Haswell-E, -EP and -EX; Haswell itself lacks x2apic, which
qemu's Haswell requires. x2apic dates back to Nehalem, but qemu's
The bug persists in kernel 4.3.0-2-generic #11-Ubuntu.
@Mike - thanks for a workaround, it works, indeed :-)
--cpu=host-model-only
for virt-manager.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
To be honest, it's pretty annoying bug, as I am not able to install any
xenial VM :-(
--
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 trusty guest 3.13.0-68
@Serge, A workaround for me is to use "hypervisor default" in virt-
manager. I'm not sure what the equivalent is in virt-install, but maybe
using --cpu=host-model-only would be a workaround?
>From the man page:
Expose the host CPUs configuration to the guest. This enables
the
** Summary changed:
- [trusty] 3.13.0-68 raid6-pq panic in raid6_avx21_gen_syndrome() while probing
grub devices (was: Xenial KVM: updating Trusty guest from 3.13.0-68 to
3.13.0-71 causes kernel exception)
+ [Xenial] KVM trusty guest 3.13.0-68 raid6-pq panic in
raid6_avx21_gen_syndrome() while
Ok I attempted to reproduce without success. What I tried:
- Xenial on Xenial on machine/guest with avx2
- Trusty 3.13.0-{68,71} on Xenial on machine/guest with avx2
In both of these instances I modprobed raid6_pq, in the trusty instance
I triggered an upgrade from 68 to 71 and neither of these
On my Trusty VM with "[x] Copy host CPU configuration" checked in virt-
manager, running 'sudo modprobe -r raid6_pq && sudo modprobe raid6_pq'
is enough to reproduce the kernel exception in dmesg (though I didn't
see it print "Segmentation Fault", so that may be somewhat of a red
herring).
Here's
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kvm (Ubuntu)
Status: New => Confirmed
--
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
It affects me, trying to bootstrap xenial vm on xenial, getting OOPS
like above.
# virt-install --name $SHORT \
--ram $MEM \
--vcpus $CPUS \
--location=http://hk.archive.ubuntu.com/ubuntu/dists/xenial/main/installer-amd64/
\
--os-type=linux --os-variant=virtio26
17 matches
Mail list logo
