Public bug reported:
[Impact]
A guest will hang while booting under 4.18.0-10.11 because of "kvm: x86: Set
highest physical address bits in non-present/reserved SPTEs", which came in via
4.18.y.
[Test Case]
A guest was booted after applying the patch.
[Regression Potential]
It might break KVM on systems with different physical memory limits, which is
just what upstream might have been testing the most.
============
A fix is already upstream, and already present in 4.18.14.
This would be upstream commit
daa07cbc9ae3da2d61b7ce900c0b9107d134f2c1 ("KVM: x86: fix L1TF's MMIO GFN
calculation").
** Affects: linux (Ubuntu)
Importance: High
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Cosmic)
Importance: High
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Description changed:
- A guest will hang while booting under 4.18.0-10.11 because of "kvm: x86:
- Set highest physical address bits in non-present/reserved SPTEs", which
- came in via 4.18.y.
+ [Impact]
+ A guest will hang while booting under 4.18.0-10.11 because of "kvm: x86: Set
highest physical address bits in non-present/reserved SPTEs", which came in via
4.18.y.
+
+ [Test Case]
+ A guest was booted after applying the patch.
+
+ [Regression Potential]
+ It might break KVM on systems with different physical memory limits, which is
just what upstream might have been testing the most.
+
+ ============
A fix is already upstream, and already present in 4.18.14.
- This would be upstream commit
+ This would be upstream commit
daa07cbc9ae3da2d61b7ce900c0b9107d134f2c1 ("KVM: x86: fix L1TF's MMIO GFN
calculation").
--
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/1798427
Title:
kvm doesn't work on 36 physical bits systems
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
[Impact]
A guest will hang while booting under 4.18.0-10.11 because of "kvm: x86: Set
highest physical address bits in non-present/reserved SPTEs", which came in via
4.18.y.
[Test Case]
A guest was booted after applying the patch.
[Regression Potential]
It might break KVM on systems with different physical memory limits, which is
just what upstream might have been testing the most.
============
A fix is already upstream, and already present in 4.18.14.
This would be upstream commit
daa07cbc9ae3da2d61b7ce900c0b9107d134f2c1 ("KVM: x86: fix L1TF's MMIO GFN
calculation").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798427/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
