Paravirtualized block device: Difference between revisions
From KVM
No edit summary |
No edit summary |
||
(One intermediate revision by one other user not shown) | |||
Line 2: | Line 2: | ||
== Host side == | == Host side == | ||
run kvm with command-line: -drive file=<path_to_your_raw_qemu_img>,if=virtio | run kvm with command-line: <code>-drive file=<path_to_your_raw_qemu_img>,if=virtio</code> | ||
you can also specify boot=on in the command-line: -drive file=<path_to_your_raw_qemu_img>,if=virtio,boot=on | you can also specify boot=on in the command-line: <code>-drive file=<path_to_your_raw_qemu_img>,if=virtio,boot=on</code> | ||
== Guest side == | == Guest side - Linux == | ||
sudo modprobe virtio_blk | sudo modprobe virtio_blk | ||
to have virtio_blk driver, you need to upgrade the kernel to higher than 2.6.25. | to have <code>virtio_blk</code> driver, you need to upgrade the kernel to higher than 2.6.25. | ||
refer to [[Virtio]] | refer to [[Virtio]] | ||
== Guest side - Windows == | |||
You can find Windows drivers at [[Downloads]] page. |
Latest revision as of 04:08, 17 April 2010
Paravirtualized Block Device
Host side
run kvm with command-line: -drive file=<path_to_your_raw_qemu_img>,if=virtio
you can also specify boot=on in the command-line: -drive file=<path_to_your_raw_qemu_img>,if=virtio,boot=on
Guest side - Linux
sudo modprobe virtio_blk
to have virtio_blk
driver, you need to upgrade the kernel to higher than 2.6.25.
refer to Virtio
Guest side - Windows
You can find Windows drivers at Downloads page.