Swizzling.org

I’ve only seen this error on a virtual machine running under VMware ESX but I dont think it’s related.
Simply go to device manager, remove the network adapter, do a scan fro new hardware and Windows will reinstall the device.

You will need to configure IP again if your using static addresses.

On more than one occasion has VMware lead to to near fatal heart attacks and one of those times which pops it head up every few months is the ol’ ESX appears disconnected in VirtualCenter but the VM’s running on it are still working fine. If you don’t use VirtualCenter then you can’t connect to it directlt via the VIclient.

Times like this you assume HA might just kick in, or maybe you should simply reboot the machine and tell everyone it was a hardware failure. Well there’s no need. Generally whats happened here is the management service has crashed resulted in you good people not being able to connect. But its generally safe to say that everything else on the host is running fine.

Solution: Log into the service console and type:

service mgmt-vmware restart

service vmware-vpxa restart

Sometimes the mgmt-vmware service can take a few minutes to restart, try to resist the urge to control+c while the service is stopping. Once restarted go back to VirtualCenter and wait, and wait, and wait. It can take 2-4 minutes before the host magically appears back again.

Yes I know you can download it directly from the web interface to VirtualCenter or an ESX host but sometimes you you may be working in an environment without web access enabled and there isn’t a VIclient in sight.

I’ve also noticed its a pain in the ass to find on Google, so I figured I’d pop it here for all to download.

http://www.swizzling.org/VMware-viclient.exe

(This is from my ESX 3.5 update 5 host. So it’s the newest version I’m aware of)

Sure VMware can increase disk sizes quickly and easily but thats not much use unless you can expand the paritions on that disk.

In this example I have a Linux install built on LVM. I want to increase the size of the virtual disk in VMware and then increase the size of the LVM Volumegroup.

Here’s my filesystem, notice I only have 11GB on the root partition;

# df -h

OK, lets start.

Power off VM

First, increase the size of the virtual disk (VMDK) by 10GB for example
vmware-vdiskmanager -x 10GB /path/machineName.vmdk
(VirtualCentre users can increase disk sizes easier via the Settings dialog of the VM)

Powered on VM

Now lets create a partition on the new space

# fdisk /dev/sda

Create a new primary partition, and set the filesystem type to LVM (AKA 8e)

Reboot VM

Create a physical volume for LVM:
# pvcreate /dev/sda3
Physical volume “/dev/sda3″ successfully created

Add the new physical volume to the volume group:
#vgextend VolGroup00 /dev/sda3 Volume group “VolGroup00″ successfully extended

Extend the logical volume over the new space in the volume group.

In the next command you will see I extended the volume by 9.6GB and not 10GB!? If you try 10GB you will receive an error because there won’t be sufficient space.

I found the 9.6GB figure by running “vgdisplay” and used the value from the “Free PE/Size”. This is how much space is available to expand the volume.

# lvextend -L+9.6G /dev/VolGroup00/LogVol00
Rounding up size to full physical extent 9.06 GB
Extending logical volume LogVol00 to 20.34 GB
Logical volume LogVol00 successfully resized

Then grow the file system into the new space of the volume.
# resize2fs /dev/VolGroup00/LogVol00
Filesystem at /dev/VolGroup/LogVol00 is mounted on /; on-line resizing required.
Performing an online-resize of /dev/VolGroup00/LogVol00 to 5332992 (4k) blocks.
The filesystem on /dev/VolGroup00/LogVol00 is now 5332992 blocks long.

Now here is my bulky new disk layout (df -h)