Don't think you have to use the ISO Domain any longer. You can upload to a Data Domain and when you highlight the VM in the management GUI, select the three dots in the top left for extra options and there is a change cd option. That option will allow for attaching an ISO from a Data Domain. That is what I recall when I was using oVirt a month or so ago. ________________________________________ From: eevans(a)digitaldatatechs.com <eevans(a)digitaldatatechs.com&gt; Sent: Wednesday, March 25, 2020 2:28 PM To: 'Shareef Jalloq'; users(a)ovirt.org Subject: [ovirt-users] Re: Windows VirtIO drivers You have to copy the iso and vfd files to the ISO domain to make them available to the vm’s that need drivers. engine-iso-uploader options list # engine-iso-uploader options upload file file file Documentation is found here: https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html Eric Evans Digital Data Services LLC. 304.660.9080 [cid:image001.jpg@01D602B1.9FEA2EC0] From: Shareef Jalloq <shareef(a)jalloq.co.uk&gt; Sent: Wednesday, March 25, 2020 1:51 PM To: users(a)ovirt.org Subject: [ovirt-users] Windows VirtIO drivers Hi, it seems the online documentation regarding the windows installation steps is well out of date. Where is there any current documentation on where to get the VirtIO drivers for a Windows installation? From a bit of Googling, it seems that I need to 'yum install virtio-win' on the engine VM and then copy the relevant .iso/.vfd to the ISO domain. Is that correct? Where is the documentation maintained and how do I open a bug on it? Thanks, Shareef.