Reviewed: https://review.opendev.org/693072
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=c2fd8294fdb615d5229c4eb2abef1226b7cc580b
Submitter: Zuul
Branch: master
commit c2fd8294fdb615d5229c4eb2abef1226b7cc580b
Author: Boris Bobrov <bbob...@suse.com>
Date: Tue Nov 5 20:06:29 2019 +0100
Create a controller for qga when SEV is used
When a guest agent is requested, it requires a virtio-serial controller.
If the controller is not created explicitly, it will be created by
libvirt. But if AMD SEV is also requested, the controller is expected
to use the iommu driver.
In order to achive that, the controller is created explicitly with the
required driver.
Change-Id: I47c248649b9d77e8bd7c5350fc84d89342be4623
Closes-Bug: 1845986
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1845986
Title:
SEV does not enable IOMMU on SCSI controller
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) train series:
In Progress
Bug description:
https://review.opendev.org/#/c/644565/ added logic to
libvirt/designer.py for enabling iommu for certain devices where
virtio is used. This is required for AMD SEV[0]. However it missed
the case of a SCSI controller where the model is virtio-scsi, e.g.:
<controller type='scsi' index='0' model='virtio-scsi'>
As with other virtio devices, here a child element needs to be added
to the config when SEV is enabled:
<driver iommu="on" />
[0] http://specs.openstack.org/openstack/nova-
specs/specs/train/approved/amd-sev-libvirt-support.html#proposed-
change
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1845986/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
