Virtio - Revision history

Thuth: Remove outdated information

2022-12-15T14:38:13Z

Remove outdated information

@@ Line 4: / Line 4: @@
 * Virtio was chosen to be the main platform for IO virtualization in KVM
 * The idea behind it is to have a common framework for hypervisors for IO virtualization
-* More information (although not uptodate) can be found [[Media:KvmForum2007$kvm_pv_drv.pdf|here]]
+* The specification can be found here: https://docs.oasis-open.org/virtio/virtio/v1.2/virtio-v1.2.html
 __NOTOC__

Vdragon: fix typo

2016-10-12T05:23:01Z

fix typo

← Older revision		Revision as of 01:23, 12 October 2016
Line 5:		Line 5:
	* The idea behind it is to have a common framework for hypervisors for IO virtualization		* The idea behind it is to have a common framework for hypervisors for IO virtualization
	* More information (although not uptodate) can be found [[Media:KvmForum2007$kvm_pv_drv.pdf\|here]]		* More information (although not uptodate) can be found [[Media:KvmForum2007$kvm_pv_drv.pdf\|here]]
	* At the moment network/block/balloon devices are ~~suported~~ for kvm		* At the moment network/block/balloon devices are supported for kvm
	* The host implementation is in userspace - qemu, so no driver is needed in the host.		* The host implementation is in userspace - qemu, so no driver is needed in the host.

Vjardin: librte_pmd_virtio

2013-07-10T19:29:35Z

librte_pmd_virtio

@@ Line 35: / Line 35: @@
 ** Ping latency is 300-500 usec
 * Enjoy, more to come :)
 __NOTOC__

Mjt at 09:37, 13 August 2011

2011-08-13T09:37:07Z

← Older revision		Revision as of 05:37, 13 August 2011
Line 21:		Line 21:
	* As an alternative one can use a standard guest kernel for the guest > 2.6.18 and make use sync backward compatibility option		* As an alternative one can use a standard guest kernel for the guest > 2.6.18 and make use sync backward compatibility option
	** 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]		** 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]
	* Use ~~model=~~virtio for the network devices and if=virtio for disk		* Use virtio-net-pci device for the network devices (or model=virtio for old -net..-net syntax) and if=virtio for disk
	** Example		** Example
	<pre><nowiki>		<pre><nowiki>

Mjt: changed old -net..-net syntax to -netdev..-device

2011-08-13T09:34:26Z

changed old -net..-net syntax to -netdev..-device

← Older revision		Revision as of 05:34, 13 August 2011
Line 24:		Line 24:
	** Example		** Example
	<pre><nowiki>		<pre><nowiki>
	~~qemu/~~x86_64-softmmu/qemu-system-x86_64 -boot c -drive file=/images/xpbase.qcow2,if=virtio~~,boot=on~~ -m 384 -~~net nic,model~~=~~virtio -net~~ tap,script=/etc/kvm/qemu-ifup		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
	</nowiki></pre>		</nowiki></pre>
	* -hd[ab] for disk won't work, use -drive		* -hd[ab] for disk won't work, use -drive

Cberendt: fixed link to kvm-forum 2007 presentation

2009-05-11T16:27:48Z

fixed link to kvm-forum 2007 presentation

← Older revision		Revision as of 12:27, 11 May 2009
Line 4:		Line 4:
	* Virtio was chosen to be the main platform for IO virtualization in KVM		* Virtio was chosen to be the main platform for IO virtualization in KVM
	* The idea behind it is to have a common framework for hypervisors for IO virtualization		* The idea behind it is to have a common framework for hypervisors for IO virtualization
	* More information (although not uptodate) can be found ~~in kvm~~ [~~http~~:~~//kvm.qumranet.com/kvmwiki/~~KvmForum2007~~?action=[[AttachFile]]&do=get&target=~~kvm_pv_drv.pdf ~~pv driver~~]		* More information (although not uptodate) can be found [[Media:KvmForum2007$kvm_pv_drv.pdf\|here]]
	* At the moment network/block/balloon devices are suported for kvm		* At the moment network/block/balloon devices are suported for kvm
	* The host implementation is in userspace - qemu, so no driver is needed in the host.		* The host implementation is in userspace - qemu, so no driver is needed in the host.

Jeremy.perry@redhat.com at 14:21, 11 March 2009

2009-03-11T14:21:26Z

← Older revision		Revision as of 10:21, 11 March 2009
Line 1:		Line 1:
	= Paravirtualized drivers for kvm/Linux =		=Virtio=

			== Paravirtualized drivers for kvm/Linux ==
	* Virtio was chosen to be the main platform for IO virtualization in KVM		* Virtio was chosen to be the main platform for IO virtualization in KVM
	* The idea behind it is to have a common framework for hypervisors for IO virtualization		* The idea behind it is to have a common framework for hypervisors for IO virtualization
Line 6:		Line 8:
	* The host implementation is in userspace - qemu, so no driver is needed in the host.		* The host implementation is in userspace - qemu, so no driver is needed in the host.

	= How to use Virtio =		== How to use Virtio ==
	* Get kvm version >= 60		* Get kvm version >= 60
	* Get Linux kernel with virtio drivers for the guest		* Get Linux kernel with virtio drivers for the guest

WikiSysop: Reverted edits by WikiSysop (Talk); changed back to last version by AnthonyLiguori

2008-12-02T18:09:27Z

Reverted edits by WikiSysop (Talk); changed back to last version by AnthonyLiguori

← Older revision		Revision as of 14:09, 2 December 2008
Line 1:		Line 1:
	t~~'''est123'''~~		= Paravirtualized drivers for kvm/Linux =
			* Virtio was chosen to be the main platform for IO virtualization in KVM
			* The idea behind it is to have a common framework for hypervisors for IO virtualization
			* More information (although not uptodate) can be found in kvm [http://kvm.qumranet.com/kvmwiki/KvmForum2007?action=[[AttachFile]]&do=get&target=kvm_pv_drv.pdf pv driver]
			* At the moment network/block/balloon devices are suported for kvm
			* The host implementation is in userspace - qemu, so no driver is needed in the host.

			= How to use Virtio =
			* Get kvm version >= 60
			* Get Linux kernel with virtio drivers for the guest
			** Get Kernel >= 2.6.25 and activate (modules should also work, but take care of initramdisk)
			*** CONFIG_VIRTIO_PCI=y (Virtualization -> PCI driver for virtio devices)
			*** CONFIG_VIRTIO_BALLOON=y (Virtualization -> Virtio balloon driver)
			*** CONFIG_VIRTIO_BLK=y (Device Drivers -> Block -> Virtio block driver)
			*** CONFIG_VIRTIO_NET=y (Device Drivers -> Network device support -> Virtio network driver)
			*** CONFIG_VIRTIO=y (automatically selected)
			*** CONFIG_VIRTIO_RING=y (automatically selected)
			*** you can safely disable SATA/SCSI and also all other nic drivers if you only use VIRTIO (disk/nic)
			* As an alternative one can use a standard guest kernel for the guest > 2.6.18 and make use sync backward compatibility option
			** 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]
			* Use model=virtio for the network devices and if=virtio for disk
			** Example
			<pre><nowiki>
			qemu/x86_64-softmmu/qemu-system-x86_64 -boot c -drive file=/images/xpbase.qcow2,if=virtio,boot=on -m 384 -net nic,model=virtio -net tap,script=/etc/kvm/qemu-ifup
			</nowiki></pre>
			* -hd[ab] for disk won't work, use -drive
			* Disk will show up as /dev/vd[a-z][1-9], if you migrate you need to change "root=" in Lilo/GRUB config
			* At the moment the kernel modules are automatically loaded in the guest but the interface should be started manually (dhclient/ifconfig)
			* 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.
			* Expected performance
			** Performance varies from host to host, kernel to kernel
			** On my laptop I measured 1.1Gbps rx throughput using 2.6.23, 850Mbps tx.
			** Ping latency is 300-500 usec
			* Enjoy, more to come :)

			__NOTOC__

WikiSysop at 12:43, 2 December 2008

2008-12-02T12:43:48Z

← Older revision		Revision as of 08:43, 2 December 2008
Line 1:		Line 1:
	~~= Paravirtualized drivers for kvm/Linux =~~		t'''est123'''
	* Virtio was chosen to be the main platform for IO virtualization in KVM
	* The idea behind it is to have a common framework for hypervisors for IO virtualization
	* More information (although not uptodate) can be found in kvm [http://kvm.qumranet.com/kvmwiki/KvmForum2007?action=[[AttachFile]]&do=get&target=kvm_pv_drv.pdf pv driver]
	* At the moment network/block/balloon devices are suported for kvm
	* The host implementation is in userspace - qemu, so no driver is needed in the host.

	~~= How to use Virtio =~~
	* Get kvm version >= 60
	* Get Linux kernel with virtio drivers for the guest
	** Get Kernel >= 2.6.25 and activate (modules should also work, but take care of initramdisk)
	*** CONFIG_VIRTIO_PCI=y (Virtualization -> PCI driver for virtio devices)
	*** CONFIG_VIRTIO_BALLOON=y (Virtualization -> Virtio balloon driver)
	*** CONFIG_VIRTIO_BLK=y (Device Drivers -> Block -> Virtio block driver)
	*** CONFIG_VIRTIO_NET=y (Device Drivers -> Network device support -> Virtio network driver)
	*** CONFIG_VIRTIO=y (automatically selected)
	*** CONFIG_VIRTIO_RING=y (automatically selected)
	*** you can safely disable SATA/SCSI and also all other nic drivers if you only use VIRTIO (disk/nic)
	* As an alternative one can use a standard guest kernel for the guest > 2.6.18 and make use sync backward compatibility option
	** 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]
	* Use model=virtio for the network devices and if=virtio for disk
	** Example
	~~<pre><nowiki>~~
	~~qemu/x86_64-softmmu/qemu-system-x86_64 -boot c -drive file=/images/xpbase.qcow2,if=virtio,boot=on -m 384 -net nic,model=virtio -net tap,script=/etc/kvm/qemu-ifup~~
	~~</nowiki></pre>~~
	* -hd[ab] for disk won'~~t work, use -drive~~
	* Disk will show up as /dev/vd[a-z][1-9], if you migrate you need to change "root=" in Lilo/GRUB config
	* At the moment the kernel modules are automatically loaded in the guest but the interface should be started manually (dhclient/ifconfig)
	* 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.
	* Expected performance
	** Performance varies from host to host, kernel to kernel
	** On my laptop I measured 1.1Gbps rx throughput using 2.6.23, 850Mbps tx.
	** Ping latency is 300-500 usec
	* Enjoy, more to come :)

	~~__NOTOC__~~

AnthonyLiguori at 13:57, 28 April 2008

2008-04-28T13:57:48Z

← Older revision		Revision as of 09:57, 28 April 2008
Line 17:		Line 17:
	*** CONFIG_VIRTIO_RING=y (automatically selected)		*** CONFIG_VIRTIO_RING=y (automatically selected)
	*** you can safely disable SATA/SCSI and also all other nic drivers if you only use VIRTIO (disk/nic)		*** you can safely disable SATA/SCSI and also all other nic drivers if you only use VIRTIO (disk/nic)
	* Either build it around Rusty's tree [http://ozlabs.org/~rusty/kernel/hg/ repo]		* As an alternative one can use a standard guest kernel for the guest > 2.6.18 and make use sync backward compatibility option
	** Or git clone git://kvm.qumranet.com/home/dor/src/linux-2.6-nv use branch rusty
	** Soon an official repository will be released
	** As an alternative one can use a standard guest kernel for the guest > 2.6.18 and make use sync backward compatibility option
	** 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]		** 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]
	* Use model=virtio for the network devices and if=virtio for disk		* Use model=virtio for the network devices and if=virtio for disk