There doesn't seem to be a reason for IOMMUs not to be handled
by this function.

Signed-off-by: Andrea Bolognani <abolo...@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 a3f0a27058..0618343b79 100644
--- a/src/conf/domain_conf.c
+++ b/src/conf/domain_conf.c
@@ -29708,6 +29708,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;
@@ -29720,7 +29724,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

Reply via email to