let wondows 2016 work with virtio on kvm/virtualizor ?
on my virtualizor/kvm,
i create vm with windows installed,
it's bus is ide by default.
i try to
(1) yum install virtio-win on my centos 7 node
(2) add a new device for my windows vm and install driver for it (download the driver from https://fedoraproject.org/wiki/Windows_Virtio_Drivers)
but when i change the booted hdd's bus from original ide to virtio,
the windows can not bootable,
it shows blue and blank screen.
i try to download a windows 2016 iso to my node and boot the vm from the iso,
i reinstall the windows manually and load the driver from the Windows_Virtio_Drivers
(1) when i set the hdd's bus as virtio,it can not find driver
(2) when i set the hdd's bus as scsi,it can find the driver and make install.
is it normal ?
because i wonder if i can use virtio for the bus ? or just scsi ? or both virtio and scsi are the same ?
I always prefer virtio to make it simple
@MSIUD Try using the windows template offered by virtualizor . Contact them over ticket or via skype if you need the template
yes,i download the windows template,
with setting the default bus as ide,
it is bootable.
but when i change the bus to virtio,
it will not be bootable.
is it possible i lose any setting ?
You can't just change things like that after installation and expect it to work. You'd want to slipstream them into your image and set it up before install, because trying to change the entire subsystem used at install is a hell of a lot more involved than it was in 2003.
I was about to say that I had never heard of "wondows 2016" ...
I think Packard Bell owns it these days.
i mean windows server 2016.
WHAT? How can you never heard of the famous Wondows 2016 by Macrosoft?
I need this wondows 2016, sounds pretty sick.
"Wondows 2016" sounds like the official North Korea clone.
"I'm so ronery" is the startup song and loads straight into Starcraft.
Easiest way: Install using IDE, add a 2nd image disk of 1GB with virtio... boot and install virtio drivers. Now change ide to virtio...
yes,i use this way,but sometime boots well and sometimes fail.
it never fails, man. Maybe you haven't selected the proper boot order