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. Management tools based on libvirt should support this too. <!-- 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?-->

+

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 ==

−

Documentation will be included as part of the changes to libvirt. <!-- 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. -->

+

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 and libvirt support a new advanced SCSI-based storage stack, virtio-scsi. Right now, virtio-scsi can be used on guests running Fedora 17. It should be included in the mainline kernel starting at release 3.4.

+

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.

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).

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.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of
Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community
maintained site. Red Hat is not responsible for content.