cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrija Panic <>
Subject Re: Changing the NIC and disk controller type permanently
Date Fri, 17 May 2019 06:30:22 GMT
Hi Gregor,

the code around managing VM details for existing VMs (CONTROLLER
specifically) could be a bit better - but in short - there is NO way to
change existing controller type from the current ones (for VMware
specifically) using CloudStack (btw you "can" make the change in the GUI,
while VM is stopped - there is a  "Settings" tab there.)

You "can" change these details on the VM level (existing VMs) via API/GUI,
this changes the records in the "user_vm_details" table - but simply these
new values are NOT read/applied during starting an existing VM - actually,
even when you change that in GUI (or DB) and start a VM - these values will
be reverted back.

I just did more tests - and the way to change it would be to stop VM, go to
vCenter, change (all 4 controllers)  to " LSI Logic SAS" (or any other you
want) - then go back to CloudStack and edit VM details (Settings tab, while
VM is stopped) to "lsisas1068" - simply to sync ACS to reality (to vCenter).

Make sure to do proper testing, since changing root controller driver in
Windows can sometimes cause it to fail boot.


On Thu, 16 May 2019 at 21:44, Riepl, Gregor (SWISS TXT) <> wrote:

> > $ cloudstack addResourceDetail "details[0].key=rootDiskController"
> > "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id"
> Note: lsisas1068 comes from
> We had set this to lsilogicsas previously (on CS 4.5), which causes the
> following exception on start on CS
> Invalid root disk
> controller detected : none
>         at
>         at
>         at
>         at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$
> ...


Andrija Panić

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message