Merge "libvirt: Stop unconditionally enabling evmcs"
This commit is contained in:
commit
f315c5658e
|
@ -28051,7 +28051,10 @@ class LibvirtDriverTestCase(test.NoDBTestCase, TraitsComparisonMixin):
|
|||
self.assertTrue(hv.reenlightenment)
|
||||
self.assertTrue(hv.tlbflush)
|
||||
self.assertTrue(hv.ipi)
|
||||
self.assertTrue(hv.evmcs)
|
||||
# NOTE(artom) evmcs only works on Intel hosts, so we can't enable it
|
||||
# unconditionally. Until we become smarter about it, just don't enable
|
||||
# it at all. See bug 2009280.
|
||||
self.assertFalse(hv.evmcs)
|
||||
|
||||
|
||||
class LibvirtVolumeUsageTestCase(test.NoDBTestCase):
|
||||
|
|
|
@ -6265,7 +6265,6 @@ class LibvirtDriver(driver.ComputeDriver):
|
|||
hv.reenlightenment = True
|
||||
hv.tlbflush = True
|
||||
hv.ipi = True
|
||||
hv.evmcs = True
|
||||
|
||||
# NOTE(kosamara): Spoofing the vendor_id aims to allow the nvidia
|
||||
# driver to work on windows VMs. At the moment, the nvidia driver
|
||||
|
|
|
@ -0,0 +1,8 @@
|
|||
---
|
||||
fixes:
|
||||
- |
|
||||
Bug 2009280 has been fixed by no longer enabling the evmcs enlightenment in
|
||||
the libvirt driver. evmcs only works on Intel CPUs, and domains with that
|
||||
enlightenment cannot be started on AMD hosts. There is a possible future
|
||||
feature to enable support for generating this enlightenment only when
|
||||
running on Intel hosts.
|
Loading…
Reference in New Issue