Symptoms:
Upgrading virtual hardware in ESX 4 may cause Windows 2008 disks to go offline.
Upgrading virtual hardware from version 4 to version 7 may cause Windows 2008 disks to go offline.
Creating a new virtual machine on hardware version 7 may cause Windows 2008 disks to go offline.
Note: The first disk (C: drive) is not affected. Any additional disks may be affected and show marked as Offline within Disk Management.
Read more…
What’s New
The following information provides highlights of some of the enhancements available in this release of VMware ESX:
VMware View 4.0 support – This release adds support for VMware View 4.0, a solution built specifically for delivering desktops as a managed service from the protocol to the platform.
Windows 7 and Windows 2008 R2 support –This release adds support for 32-bit and 64-bit versions of Windows 7 as well as 64-bit Windows 2008 R2 as guest OS platforms. In addition, the vSphere Client is now supported and can be installed on a Windows 7 platform. For a complete list of supported guest operating systems with this release, see the VMware Compatibility Guide.
Read more…
Details:
If you plan to use Windows 7 or Windows 2008 R2 as a guest operating system, do not use the SVGA drivers included with VMware Tools. Use the standard SVGA driver instead.
Symptoms:
Freeze
Hanging Console
High CPU
Reboots
Solution:
To deselect the SVGA drivers installed with VMware Tools:
- When you install VMware Tools, select VMware Tools Custom Install and deselect the SVGA driver.
Alternatively, remove the SVGA driver from the Device Manager after installing VMware Tools
Product Versions:
VMware ESX 4.0.x
VMware ESXi 4.0.x Installable
Source: KB 1011709
After upgrading from VMware ESX 3.x to ESX 4.0 you can cleanup the bootloader from the older ESX 3.5 installation. You can do this from the console of by connection the host with ssh, give the command “cleanup-esx3”
Little note: You can run the cleanup-esx command as long as everything works for you in 4. If you use the -f flag, the software prompts you to confirm that you want to disable the ability to roll back to the ESX 3.x.x.
Thanks xchello from Dutch VMug for the tip!
To use Microsoft Windows Cluster Service in VMware ESX you need to config you’r VM’s with independent persistent disks.
VM configuration:
I deployed two Windows 2003 SP2 Enterprise 32-Bit VM’s with both 12 GB of OS disks and two NIC’s. I called these: VMPROS-CL01 and VMPROS-CL02.
VMPROS-CL01 with ip: 172.16.254.78 and for MSCS nic ip: 1.0.0.1
VMPROS-CL01 with ip: 172.16.254.89 and for MSCS nic ip: 1.0.0.3
Registered this VM’s in domain VMpros.nl
Read more…
After moving some Windows 2003 and 2008 VM’s from 3.5 hosts to 4.0 hosts the network adapter is now shown as a removable device in the "Safely remove hardware" on the Windows task bar.
To resolve this:
- VM: Edit Settings
- Options
- Select General
- Configuration Parameters…
- Add Row
- Name: devices.hotplug
- Value: false
Source: VMware KB
The VMware KB 1003926 is very helpful to support problems with your VirtualCenter Server service that won’t start. VMware updated this document 2 September 2009.
Symptoms
- You cannot connect to VirtualCenter
- If you try to connect to VirtualCenter, you see the error:
Cannot connect to host <server>: No connection could be made because the target machine actively refused it.
- If you try to start the VMware VirtualCenter Server service, you may see the errors:
Read more…
“Unable to connect to the MKS: Failed to connect to the server 172.16.254.202:902” or “Unable to connect to the MKS: Failed to connect to the server no such host is known”
Solution:
To avoid losing access to the ESX host, perform the following steps:
1. Add the ESX server in your DNS
2. Edit your hostfile on the workstation (C:\Windows\System32\Drivers\etc\hosts\) and add your ESX server
After adding the ESX by DNS in my hostfile and restarted the VI Client I was able to open Console screen.
[ad#ad-banner]
