[
https://issues.apache.org/jira/browse/CLOUDSTACK-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276432#comment-14276432
]
ASF subversion and git services commented on CLOUDSTACK-4787:
-------------------------------------------------------------
Commit a4cc987a6f66f20c434942956fffe5951df09e43 in cloudstack's branch
refs/heads/vmware-disk-controllers from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a4cc987 ]
CLOUDSTACK-4787 Allow selection of scsi controller type in vSphere
commit #7
So far only 1 controller (scsi or ide) is supported in Cloudstack for ide or
scsi, this is existing limitation. Added support for 2nd IDE controller.
Support adding IDE
virtual disk to VM. Also added check if VM is running as IDE virtual disk
cannot be attached
to VM if VM is runnning.If user detaches a virtual disk on lower unit
number of controller,
then subsequent attach operation should find free unit number on the
controller and attach
the virtual disk there.
commit #6
Let the controllers of existing VMs continue without flip, current busInfo
retrieved from
chain_info field of volume record from database would be preferred over
controller settings from all configuration settings.
commit #5
Editing global configuration param vmware.root.disk.controller osdefault
value results
in loss of previous root disk controller type. Hence root disk's controller
type for legacy
VMs is unknow post that modificaiton by user. If VM is stop/start then we
could get this
infromation from bus info of existing volume. But if user resets VM and
then try to start VM.
The existing bus info would be lost. Hence existing disk info is not
available to depend on.
Using lsilogic or generic scsi controller for ROOT disk of legacy VMs if
reset.
commit #4
Avoid adding additional (>1) scsi controllers to system vms. While
attaching volume to legacy VM
don't use osdefault optoin which applicable only for VM created with the
option enabled, use
legacy data disk controller type (lsilogic)
commit #3
If root disk's controller type is scsi and data disk controller type
condenses
to any of scsi sub-types then data disk controller type would fall back to
root disk controller itself. This
ensures data volumes would be accessible in all cases as controller of root
volume would be reliable
and it means VM has the supported controller. It also avoids mix of scsi
controller sub-types in a user instance.
Also translating disk controller type scsi to lsilogic.
commit #2
Support auto detection of recommended virtual disk controller type for
specific guest OS.
commit #1
Support granual controller types. Add support for controller types in
template registration as well.
Fix white spaces.
Removed stale HEAD merge lines
Removed tail of merge lines
Fixed VmwareResource, removing storage commands that moved to
VmwareStorageProcessor.
removed stale code of controller that is present in processor
Fixed check style errors.
Fixed injection.
Tested with Linux and windows templates. Unable to run iso based tests due
to few bugs in register iso area.
Signed-off-by: Sateesh Chodapuneedi <[email protected]>
> Allow selection of scsi controller type in vSphere
> --------------------------------------------------
>
> Key: CLOUDSTACK-4787
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4787
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, UI, VMware
> Affects Versions: 4.2.0, 4.3.0
> Environment: vSphere 5.1
> Reporter: Chris Sciarrino
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.6.0
>
>
> When adding an OVA template for a vSphere environment allow the selection of
> the scsi controller type.
> Currently the instances are deployed with the the LSI Parallel controller
> type. This results in a blue screen on boot when attempting to deploy
> templates that use the LSI SAS controller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
