Feeds:
Posts
Comments

Archive for August, 2010

Problem

I moved a virtual machine by storage vmotion between two ESX servers. (The servers are not a part of a cluster)

After the storage vmotion ended, I couldn’t powered on the virtual machine and I received the following error:

Cannot open the disk. Reason: The parent virtual disk has been modified since the child was created

Solution

  1. Open SSH connection to the ESX server which the virtual machine is on (by putty)
  2. From the vSphere client, stand on the virtual machine > right click > Edit Settings > Options > General Options > Virtual Machine Working Location (This is the path of the virtual machine)
  3. From the Putty connection, Navigate to the virtual’s machine path /vmfs/volumes /and the path from paragraph 2
  4. From the folder of the virtual machine perform the following:

             1.Cat VM_Name-000001.vmdk (according to the error massage you have received)

  • The file which end with *.000000x.vmdk is the snapshot file.
  • Look for the parentCID and write it down.

             2.Cat VM_Name.vmdk (according to the error massage you have received)

  • This is the original / source file.
  • Look for the CID and write it down.
  1. Compare the snapshot parentCID and the source disk CID, in case they are different this is the problem.
  2. Open nano on the snapshot file as follow: nano VM_Name-000001.vmdk
  3. Change the parentCID to the ID that was written in the source disk under CID
  4. Save the changes (ctrl+x, y, Enter)
  5. Make sure the change has saved >  cat VM_Name-000001.vmdk
  6. Start the virtual machine.

 

Idit.

Read Full Post »

 

Problem

I created a virtual machine (object) in Hyper-V Manager, and when I tried to start the virtual machine, I received the following error: The virtual machine could not be started because the hypervisor is not running.

Solution

I restated the Hyper-V server , and entered its BIOS. In the BIOS under processor options I have noticed that the Virtualization Technology is disabled.

I enabled that option and afterwards everything was back to normal.

Idit.

Read Full Post »

Problem

Suddenly our vSphere client stopped responding (version 4 Build 208111) and all virtual machines appeared as “grayed out” . We restarted the following services in our vCenter server:

  • VMware VirtualCenter Server
  • VMware VirtualCenter Management Webservices

But it didn’t helped, and afterwards we couldn’t even login to our vSphere client.

 Solution

We connected to the vCenter server and looked at the vpxd log which exist in the following path: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs

And saw the following error:

We immediately restarted the VMware License Server and everything was OK.

Idit.

Read Full Post »

Problem

I have installed VMware Workstation 6.5.4 on top of Windows 2008 R2, and while I tried to resume one of my virtual machines (which I moved to Suspended State), I’ve received the following error: Cannot find a valid peer process to connect to.

Solution

1. Open task manager and kill vmware-auth.exe process.

2. Open services.msc as administrator (Right Click on Services > Open as Administrator) and restart “VMware Authorization service”

3. Refresh the VMware Workstation page and try again.

4. Fixed!

Idit.

Read Full Post »

Problem

I was logged in to Windows 2003 SP2 server with an administrative user  account which is administrator on the server, but when I have trired to install acerain software I received the following error:

Windows cannot access the specified device path or file. You may not have appropriate permissions.

 Solution

It was very odd but the solution was to uninstall “internet explorer enhanced security configuration” from : control panel > add/remove programs > add/remove windows component , and it solved the problem.

 Yaron & Idit.

Read Full Post »

Problem

When we connected to lab manager 4 web console , all virtual Machines appeared as unavailable. In addition, in the Overview page we saw the following massage: Alert! vCenter Lab Manager is Currently Not Connected to vCenter (as shown below)

We restarted the Lab Manager service but it didn’t work. We even restarted the management service of the Lab Manager ESX hosts, but it didn’t work as well.

Solution

Go to System > Settings > vCenter® , and enter the user name and password again. That worked for us!

Yaron & Idit.

Read Full Post »