Hi Chris,
I notice that in the class com.cloud.hypervisor.kvm.resource, Windows PV is
classified as Other PV.
s_mapper.put("Windows PV", "Other PV");
In my opinion, you can set the OS type as "Other PV". Before this, you have
to install the virtio drivers in Windows. You can see:
http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers
After that, if you change the VM configuration XML file (you can see
http://wiki.libvirt.org/page/Virtio), and start the VM, you should see from
the device manager in Windows that the NIC and disk are RedHat VirtIO
devices.
It is complicated to install the SCSI disk driver. And it does not always
work well.
For example, maybe you have to install the driver for Windows 2003 in
Windows XP (I remember this not very clear).
Kind regards,
Wei
2013/1/14 Chris Sears <chris.x.se...@sungard.com>
> Greetings,
>
> A question came up a couple days ago on the users list about provisioning
> Windows VMs with Virtio enabled on KVM:
> http://markmail.org/thread/g42vr63dolaa56yv
>
> The workaround mentioned was to set the OS Type to "Other PV". This seems
> non-optimal. Is there a better solution? Or is this a bug/enhancement?
>
> Looking around at the source, isGuestPVEnabled() seems to have a hard coded
> list of guest OS which will get virtio provisioned by default. No Windows
> OS's are in the list, presumably because the virtio drivers don't ship
> natively with Windows. Is there some other way to control what type of
> virtual NIC and disk controller hardware gets provisioned on a per-VM or
> per-template basis?
>
> Regards,
>
> - Chris
>
