I tried to remove RDM disk from VM but it failed with an error “invalid configuration for device 0”. I have usually seen this message related with vNIC but this time it was the disk.
After some searching I found a solution – I changed SCSI ID from 0:1 to 0:2 for the disk I wanted to remove. After that remove operation worked.
I’ve recently extended my home lab with additional capacity. In addition to my Windows Server + VMware Workstation (info here) I’ve added refurbished HPE DL380 G7 server with following configuration:
1 x Intel Xeon Processor X5650 2.66Ghz
will add SSD in the future
The added server is running VMWare ESXi 6.7. It hosts vCenter 6.7 appliance and also few virtual ESXi 6.7 instances. HPE G7 series servers are not officially supported by VMWare to run ESXi 6.7 but it seems to be working for now.
I found my refurbished HPE G7 server from Ebay.
Recently I deployed some VMs from an template which I had created some years ago. When I tried to update VMWare Tools I received an error “The required VMWare Tools ISO image does not exist or is inaccessible.”
After some digging around in Google I found a thread in VMware forums which also pointed me to a right direction. I had set following advanced option in VM configuration – isolation.tools.autoInstall.disable = TRUE.
To allow VMWare Tools ISO mounting I set the value from TRUE to FALSE.
I recently changed from Windows based VMware Update Manager (VUM) to Update Manager which is embedded in to the appliance of vCenter. In old VUM I had increased host reboot timeouts to allow host firmware patching during reboot without timing out remediation job. In appliance the vci-integrity.xml file located in “/usr/lib/vmware-updatemgr/bin”. You need to restart VUM service or appliance after the change.
Lines which need to be change are following:
Changed the values to:
This change allows me to patch ESXi host and install new firmware’s with a same reboot and with as least operations as possible.
I was installing a new ESXi and after some steps I got an error “Illegal OpCode” while booting. It happened after ESXi patching with VUM. After some debugging I found the issue.
The server had local storage where I created a VMFS datastore before patching. In BIOS boot order was CD/DVD ROM, Hard Disk and USB. ESXi was installed onto USB. The error happened when server tried to boot from disk which contained VMFS datastore. After I moved USB before Hard Disk in boot order server booted correctly.
I saw an article in The Register that Dell EMC will discontinue the software-only version of ScaleIO and you can only get it if you buy it together with hardware (VxRack Flex). Today I tried searching Dell EMC website for ScaleIO downloads but all the links redirected to Dell EMC’s Converged Infrastructure homepage. Seems Dell EMC has removed the possibility download ScaleIO from their website.
ScaleIO is a software-defined storage product. It converts direct-attached storage into shared block storage over LAN.
More info: wikipedia
I got a question about using Windows Defender Credential Guard in VMware virtual machines. I did some digging and found following things:
Info from https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements
Windows Defender Credential Guard requires:
- Support for Virtualization-based security (required)
- Secure boot (required)
- TPM 2.0 either discrete or firmware (preferred – provides binding to hardware)
- UEFI lock (preferred – prevents attacker from disabling with a simple registry key change)
The Virtualization-based security requires:
- 64-bit CPU
- CPU virtualization extensions plus extended page tables
- Windows hypervisor
As of today only VMware Workstation 14 has option to enable Virtualization-based security. I created a case to VMWare where I inquired about support for Virtualization-based security in vSphere and answer I got that it will be available in the future version.
Update: VMWare has now released vSphere 6.7 which supports Virtualization-based security options.