There doesn't seem to be a reason for IOMMUs not to be handled
by this function.
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
src/conf/domain_conf.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/conf/domain_conf.c b/src/conf/domain_conf.c
index df51d59e0d..60f2b1129f 100644
--- a/src/conf/domain_conf.c
+++ b/src/conf/domain_conf.c
@@ -29588,6 +29588,10 @@ virDomainDeviceDefCopy(virDomainDeviceDef *src,
virDomainShmemDefFormat(&buf, src->data.shmem, flags);
rc = 0;
break;
+ case VIR_DOMAIN_DEVICE_IOMMU:
+ virDomainIOMMUDefFormat(&buf, src->data.iommu);
+ rc = 0;
+ break;
case VIR_DOMAIN_DEVICE_VSOCK:
virDomainVsockDefFormat(&buf, src->data.vsock);
rc = 0;
@@ -29600,7 +29604,6 @@ virDomainDeviceDefCopy(virDomainDeviceDef *src,
case VIR_DOMAIN_DEVICE_SMARTCARD:
case VIR_DOMAIN_DEVICE_MEMBALLOON:
case VIR_DOMAIN_DEVICE_NVRAM:
- case VIR_DOMAIN_DEVICE_IOMMU:
case VIR_DOMAIN_DEVICE_LAST:
virReportError(VIR_ERR_INTERNAL_ERROR,
_("Copying definition of '%d' type "
--
2.31.1