Status: New
Owner: ----
New issue 706 by [email protected]: Please support virtio-scsi (and/or
-drive if=none for a general use case)
http://code.google.com/p/ganeti/issues/detail?id=706
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
Software version: 2.9.2
Internode protocol: 2090000
Configuration format: 2090000
OS api version: 20
Export interface: 0
VCS version: v2.9.2
hspace (ganeti) version v2.9.2
compiled with ghc 7.6
running on linux x86_64
What distribution are you using?
Debian Jessie (testing)
What steps will reproduce the problem?
1. disk_type (which is more or less synonym for the "if=" option in the
qemu -drive parameter) only allows for paravirtual, pflash, scsi, ide, mtd,
sd.
What is the expected output? What do you see instead?
Having the option for a disk_type of "virtio-scsi", however this is not
drive interface option but needs to be mapped with something akin to this:
"-drive if=none,id=hd,file=/path/to/image
-device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd"
Please provide any additional information below.
Among the many advantages of virtio-scsi is the fact that it supports
TRIM/DISCARD and unlike the qemu IDE interface is nearly as fast as
virtio-blk.
Anybody wanting to use TRIM/DISCARD in a production environment won't use
IDE as it is 3-4 times slower than virtio-blk.
While having a "disk_type=virtio-scsi" option in ganeti is definitely the
desirable outcome, being able to define a disk_type of "none" (qemu -drive
if=none) should also be taken into consideration, as it will allow for any
other and future backends to be supported by inserting the
correct "-device " parameters via the ganeti kvm_extra configuration
parameter.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
