[
https://issues.apache.org/jira/browse/CLOUDSTACK-8239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906404#comment-15906404
]
ASF GitHub Bot commented on CLOUDSTACK-8239:
--------------------------------------------
Github user nathanejohnson commented on the issue:
https://github.com/apache/cloudstack/pull/1955
I just re-depoyed and re-ran the test:
Test that libvirt properly created domain with scsi controller ... ===
TestName: test_01_verify_libvirt | Status : SUCCESS ===
ok
Verify that libvirt settings are as expected after a VM stop / start
... === TestName: test_02_verify_libvirt_after_restart | Status : SUCCESS ===
ok
Verify that libvirt settings are expected after a disk add ... ===
TestName: test_03_verify_libvirt_attach_disk | Status : SUCCESS ===
ok
Verify that guest sees scsi controller and disks ... === TestName:
test_04_verify_guest_lspci | Status : SUCCESS ===
ok
Update os type to Ubuntu, change vm details rootdiskController ... ===
TestName: test_05_change_vm_ostype_restart | Status : SUCCESS ===
ok
Verify that guest sees scsi controller and disks after switching ostype
and rdc ... === TestName: test_06_verify_guest_lspci_again | Status : SUCCESS
===
ok
----------------------------------------------------------------------
Ran 6 tests in 785.914s
OK
@wido , I believe all of your concerns should be addressed. trim is
enabled, it's using an enum and not a string, and spurious log messages have
been eliminated.
I have squashed all of the commits into one. I'm at a point where I'm
happy with the code.
> 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)
