Support for para-virtualized drivers is already built into all SUSE Linux Enterprise Server 11 SP1 Kernels, so virtio devices are supported out of the box. Para-virtualized drivers for SUSE Linux Enterprise Server 10 SP3 are not shipped with the product and need to be installed from a repository provided by Novell. It is recommended to install para-virtualized drivers during the installation as described in Section 5.3.1, Adding para-virtualized Drivers During the Installation. If you need to install the drivers on an existing virtual machine, follow the instructions below.
Add the para-virtualized drivers repository and the corresponding drivers update repositories with either the YaST zypper ar.module or with
Determine the flavor of the installed Kernel by running uname -r. The output string has the form Version-Flavor (for example 184.108.40.206-0.2-default).
Search for packages matching the string novell-virtio-drivers in the YaST module or with zypper se.
Install the novell-virtio-drivers package matching your Kernel flavor.
Providing para-virtualized drivers during a Microsoft Windows installation does currently not work, since the installation refuses to boot from a para-virtualized hard disk. Therefore, the para-virtualized drivers need to be installed on a running Windows installation.
The following instructions assume that the existing Windows installation uses a single IDE hard disk and a single network adapter. An ISO image containing the virtio drivers for Windows is part of the kvm package and is available on the KVM host under /usr/share/qemu-kvm/win-virtio-drivers.iso. Make this ISO image available as a CD-ROM on your virtual machine as described in Section 9.3, Ejecting and Changing Floppy or CD/DVD-ROM Media with Virtual Machine Manager. In case your virtual machine is configured without a CD-ROM device or you prefer to add a second one, see Section 9.1, Adding a CD/DVD-ROM Device with Virtual Machine Manager for setup instructions.
The following instructions show how to install para-virtualized storage
an network drivers for Windows 7. Please make sure to
exactly follow the instructions for installing the
storage drivers, otherwise your system will either completely refuse to
boot or will boot into a
IMPORTANT: Technical Support
The following instructions require to use virsh edit. Using this command in principle is not supported by the Novell Technical Support. However, this special context (Installing Para-Virtualized Storage Drivers for Windows) is an exception from this rule. It will be supported with reasonable effort.
Shut down the Windows 7 VM Guest and use Virtual Machine Manager to add an additional hard disk of type virtio (a para-virtualized hard disk). This disk is only temporarily needed and will be removed again from the VM Guest.
If necessary, use Virtual Machine Manager to adjust the must start with , otherwise the system will not boot once the system disk is para-virtualized. You need to confirm your changes with , otherwise they will not be written to the configuration.. It
Reboot the VM Guest. Once it has booted, open the devmgmt.msc followed by Enter into the field., for example, by opening the main menu and entering
Search for the entry. The entry is marked with an exclamation mark as being problematic. Right-click this entry and choose .
Install the driver. Choose to viostor\install\Win7\x86\). Confirm the security exception by clicking .. Use the button to select the directory on the driver CD containing the storage drivers for your operating system and architecture (
Once the driver installation is finished, a newnamed is listed in the . Additionally, the entry now contains the temporary para-virtualized disk. It is listed as .
Shut down the Windows 7 VM Guest and use Virtual Machine Manager to remove the temporary para-virtualized disk added earlier.
Changing the type of a virtual hard disk is currently not supported by Virtual Machine Manager—therefore the XML configuration needs to be changed directly. Open a terminal and enter the following command (replace NAME with the name of you Windows 7 VM Guest). If operating from a remote host, also specify a connection URL with the -c parameter.
virsh edit NAME
An editor (vi by default) opens. Search for a block similar to the following:
<disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/win7.raw'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk>
Remove the <address> tag. Change the attributes of the <target> tag to dev='vda' and bus='virtio':
<disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/Virtual/win7'/> <target dev='vda' bus='virtio'/> </disk>
Save the file. A successful save results in Domain NAME XML configuration edited. In case an error is reported (for example, when having produced invalid XML), the configuration has not been changed.
Restart the VM Guest. If starting it via Virtual Machine Manager, make sure the hardware change is visible in the virsh). Otherwise your changes will be overwritten with the configuration last used by Virtual Machine Manager.screen before you start (this may take a few seconds after you have saved the configuration changes from
Your Windows 7 VM Guest now uses a para-virtualized system disk.
Installing para-virtualized network drivers is very similar to installing the storage drivers:
Shut down the Windows 7 VM Guest and use Virtual Machine Manager to add an additional network adapter of type virtio (a para-virtualized network adapter). This ensures that you still have network connectivity while installing the drivers.
Reboot the VM Guest and install the driver via theas described above. The new network adapter can be found under . After a successful driver installation, a is listed in the under .
Shut down the VM Guest and remove the original, non-para-virtualized network adapter from the guest configuration using Virtual Machine Manager. Reboot the guest—now it uses a para-virtualized network adapter.
Installing para-virtualized drivers for other Windows versions is very similar to installing them on Windows 7 (see Windows 7). You do not need to manually start the — Windows will rather prompt you to install the missing drivers. Make sure to manually choose the location of the driver during the installation process.
WARNING: Para-Virtualized Storage Drivers on Windows Vista
Currently the para-virtualized storage drivers for Windows Vista do not support booting from a para-virtualized disk. Using para-virtualized storage devices for non-bootable disks is supported.
NOTE: Para-Virtualized Storage Drivers on Windows XP not Recommended
Using the para-virtualized storage drivers on Windows XP does not result in any performance gain—it may even result in performance penalties. Therefore, it is not recommended to use them. See http://firstname.lastname@example.org/msg22834.html for technical details.
Note that this only affects para-virtualized storage drivers for Windows XP! Using para-virtualized storage drivers on other Windows versions will result in better performance. Using para-virtualized network drivers on Windows XP is also beneficial.