[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897555#comment-15897555
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8239:
--------------------------------------------

Github user nathanejohnson commented on the issue:

    https://github.com/apache/cloudstack/pull/1955
  
    Also, I just made a commit, I have not squashed it because I wanted to get 
some feedback.  I noticed that vmware uses details to pass rootDiskController 
for the bus type, and there was even some code that inspected this in the kvm 
plugin.  With this latest commit, it will actually honor either OS type "Other 
PV Virtio-SCSI" or rootDiskController passed in via details, with details 
overriding OS type.  I also made a minor tweak to the UI to allow setting the 
root disk bus via the add template dialog in the UI:
    
    
![template_screen](https://cloud.githubusercontent.com/assets/1360240/23617743/b29b8dd6-0253-11e7-970b-6aafe314bd49.png)
    
    So this way you can select virtio scsi by one of the following three ways:
    
    1) selecting os type as "Other PV Virtio-SCSI (64 bit)"
    2) uploading a template and specifying details[0].rootDiskController=scsi, 
either from the UI or the API, then creating a VM from this template
    3) deploying a VM and specifying details[0].rootDiskController=scsi , 
currently only available via the API
    



> Add support for VirtIO-SCSI for KVM hypervisors
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-8239
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8239
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: KVM, Storage Controller
>    Affects Versions: 4.6.0
>         Environment: KVM
>            Reporter: Andrei Mikhailovsky
>            Assignee: Wido den Hollander
>            Priority: Critical
>              Labels: ceph, gsoc2017, kvm, libvirt, rbd, storage_drivers, 
> virtio
>             Fix For: Future
>
>
> It would be nice to have support for virtio-scsi for KVM hypervisors.
> The reason for using virtio-scsi instead of virtio-blk would be increasing 
> the number of devices you can attach to a vm, have ability to use discard and 
> reclaim unused blocks from the backend storage like ceph rbd. There are also 
> talks about having a greater performance advantage as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to