30 May, 2011 KVM provides a Virtio interface for the virtual hard disk and NIC. To use them in a Windows guest VM, the drivers from (you only need the ISO file) must first be installed into Windows. To install them in a Windows guest VM, it must also be started with these interfaces so that Windows can detect them. ![]() Fedora cannot ship Windows virtIO drivers because they cannot be. The latest driver builds. The builds may be bug free. - QEMU PCI serial device driver. Download add ons, extensions, service packs, and other tools to use with your Windows software. Updating the VirtIO Drivers (Windows. Download the VirtIO ISO file from. Scroll down to Drivers and Tools and then continue scrolling to everRun VirtIO Driver. ![]() While the Windows guest could be started with the Virtio NIC without any problems, we can not start with the Windows image (i.e. The virtual hard disk image where Windows is installed on your guest VM) using the Virtio hard disk interface (until the driver is installed, Windows will not know how to use the Virtio hard disk interface). The easiest solution to this problem is to create another virtual disk that can use Virtio: qemu-img create -f qcow2 Now, start the Windows VM with the Virtio interfaces: qemu-kvm -hda -drive file=,if=virtio -drive file=,media=cdrom,index=1 -net nic,model=virtio -net user -boot d -vga std -m 1024 When Windows is loaded in your guest VM, go in to the Device Manager. Under Other Devices, there should be two entries – one for the SCSI controller to the the temporary virtual hard drive and the other for the Virtio network card. On one of the items, right click on it and select Properties, go to the Driver tab. You should now see the following: Click on Update Driver. In the next dialog, choose to specify a location and install the Red Hat Virtio drivers. The dialogs for installing the drivers will vary, depending on the installed version of Windows. It should be fairly easy to work how to install the drivers, but installing the drivers for Windows 7 and Windows XP are here if you need them (). Installing the Drivers on Windows XP For Windows XP, choose Install from a list or specific location on the first prompt. On the next set of options, choose Search for the best driver in these locations and ensure that Search removable media is ticked and click on Next again. When installing the hard disk controller, you might be prompted, at this point, to choose a driver. At this point, choose the one in the wxp directory. Eventually, you will probably be warned that you are installing an unsigned driver. Select Continue Anyway to install the driver. When installation is complete, you should get a confirmation, similar to the following: After repeating the steps for the other driver, you use the Virtio interface on your Windows hard disk image (see ). Installing the Drivers on Windows 7 For Windows 7, choose Browse my computer for driver software. On the next screen, choose the drive for your CDROM. You should be able to let Windows search the CD for the drive. When prompted, confirm that you want to install the driver. There will be a confirmation that the driver was installed, similar to this one: Close the dialog and repeat the steps for the other driver. After Installing the Drivers After both drivers are installed, the device manager should contain a Red Hat VirtIO device for the SCSI controller and another one for the ethernet adapter. Next time you start the guest VM, you can use the Virtio interface for the Windows image: qemu-kvm -drive file=,if=virtio -net nic,model=virtio -net user -vga std -m 1024 Your Windows VM is now using the Virtio interfaces for your Windows virtual hard drive and NIC. If you wish to know more about Virtio and how it works, I suggest having a read of the article. We are running a Windows Server 2008 system as a 'guest' on a Linux-KVM virtual server (SLES11, with VirtIO support). We have trouble with the system performance and this is possibly due to not using the VirtIO drivers. I don't have much experience with neither KVM nor VirtIO. Just heard it this could be the reason for our problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2018
Categories |