Installing the virtio drivers is probably the best option, but is
going to remain our last resort because it has further
implications like a larger maintenance window. Thanks for pointing
us towards the W2016 virtio drivers.
Your last email was a little unclear to me. Would you expect a performance boost by changing bus='ide' to bus='scsi'? For instance changing this:
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source
file='/var/data/virtuals/machines/windows-server-2016-x64/image.qcow2'/>
<backingStore/>
<target dev='hda' bus='ide'/>
<alias name='ide0-0-0'/>
<address type='drive' controller='0' bus='0' target='0'
unit='0'/>
</disk>
to the following:
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source
file='/var/data/virtuals/machines/windows-server-2016-x64/image.qcow2'/>
<backingStore/>
<target dev='hda' bus='scsi'/>
<address type='drive' controller='0' bus='0' target='0'
unit='0'/>
</disk>
Do you see any gotchas in this configuration that could prevent
the virtualized guest to power on and boot up?
On Tue, Jun 20, 2017 at 10:29 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
That said, I don't know what is the level of support for W2016 at time with virtio and virtio-scsi drivers.You can download iso and virtual floppy images here:
This message below just posted at ovirt-users mailing list so that for drivers you can use this iso, that seems supporting W2016 (not tested myslef yet):Gianluca