Features/VirtioSCSI: Difference between revisions

From QEMU
Line 26: Line 26:
** Patches on mailing list
** Patches on mailing list
** http://www.redhat.com/archives/libvir-list/2012-January/msg00537.html
** http://www.redhat.com/archives/libvir-list/2012-January/msg00537.html
* SeaBIOS support
** Patches on mailing list


= Future tasks =
= Future tasks =

Revision as of 13:25, 16 February 2012

Overview

A virtio storage interface for efficient I/O that overcomes virtio-blk limitations and supports advanced SCSI hardware.

Features

  • /dev/sda inside guest
  • Multiple LUNs per PCI adapter, solves virtio-blk 1:1 scalability problem
  • SCSI passthrough (tape, CD burning, ...)

Status

Future tasks

  • Pick up vhost-scsi work again:
    • Port QEMU hw/virtio-scsi.c vhost-scsi support onto latest code
    • add QEMU Object Model (QOM) support to the vhost-scsi device
    • Port LIO vhost-scsi code onto latest lio.git code
    • Update vhost-scsi to implement latest virtio-scsi device specification
    • Ensure vhost-scsi I/O still works
    • Design libvirt integration for LIO
  • QEMU SCSI target:
    • Add support for WRITE SAME commands
    • Add support for rerror/werror to scsi-generic
  • Complete virtio-scsi spec implementation:
    • Add support for hotplug events
    • Add support for asynchronous media change notifications
    • Multi-queue (with fine-grained locking in the Linux driver?)
  • Use cases to test:
    • CD-ROM/DVD burning passthrough
    • Tape passthrough
    • 100s of LUNs (scalability)
  • Use cases to flesh out:
    • LUN hotplug (known to work with manual hotplug)
    • Multipath inside guest
  • Performance analysis
    • Compare against virtio-blk I/O (rough numbers: 6% slower on iozone with a tmpfs-backed disk)
    • Compare passthrough performance against bare metal host SCSI
    • Measure scalability and where the bottlenecks are (full virtqueues? locks?)

Links