I want to change some settings on my vCenter VM, but it's version 10. When I connect the version 5.5 VIC to the host, and try to manage it, says you need to use the web client to change the settings on VMs that are version 10 or higher.
Specifically I want to change the SCSI controller from LSI to VMware Paravirtual. Which requires that the VM be off. How can I work around this?
Hi
As described in this KB VMware KB: Editing virtual machine settings fails with the error: You cannot use the vSphere client ... to work around this you can use PowerCLI and PowerCLI can connect ESXi host directly.
To change SCSI controller type you can use cmdlets Set-ScsiController vSphere 5.5 Documentation Center - Set-ScsiController
LucD also has posted a blog about changing SCSI Controller to Paravirtual with PowerCLI available here: Switching to the Paravirtual SCSI Controller - LucD notes
Here's some script that I just tested
Get-VM vm1 | Get-HardDisk
CapacityGB Persistence Filename
---------- ----------- --------
2.000 Persistent [ds1] vm1/vm1.vmdk
1.000 Persistent [ds1] vm1/vm1_1.vmdk
$disks = get-vm vm1 | Get-HardDisk
Get-ScsiController -HardDisk $disks
Type BusSharingMode UnitNumber
---- -------------- ----------
VirtualLsiLogicSAS NoSharing 3
VirtualLsiLogicSAS NoSharing 4
Let say you want to change the 2nd controller
Get-VM vm1 | Get-ScsiController | where {$_.UnitNumber -eq "4"} | Set-ScsiController -Type ParaVirtual
Hope this helps
Hi Friend,
From VC 5.5, any new feature is only supported on web client. VM with hardware version 10 is introduced in VC 5.5. As you have already vCenter 5.5, web client is already comes with vCenter bundle. If you have used Simple install, web client is installed by default. If it was not simple install, plz install web client by connecting vCenter ISO again.
(You might be knowing below details already but I am not assuming)
Once it is installed, open IE/chrome/firefox &
- open this URL "https://<THE IP of web client installed machine>:9443"
- You will be asked for username/password.
- Enter the username /password : same that you used for logging into VIC.
Now you can edit your VM settings. I believe, there is no work around from VIC.
Hi
As described in this KB VMware KB: Editing virtual machine settings fails with the error: You cannot use the vSphere client ... to work around this you can use PowerCLI and PowerCLI can connect ESXi host directly.
To change SCSI controller type you can use cmdlets Set-ScsiController vSphere 5.5 Documentation Center - Set-ScsiController
LucD also has posted a blog about changing SCSI Controller to Paravirtual with PowerCLI available here: Switching to the Paravirtual SCSI Controller - LucD notes
Here's some script that I just tested
Get-VM vm1 | Get-HardDisk
CapacityGB Persistence Filename
---------- ----------- --------
2.000 Persistent [ds1] vm1/vm1.vmdk
1.000 Persistent [ds1] vm1/vm1_1.vmdk
$disks = get-vm vm1 | Get-HardDisk
Get-ScsiController -HardDisk $disks
Type BusSharingMode UnitNumber
---- -------------- ----------
VirtualLsiLogicSAS NoSharing 3
VirtualLsiLogicSAS NoSharing 4
Let say you want to change the 2nd controller
Get-VM vm1 | Get-ScsiController | where {$_.UnitNumber -eq "4"} | Set-ScsiController -Type ParaVirtual
Hope this helps
Hrm, that didn't quite work.
PowerCLI C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI> Get-VM vcenter01 | Get-ScsiController | where {$_.UnitNumber -eq "3"} | Set-ScsiController -Type ParaVirtual
Set-ScsiController : 05/14/2014 1:11:14 PM Set-ScsiController The operation for the entity "vcenter01" failed with the following message: "Access to resource settings on the host is restricted to the server that is managing it: '172.x.y.z'."
At line:1 char:77
+ Get-VM herkvcenter02 | Get-ScsiController | where {$_.UnitNumber -eq "3"} | Set- ...
+ ~~~~
+ CategoryInfo : NotSpecified: (:) [Set-ScsiController], HostAccessRestrictedToManagementServer
+ FullyQualifiedErrorId : Client20_TaskServiceImpl_CheckServerSideTaskUpdates_OperationFailed,VMware.VimAutomation.ViCore.Cmdlets.Commands.VirtualDevice.SetScsiController
Of course, the "server that is managing it" is the very server I'm attempting to change.
Edit - this behavior is intended. This is the fix - VMware KB: Changing the hard disk mode of a virtual machine fails with the error: Access to resource...
It's working!
Another option is to edit vmx file although I think is unsupported .
Edit VM vmx file
change line
virtualHW.version = "10"
to
virtualHW.version = "9"
And you will be able to edit setting with C# client
Hope this helps you somehow
