[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2019-07-24 Thread Brad Figg
** Tags added: cscc -- 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/1682077 Title: nested KVM fails - KVM: entry failed, hardware error 0x0 Status in linux package in Ubuntu:

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2019-02-24 Thread Martin Pitt
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 Kernel Packages,

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2019-01-22 Thread Gianpietro Lavado
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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2018-11-17 Thread fransiscus bimo
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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2018-01-26 Thread Yan Chen
Running into the same as well. Is there any workaround on this? -- 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/1682077 Title: nested KVM fails - KVM: entry failed, hardware error 0x0

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2018-01-08 Thread Kai
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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2017-12-05 Thread Ujwal Setlur
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 Kernel

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2017-12-05 Thread Joseph Salisbury
** Tags removed: 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/1682077 Title: nested KVM fails - KVM: entry failed, hardware error 0x0 Status in linux package in

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2017-12-05 Thread Manikandan R
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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2017-04-24 Thread Iain Lane
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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2017-04-24 Thread Seth Forshee
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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2017-04-24 Thread Joseph Salisbury
** 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/1682077 Title: nested KVM fails - KVM: entry failed, hardware error 0x0 Status

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2017-04-13 Thread Seth Forshee
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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2017-04-12 Thread Iain Lane
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

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2017-04-12 Thread Joseph Salisbury
** 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: