[pve-devel] scsihw / hotplug integration into GUI
Stefan Priebe - Profihost AG
s.priebe at profihost.ag
Mon Aug 13 13:02:25 CEST 2012
as virtio-scsi-pci is supported in guest since 3.4 wouldn't it make
sense to change scsi-hd to scsi-generic for all guests where scsihw is
set to virtio-scsi-pci and the host stgt interface is recent enough?
Am 13.08.2012 12:42, schrieb Stefan Priebe - Profihost AG:
> Am 13.08.2012 12:19, schrieb Alexandre DERUMIER:
>>>> But scsi-block needs at least the following patch as it misses some
>>>> implemtations. Otherwise you can't start a hd with scsi-block.
>> (yes, I want to said when qemu-kvm 1.2 will be release)
>>> - but scsi-generic seem faster (but need guest 3.4 ?)
>>>> Will check / recheck this.
>> In fact, virtio-scsi drivers are only available since kernel 3.4.
> OK so scsi-generic can't work before ;-) But then we can do
> autodetection. If somebody has scsihw: virtio-scsi-pci the scsi-generic
> should be available.
>> Can you try:
>> lsi controller + libiscsi + scsi-generic vs scsi-block
>> lsi controller + open-scsi (host) + scsi-generic vs scsi-block
> NO real difference lsi is always SLOW (around 2000-5000 max iops)
>> virtio-scsi controller + libiscsi + scsi generic vs scsi-block
> scsi-block is the same performance as scsi-hd (maxed 20.000 iops) vs.
> 50.000 iops with scsi-generic.
>> virtio-scsi controller + open-scsi (host) + scsi-generic vs scsi-block
> I can't get that running as i don't know how to pass the open-iscsi
> device to the guest.
> pve-devel mailing list
> pve-devel at pve.proxmox.com
More information about the pve-devel