IC. The Windows E1000 driver is unreliable with
> > VMware's emulation, so we'd like to switch to VMXNET3 for all Windows
> VMs.
> > Setting the nicAdapter detail worked as expected, at least.
> >
> >
> > Any suggestions?
> >
> >
> > Regards,
> >
: Andrija Panic
Sent: 17 May 2019 11:45:40
To: users
Subject: Re: Changing the NIC and disk controller type permanently
Gregor,
I already shared the solution for existing VMs - for any new VMs to be
deployed from some template, please change the template details and specify
the rootController
ble with
> VMware's emulation, so we'd like to switch to VMXNET3 for all Windows VMs.
> Setting the nicAdapter detail worked as expected, at least.
>
>
> Any suggestions?
>
>
> Regards,
>
> Gregor
>
> ________
> From: Andrija Panic
To: users
Subject: Re: Changing the NIC and disk controller type permanently
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
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
> $ cloudstack addResourceDetail "details[0].key=rootDiskController"
> "details[0].value=lsisas1068" "resourcetype=UserVm" "resourceid=$id"
Note: lsisas1068 comes from
https://github.com/apache/cloudstack/blob/4.11.2.0/vmware-base/src/com/cloud/hypervisor/vmware/mo/ScsiDiskControllerType.java
Hi,
This is an old topic, [1] but it looks like behaviour changed in newer
CloudStack versions.
What is the recommended procedure to change the NIC and disk controller
types of an existing VM (in stopped state)?
We used
$ cloudstack addResourceDetail "details[0].key=rootDiskController"
: Disk controller type
** This mail originated from OUTSIDE the Oakford corporate network. Treat
hyperlinks and attachments in this email with caution. **
Hi Adam,
Glad you solved the problem! But I need to say this work sounds "crazy" in a
sense that this is not (per my knowledge) how
ryone's help and suggestions
>
> Adam
>
>
> -Original Message-
> From: Andrija Panic
> Sent: 21 September 2018 16:50
> To: users
> Subject: Re: Disk controller type
>
> ** This mail originated from OUTSIDE the Oakford corporate network. Treat
> hyperli
the VM and all is good
Thanks for everyone's help and suggestions
Adam
-Original Message-
From: Andrija Panic
Sent: 21 September 2018 16:50
To: users
Subject: Re: Disk controller type
** This mail originated from OUTSIDE the Oakford corporate network. Treat
hyperlinks and attachments
ptember 21, 2018 5:28 AM
> To: users@cloudstack.apache.org
> Subject: RE: Disk controller type
>
> Win 2016 doesn’t use Virtio by default, but we need too as disk
> performance is rubbish if we don’t
>
>
>
>
> -Original Message-
> From: Andrija Panic
> S
From: Adam Witwicki
Sent: Friday, September 21, 2018 5:28 AM
To: users@cloudstack.apache.org
Subject: RE: Disk controller type
Win 2016 doesn’t use Virtio by default, but we need too as disk performance is
rubbish if we don’t
-Original Message-
From
Win 2016 doesn’t use Virtio by default, but we need too as disk performance is
rubbish if we don’t
-Original Message-
From: Andrija Panic
Sent: 21 September 2018 11:25
To: users
Subject: Re: Disk controller type
** This mail originated from OUTSIDE the Oakford corporate network
--Original Message-
> From: Andrija Panic
> Sent: 20 September 2018 11:18
> To: users
> Subject: Re: Disk controller type
>
> ** This mail originated from OUTSIDE the Oakford corporate network. Treat
> hyperlinks and attachments in this email with caution. **
>
> So
Subject: RE: Disk controller type
** This mail originated from OUTSIDE the Oakford corporate network. Treat
hyperlinks and attachments in this email with caution. **
Ok, I have found were to force the controller type for a VM
Set this is the user_vm_details table
idvm_idnamevaluedisplay
: 20 September 2018 11:18
To: users
Subject: Re: Disk controller type
** This mail originated from OUTSIDE the Oakford corporate network. Treat
hyperlinks and attachments in this email with caution. **
Sooo... here is my experience:
if using correct VirtIO OS TYPE (set on template/VM) - i.e
cki wrote:
>
>
> It looks like I can just add
>
> rootDiskController virtio
>
> To the templates settings tab?
>
> Can anyone confirm?
>
> Thanks
>
> Adam
>
> -Original Message-
> From: Ivan Kudryavtsev
> Sent: 20 September 2018 10:20
>
It looks like I can just add
rootDiskController virtio
To the templates settings tab?
Can anyone confirm?
Thanks
Adam
-Original Message-
From: Ivan Kudryavtsev
Sent: 20 September 2018 10:20
To: users
Subject: Re: Disk controller type
** This mail originated from OUTSIDE
Controler depends on setyings, specified in template or os family used. So
Windows guests don't receive virtio for network and storagr, thus they can
be deployed without additional drivers.
чт, 20 сент. 2018 г., 16:19 Ivan Kudryavtsev :
> Rakesh, It doesn't work like that for CS as it uses
Rakesh, It doesn't work like that for CS as it uses stateless XML configs.
чт, 20 сент. 2018 г., 16:12 Rakesh Venkatesh :
> I think you can change the controller type in XML file of the VM but not
> sure if that works or not.
>
> virsh dumpxml
> virsh edit
> change the controller type, save
I think you can change the controller type in XML file of the VM but not
sure if that works or not.
virsh dumpxml
virsh edit
change the controller type, save and start the vm again
On Thu, Sep 20, 2018 at 9:59 AM Adam Witwicki
wrote:
> Hello,
>
> I have a number of of instances using the
Hello,
I have a number of of instances using the wrong controller type (ATA) does
anyone know where this is set in the database so I can start them with the
VirtIO scsi controller?
Thanks
Adam
Disclaimer Notice:
This email has been sent by Oakford Technology Limited, while we have checked
22 matches
Mail list logo
