VMPOOL & TECH BLOG

Purpose This article guides you through the process of increasing the size of a virtual disk. This procedure is necessary to accommodate data requirements that have changed since the creation of the virtual disk. Resolution Important information before you begin Even though this article provides steps to increase the size of your virtual disk, the size of the disk partition does not increase as observed inside the guest operating system. You must follow steps related to your specific operating system to increase the size of the disk partition(s). For more information, see  Increasing the size of a disk partition (1004071) . Caution : VMware recommends that you back up your virtual machine before increasing the size of virtual disks. The procedure for increasing the size of a virtual disk differs between VMware products. Follow the section below that matches your product. In all cases, confirm the following before increasing the size of the virtual disk: Al

Purpose This article explains VMware's position on its support for running Fusion 3 on Mac OS X Lion, and the compatibility guidelines. Resolution VMware Fusion 4.x supports OS X 10.7 (Lion) as both a host and a guest operating system. For more information, see the VMware Fusion home page .   VMware Fusion 3.1.4 was designed for OS X 10.5 (Leopard) and OS X 10.6 (Snow Leopard). It is compatible with Mac OS X 10.7 (Lion), with some limitations. VMware Fusion 3.x is incompatible with Mac OS X 10.8 (Mountain Lion). VMware Fusion 2.x is incompatible with Mac OS X 10.7 (Lion). If you are running an older version of VMware Fusion, upgrade to VMware Fusion 3.1.4 before upgrading to Lion. For the best experience, reinstall Fusion after upgrading to Lion. When running Fusion on Lion, these limitations are known to exist: VMware Fusion 3.1.3 virtual machines do not start in Mac OS X 10.7.4 or later. For more information, see   Fusion 3.1.3 virtual machines fail to start af

Purpose This article explains the host machine hardware and firmware requirements for installing virtual machines with 64-bit guest operating systems. Note : 64-bit guests are not supported for ESX versions 2.5.x and earlier. For information about installing Guest Operating Systems, see the  Guest Operating System Installation Guide . Resolution VMware's virtual machine monitor has traditionally used segmentation to provide isolation between the guest operating system and the virtual machine monitor. This is necessary because the guest operating system and virtual machine monitor share the linear address space. To determine whether or not your CPU is suitable for running 64-bit guest operating systems, VMware distributes a free utility. You can download the tool from our web site:  Processor Check for 64-Bit Compatibility  . Note : This utility is provided without support from VMware and does not require ESX/ESXi, VMware Server or VMware Workstation to perform

Symptoms Cannot convert a Windows physical machine Converting a Windows physical machine fails You see the error: Unable to create a VSS snapshot In Windows Event Viewer, you see the error: Service Control Manager Event ID 7000 The Vstor2 P2V230 Virtual Storage Driver service failed to start due to the following error: The system cannot find the path specified  Cause This issue occurs if the previous agent installation was not removed correctly and  Vstor2P2V30.sys  is installed and continues to exist from a previous conversion attempt with Converter 3.0. Resolution To workaround this issue: Click  Start > Run , type devmgmt.msc, and click  OK . The Device Manager window opens. Click  View  >  Show Hidden Devices . Expand  Non-Plug and Play Devices . Locate  Vstor2 P2V30 Virtual Storage Driver .  Right-click  Vstor2 P2V30 Virtual Storage Driver  and click  Uninstall. Reference http://kb.vmware.com

If you’re running the free version of ESXi 5.0 in your homelab or testing it at work, you might be wondering what’s the easy way to upgrade existing ESXi 5.0 installation to the latest ESXi 5.1 without much effort and without breaking your existing installation, without re-installing everything. Your existing VMs won’t be affected. I’ve already wrote about patching ESXi without vCenter, but this time the command used slightly differ, and here I’m showing you the the steps which needs to be accomplished to upgrade to the latest ESXi 5.1 version. More advanced users can skip, because they’ll probably know this method. This article is meant to be for every user who don’t uses vSphere update manager for this process. I’m writing it down here for my own bookmarking needs as well. -:) As you might already read in my article about the changes to the ESXi, there isn’t any vRAM limitation on the free ESXi 5.1 but there is still the 2 physical CPU limit together with the 32Gb physical RA