A specified parameter was not correct spec.sharesinfo.shares

To fix the problem and edit resource allocation you should edit values directly from the virtual machine
settings.

Login in as Administrator into Vmware Virtual Center using Vmware Infrastructure client. Select the virtual machine you want to modify. Edit Settings. Click Resources tab. Modify the required resource values as required.

A general system error occurred: Source detected that destination failed to resume

Default values for disk settings in Vmware Vsphere ESXi server console are:

disk.delayonbusy 400
disk.resetlatency 1000
disk.maxresetlatency 2000

You may want to increase these values to:

disk.delayonbusy 1000
disk.resetlatency 2000
disk.maxresetlatency 4000

And perform a LIVE disk migration from one LUN to another and see if you are experiencing timeouts…

The above error was displayed in Vsphere Virtual Center client when I tried powering on ta virtual machine that was stopped for RAM changes. This virtual server was running for over a year without any problems. I was scared a bit at the beginning since it was a production server, but after restarting management agents on the Vsphere ESXi server (via console), I was able to power-on this problematic virtual machine.

Please note that this guide will also apply for SLES 11 installed on a dedicated hardware just skip the Vmware specific configuration.

Disable Vmware Tools time synchronization with the Host under “Edit settings” for the specific virtual machine. This requires virtual machine… Read the rest of this entry »

Remember, there will be downtime even if you intend to use Site Recovery Manager – in order… Read the rest of this entry »

We only use ESXi Vsphere 4 version with Standard and Advanced type licenses. All ESXi servers are connection to Virtual Center and managed from there.

1.) Download ESXi installable ISO from Vmware.com web site and burn it in CD
2.) Move all virtual servers to other ESXi hosts using vMotion or shutdown servers and use standard migration
3.) Enter ESXi host in “Maintenance mode”
4.) Disconnect FC storage uplinks
5.) Insert CD in CD… Read the rest of this entry »

• 2 physical uplink switches in failover set-up;
• 3 physical uplinks in team per each vSwitch with beacon probing enabled;
• 2 of the uplinks (each going into different uplink switch) must be active and the third physical uplink should be set-up as a Standby adapter.

Beacon probing also works if you are using Vlan trunks. The only difference is that in case of any uplink failure beacon probes will be sent to all vSwitch VLANs increasing traffic a little.

Keep in mind:

You… Read the rest of this entry »

From my own experience, CPU resources are not the bottleneck for most of the applications we are running on Vmware vSphere – it’s performance is great and CPUs are fast nowadays. We are usually running out of the RAM with our vSphere 4 ESXi servers and thus, recommend a minimum of 128GB RAM for Vmware Enterprise license powered servers and at least… Read the rest of this entry »

I guess we need to delete both these disks from the virtual machines and create a new configuration once again.

Remember that Vmware supported methods of updating ESXi servers are using vihostudate utility or burning the CD and installing from it.

Non-supported mode (and not recommended thought!) is to use “unsupported” mode and using esxupdate utility. Many folks report great success, but remember I haven’t recommended this method to you :)