Re: [Engine-devel] Issues with VirtIO-SCSI
Hi Vitor,
The new VirtIO-SCSI enabled checkbox is an indication whether to
attach a VirtIO-SCSI controller when running the VM.
It should be enabled automatically on cluster >= 3.3.
When disabled, I think it's preferable not to add a new controller
automatically when running the VM as it requires creating/attaching
a new VmDevice - which we refrain of on VmInfoBuilder flows
(and since it might be confusing to the user...).
As an alternative, I've planned to add a warning in the dialog
or create a canDo message to prevent running the VM at all.
I'm not sure we should hide the option from disk interfaces
list as it's already being filtered using VirtIoScsiEnabled
ConfigurationValue (and using OsInfo soon...).
Let me know what you think and thanks a lot for the input!
Daniel
----- Original Message -----
From: "Vitor de Lima" <vitor.lima(a)eldorado.org.br>
To: engine-devel(a)ovirt.org
Sent: Monday, September 23, 2013 10:42:39 PM
Subject: [Engine-devel] Issues with VirtIO-SCSI
Hi everyone,
I have found some issues with this patch:
http://gerrit.ovirt.org/#/c/18638/
It allows the user to disable the VirtIO-SCSI disk interface during the VM
creation. The problem is that the user still can add, attach and hotplug
disks with the VirtIO-SCSI interface type, but when the user does so,
libvirt automatically creates a LSI Logic SCSI controller and connects the
new disk to it.
How can this problem be solved? Should the VirtIO-SCSI interface type be
hidden from the user in case it wasn't enabled, or should the engine enable
the VirtIO-SCSI controller, hotplug it, then hotplug the disk into it
transparently?
Thanks,
Vitor de Lima
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel