** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682077
Title:
nested KVM fails - KVM: entry failed, hardware error 0x0
To manage notifications about this bug go to:
This happens in about half of the xenial semaphoreci.com instances as
well:
$ uname -a
Linux semaphore-light-1809b 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12
15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Reproduced in Intel(R) Xeon(R) Gold 5120 CPU @ 2.20GHz
Ubuntu 16.04.5 LTS
4.4.0-134-generic
libvirt 4.0.0
QEMU 4.0.0
Running hypervisor: QEMU 2.11.1
Nested KVM not working, instances log "KVM: entry failed, hardware error
0x0"
--
You received this bug notification because you are a member of
I am sorry if this bug is to old, but i have this problem and cannot
find the solution until now.
I can reproduce this bug with following HW:
Ubuntu 16.04.5 LTS
Kernel 4.4.0-131-generic
libvirtd (libvirt) 1.3.1
QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.32)
Intel(R) Xeon(R) Gold
Running into the same as well.
Is there any workaround on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682077
Title:
nested KVM fails - KVM: entry failed, hardware error 0x0
To manage
Changing the script to be used with xenial instead of trusty:
https://gist.github.com/kmindi/4fb1332509a39b6214b0e8b39611f5ad
I can also confirm the bug on the following hardware configuration:
CPU Model - Skylkake (Intel(R) Xeon(R) Gold 5115 CPU @ 2.40GHz)
L0 and L1:
Ubuntu 16.04.3 LTS
Kernel
The last time something like this was fixed was
https://bugs.launchpad.net/bugs/1329434. The fix was to disable APIC
virtualization in nested guests. Did it suddenly get turned on again?
Any patches we could test? Thanks.
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682077
Title:
nested KVM fails - KVM: entry failed, hardware error 0x0
To manage notifications about this bug go to:
Facing the same issue with KVM enabled L2 VM on following setup
CPU Model - Skylake-Client
L0:
Ubuntu 16.04.3 LTS
Kernel - 4.4.0-98-generic & 4.4.0-101-generic
libvirtd (libvirt) 2.5.0-3ubuntu5.5~cloud0
QEMU emulator version 2.8.0(Debian 1:2.8+dfsg-3ubuntu2.5~cloud0)
L1:
Ubuntu 16.04.3 LTS
Maybe IS happens to have a box that's not provisioned yet and you can
borrow? Or you can borrow that one for a bit if lgw01 has some spare
capacity? Or they'll upgrade to the current lts-xenial kernel so we
maybe get lucky. :)
--
You received this bug notification because you are a member of
Stefan Bader and I have continued trying to reproduce this. Here's what
we've done:
- Tried to reproduce on various pieces of hardware available to us.
- Requested the hardware information about the host machine from IS and tested
on the most similar machine available to us (same generation Xeon
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682077
Title:
nested KVM fails - KVM: entry failed, hardware error 0x0
To manage
Adding some miscellaneous data points.
I'm still unable to reproduce this outside of a lgw01 compute node that
Laney set up for me, running xenial with qemu 1:2.5+dfsg-5ubuntu10.10
and linux 4.4.0-72. It doesn't happen on every host. I'm still
experimenting to see if I can reproduce this on some
For me it's enough to boot an instance on an affected lgw01 compute
node, install qemu-system-x86, download a cloud image and run "/usr/bin
/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -drive
format=raw,cache=unsafe,file=zesty-server-cloudimg-amd64.img -machine
accel=kvm -enable-kvm
** Changed in: linux-lts-xenial (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added:
We hit this late last week too, I'm having difficulty reproducing it
though. smb thinks there could be some issue with checks failing for
feature bits not passed into the guest because they were new and thus
perhaps a problem when using pretty recent hardware.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-xenial (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682077
arges wrote a script in bug #1329434 which might be enough to repro
this, but I don't have access to the hw myself to test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682077
Title:
nested KVM
Hmm, that's a non current kernel - I wonder if someone can test with the
current lts-xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682077
Title:
nested KVM fails - KVM: entry failed,
19 matches
Mail list logo
