No edit summary |
No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 18: | Line 18: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/17 | Fedora 17 ]] | * Targeted release: [[Releases/17 | Fedora 17 ]] | ||
* Last updated: 2011-07 | * Last updated: 2011-02-07 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
== Detailed Description == | == Detailed Description == | ||
| Line 28: | Line 28: | ||
== Scope == | == Scope == | ||
The guest driver will be included as part of the distribution's kernel and as part of the seabios ROMs installed together with QEMU. The host drivers will be included in the qemu package. | The guest driver will be included as part of the distribution's kernel and as part of the seabios ROMs installed together with QEMU. The host drivers will be included in the qemu package. For Fedora 17, management tools based on libvirt will not support this yet. <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
== How To Test == | == How To Test == | ||
| Line 59: | Line 59: | ||
== Documentation == | == Documentation == | ||
Since libvirt did not make the F17 deadline and documentation was supposed to be there, it still has to be written. <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | |||
== Release Notes == | == Release Notes == | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
KVM | KVM supports a new advanced SCSI-based storage stack, virtio-scsi. Right now, virtio-scsi can be used on guests running Fedora 17. It will be included in the mainline kernel starting at release 3.4. | ||
== Comments and Discussion == | == Comments and Discussion == | ||
Latest revision as of 07:33, 27 March 2012
virtio-scsi
Summary
A new storage architecture for KVM based on SCSI.
Owner
- Name: Paolo Bonzini
- Email: pbonzini@redhat.com
Current status
- Targeted release: Fedora 17
- Last updated: 2011-02-07
- Percentage of completion: 100%
Detailed Description
virtio-scsi improves the storage stack in terms of scalability (easily overcomes the current limit of ~30 freely hot-pluggable/unpluggable storage devices), flexibility (support features such as SCSI passthrough or persistent reservations), extensibility (exposing new features to the guest does not require updating drivers in both the host and the guest).
Benefit to Fedora
Fedora users will be able to use an industry-standard storage stack for their virtual machines.
Scope
The guest driver will be included as part of the distribution's kernel and as part of the seabios ROMs installed together with QEMU. The host drivers will be included in the qemu package. For Fedora 17, management tools based on libvirt will not support this yet.
How To Test
- Install the qemu-kvm package.
- Download an install image for this release of Fedora (network or DVD).
- Prepare a large file to be used as the disk for a Fedora virtual machine.
- Use the following command to install Fedora:
qemu-kvm -drive if=none,id=hd,file=/path/to/test.img -device virtio-scsi-pci,id=scsi --enable-kvm -device scsi-hd,drive=hd -cdrom /path/to/boot.iso. - Reboot and test that the virtual machine can boot from the virtio-scsi hard disk.
- Use the following command to (re)install Fedora:
qemu-kvm -drive if=none,id=cd,file=/path/to/boot.iso -device scsi-cd,drive=cd,bootindex=0 -drive if=none,id=hd,file=/path/to/test.img -device virtio-scsi-pci,id=scsi --enable-kvm -device scsi-hd,drive=hd. The virtual machine will boot from the virtio-scsi image.
Dependencies
None.
Contingency Plan
Each piece (kernel, qemu, libvirt) can be included separately, so there is no need to revert partial changes.
Documentation
Since libvirt did not make the F17 deadline and documentation was supposed to be there, it still has to be written.
Release Notes
KVM supports a new advanced SCSI-based storage stack, virtio-scsi. Right now, virtio-scsi can be used on guests running Fedora 17. It will be included in the mainline kernel starting at release 3.4.