https://linux-kvm.org/api.php?action=feedcontributions&feedformat=atom&user=Vdragon 2026-04-05T23:13:50Z User contributions MediaWiki 1.39.5 https://linux-kvm.org/index.php?title=WindowsGuestDrivers/Download_Drivers&diff=173843 2017-10-17T20:46:37Z

<p>Vdragon: Update new Git repo address according to README</p> <hr /> <div>= Windows VirtIO Drivers =<br /> <br /> The source for the Windows drivers is hosted in a repository on GIT hub. Anonymous users can clone the repository<br /> <br /> git clone git://github.com/virtio-win/kvm-guest-drivers-windows.git<br /> <br /> [https://github.com/virtio-win/kvm-guest-drivers-windows Browse GIT repository online ]<br /> <br /> <br /> == Binary Drivers ==<br /> <br /> Binary drivers are provided by some Linux distributions including WHQL Certified drivers.<br /> <br /> For example the binary drivers for Ubuntu can be found [https://launchpad.net/kvm-guest-drivers-windows/+download here].<br /> <br /> 64-bit versions of Windows Vista and newer (this currently includes Windows Server 2008, Windows 7, Windows 8, Windows Server 2008 R2 and Windows Server 2012) require the drivers to be [http://msdn.microsoft.com/en-us/windows/hardware/gg487332 digitally signed] to load.<br /> <br /> If your distribution does not provide binary drivers for Windows, you can use the package from the Fedora Project. These drivers are digitally signed, and will work on 64-bit versions of Windows:<br /> <br /> [https://fedoraproject.org/wiki/Windows_Virtio_Drivers Latest VirtIO drivers for Windows from Fedora ]<br /> <br /> = Code signing drivers for the Windows 64bit platforms =<br /> * Drivers should be signed for Windows 64bit platforms. <br /> * Here are some links how to self sign and install self signed drivers:<br /> ** [http://msdn.microsoft.com/en-us/library/ff547649.aspx Installing Test-Signed Driver Packages]<br /> ** [http://www.microsoft.com/whdc/driver/tips/IFS_Signing.mspx How to Release-Sign File System Drivers]</div>

Vdragon https://linux-kvm.org/index.php?title=Virtio&diff=173787 2016-10-12T05:23:01Z

<p>Vdragon: fix typo</p> <hr /> <div>=Virtio=<br /> <br /> == Paravirtualized drivers for kvm/Linux ==<br /> * Virtio was chosen to be the main platform for IO virtualization in KVM<br /> * The idea behind it is to have a common framework for hypervisors for IO virtualization<br /> * More information (although not uptodate) can be found [[Media:KvmForum2007$kvm_pv_drv.pdf|here]]<br /> * At the moment network/block/balloon devices are supported for kvm<br /> * The host implementation is in userspace - qemu, so no driver is needed in the host.<br /> <br /> == How to use Virtio ==<br /> * Get kvm version &gt;= 60<br /> * Get Linux kernel with virtio drivers for the guest<br /> ** Get Kernel &gt;= 2.6.25 and activate (modules should also work, but take care of initramdisk)<br /> *** CONFIG_VIRTIO_PCI=y (Virtualization -&gt; PCI driver for virtio devices)<br /> *** CONFIG_VIRTIO_BALLOON=y (Virtualization -&gt; Virtio balloon driver)<br /> *** CONFIG_VIRTIO_BLK=y (Device Drivers -&gt; Block -&gt; Virtio block driver)<br /> *** CONFIG_VIRTIO_NET=y (Device Drivers -&gt; Network device support -&gt; Virtio network driver)<br /> *** CONFIG_VIRTIO=y (automatically selected)<br /> *** CONFIG_VIRTIO_RING=y (automatically selected)<br /> *** you can safely disable SATA/SCSI and also all other nic drivers if you only use VIRTIO (disk/nic)<br /> * As an alternative one can use a standard guest kernel for the guest &gt; 2.6.18 and make use sync backward compatibility option<br /> ** Backport and instructions can be found in [http://www.kernel.org/pub/scm/virt/kvm/kvm-guest-drivers-linux.git kvm-guest-drivers-linux.git]<br /> * Use virtio-net-pci device for the network devices (or model=virtio for old -net..-net syntax) and if=virtio for disk<br /> ** Example<br /> &lt;pre&gt;&lt;nowiki&gt;<br /> x86_64-softmmu/qemu-system-x86_64 -boot c -drive file=/images/xpbase.qcow2,if=virtio -m 384 -netdev type=tap,script=/etc/kvm/qemu-ifup,id=net0 -device virtio-net-pci,netdev=net0<br /> &lt;/nowiki&gt;&lt;/pre&gt;<br /> * -hd[ab] for disk won't work, use -drive<br /> * Disk will show up as /dev/vd[a-z][1-9], if you migrate you need to change &quot;root=&quot; in Lilo/GRUB config<br /> * At the moment the kernel modules are automatically loaded in the guest but the interface should be started manually (dhclient/ifconfig)<br /> * Currently performance is much better when using a host kernel configured with CONFIG_HIGH_RES_TIMERS. Another option is use HPET/RTC and -clock= qemu option.<br /> * Expected performance<br /> ** Performance varies from host to host, kernel to kernel<br /> ** On my laptop I measured 1.1Gbps rx throughput using 2.6.23, 850Mbps tx.<br /> ** Ping latency is 300-500 usec<br /> * Enjoy, more to come :)<br /> <br /> == How to use get high performance with Virtio ==<br /> * get the latest drop from [http://dpdk.org/download dpdk.org]<br /> * add the [http://dpdk.org/browse/virtio-net-pmd/refs/ librte_pmd_virtio]<br /> ** Example<br /> &lt;pre&gt;&lt;nowiki&gt;<br /> testpmd -c 0xff -n 1 \<br /> -d librte_pmd_virtio.so \<br /> -- \<br /> --disable-hw-vlan --disable-rss \<br /> -i --rxq=1 --txq=1 --rxd=256 --txd=256<br /> &lt;/nowiki&gt;&lt;/pre&gt;<br /> <br /> __NOTOC__</div>

Vdragon