This bug was fixed in the package linux - 3.13.0-36.63
---
linux (3.13.0-36.63) trusty; urgency=low
[ Joseph Salisbury ]
* Release Tracking Bug
- LP: #1365052
[ Feng Kan ]
* SAUCE: (no-up) irqchip:gic: change access of gicc_ctrl register to read
modify write.
-
** Tags added: ua
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM: entry failed, hardware error
0x0
Status in “linux” package
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
I tested and I am currently using the latest patch. It works for me.
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM: entry
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1329434
Title:
nested KVM fails on intel hardware -
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM: entry failed,
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM: entry failed, hardware
Ok a simplified patchset, I've had this work for me with limited testing:
http://people.canonical.com/~arges/lp1329434v2/
--
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/1329434
Title:
** Description changed:
[Impact]
Using nested KVM on some hypervisors doesn't work.
[Test Case]
+ A script to make this easier is posted here:
+ https://gist.github.com/arges/9d21c6da03a8c10d3980
+
1) enable nested KVM:
sudo modprobe -r kvm_intel
sudo modprobe kvm_intel nested=1
** Description changed:
[Impact]
Using nested KVM on some hypervisors doesn't work.
[Test Case]
A script to make this easier is posted here:
https://gist.github.com/arges/9d21c6da03a8c10d3980
1) enable nested KVM:
sudo modprobe -r kvm_intel
sudo modprobe kvm_intel nested=1
I have been testing the inital kernel, and so far it is looking good.
Im going to be installing the new version in just a few and will circle back
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Running newer patch. looks good so far.
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM: entry failed, hardware error
0x0
** Changed in: linux (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM:
works for me - tested it on devstack
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM: entry failed, hardware error
0x0
Status
Test kernel posted here:
http://people.canonical.com/~arges/lp1329434/
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM: entry
Another simplified version of the patch set is here:
http://people.canonical.com/~arges/lp1329434v2
--
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/1329434
Title:
nested KVM fails on
Glad to hear that a fix is in the pipeline.
I don't know anything about KVM, but I saw this the other day:
http://lkml.iu.edu/hypermail/linux/kernel/1408.0/00981.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
So I've been able to get this working with the following patches (and notes
about how I resolved the conflicts)
533558bcb69ef28aff81b6ae9acda8943575319f (remove vmx_leave_nested)
b6b8a1451fc40412c57d10c94b62e22acab28f94 (remove vmx_mpx_supported)
f4124500c2c13eb1208c6143b3f6d469709dea10 (remove
apport information
** Tags added: apport-collected uec-images
** Description changed:
[Impact]
Using nested KVM on some hypervisors doesn't work.
[Test Case]
1) enable nested KVM:
sudo modprobe -r kvm_intel
sudo modprobe kvm_intel nested=1
cat
Attached info from an affected machine.
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM: entry failed, hardware error
0x0
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
--
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/1329434
Title:
nested KVM fails on intel hardware -
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: linux (Ubuntu Trusty)
Status: New = In Progress
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided = Medium
--
You received this bug notification because you are a member
Another report on different hardware:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1278531
I've been able to test with a mainline 3.16 kernel
(dfb945473ae8528fd885607b6fa843c676745e0c)
and it worked fine. Time to bisect...
--
You received this bug notification because you are a member
Work on v3.15, so fixed in Utopic.
** Changed in: linux (Ubuntu)
Assignee: Chris J Arges (arges) = (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
v3.15rc7 fails
v3.15rc8 works
Fix is somewhere in there...
--
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/1329434
Title:
nested KVM fails on intel hardware - KVM: entry failed,
25 matches
Mail list logo
