Archive

Archive for the ‘VMware’ Category

Cleared VCP5 Delta Exam

Today i have written VCPD550 Delta exam and passed.

Advertisements
Categories: VMware

Invalid configuration for device ‘0’ Error when removing vm hard disk

Error:

vm invalid config

Steps:
1.verify the hard disk source storage
2.These error came when mounted LUN inaccessible
3.Try to remove the vm hard disk
4.If error persists remove the VM from inventory
5.Take the backup of .vmx file and download
6.Edit the .vmx file and remove the scsi(x:x) id for the disk
7.save the file and upload it into datastore and add to inventory
8.Now power on the VM
9.Once LUN comes back online add that .vmdk which was removed from .vmx file earlier

Categories: VMware

VMware Tools installation in RHEL 5.4

1. Right click the RHEL 5.4 VM and click “Install/Upgrade VMware Tools”

2. Create one folder. I created folder in desktop and named as “Test”

3.Copy the media files from CD drive to “Test” folder

4.Open the Terminal,

vmtools1

5. Unzip the archive file by using tar command

6. Go to “vmware-tools-distrib” directory

vmtools2

7. install the tools by executing  ./vmware-install.pl

8. While installing choose number for screen resolution ( I selected 12=1024*768)

9. After few seconds vmware tools installed successfully.

Categories: VMware

Safely Remove Hardware Option in Windows VM Guest OS

We can see safely remove hardware option in windows guest operating system. This is critical one, if we remove network adapter it will cause VM unreachability.

Device Eject Option

We need to enable one option after power off the VM to hide this “Safely Remove Hardware” Option.

Power off the VM and right click “Edit Settings”

Go to Options and General,

Go to Configuration Parameters

Add Parameter “devices.hotplug” = “false”  without quotes

config parameter

Now, Power On the VM and you can see the task bar, Safely Remove Hardware Hided.

Categories: VMware

Troubleshoot ESXi Server’s iSCSI connectivity

Netcat or nc is a networking utility for debugging and investigating the network.

Netcat Utility

Categories: VMware

Mount VMDK in Windows

December 24, 2012 Leave a comment

If you wish to mount a vmdk file into your windows you need to download VDDK from VMware web site. After installation of VDDK, go to command prompt and run the below commands,

I am kept my VMDK in “C:\VMDK\Test.vmdk”

C:\Program Files\VMware\VMware Virtual Disk Development Kit\bin>vmware-mount.exe  J:  “C:\VMDK\Test.vmdk”

Now, you have the read only access to drive “J”

If the vmdk file contains more than one partition you can use the parameter /v:x to mount the other volumes:

vmware-mount.exe /v:2 J: “C:\VMDK\Test.vmdk”

If you need a writeable access just use the parameter /m:w.

vmware-mount.exe /m:w J: “C:\VMDK\Test.vmdk”

To delete vmdk mount,use the parameter /d:

vmware-mount.exe /d J:

vmware-mount.exe /L = This command list out all mounted vmdk

Please note that disk management does not show the vmdk mounts. you can view mounts in “My Computer”.

Categories: VMware

Unable to access the file since it is locked error

September 29, 2012 Leave a comment

Error:

1. Process Lock: There is a process on the ESX server that still has hold of a file(s) used by the VM.  This is one of the most common causes.  To resolve this there have been a couple of good VMware Forum postings here and here that have been consolidated to this useful posting over at GabesVirtualWorld.com (*Note: It is worth checking out the comment by Kent at the bottom of the posting). Also, check out Tecumseh’s posting here.

2. Disk Naming Conflict: Two or more disks with the same VMDK name. This can be caused by another disk with the same VMDK file name being referenced by the VM.  This may have occurred due to a VM move where the VM used have disks located on different LUN’s or similar which have now been moved onto the same LUN and VM directory.  If this is the case rename one of the matching VMDK files (preferably not the one used as the boot drive) and with the VM powered down remove the renamed disk and reattach it (using its new name).

3. Corrupt VMX file: There is a possibility that the VM’s VMX file has corrupted.  You can look through the VMX file and try and troubleshoot the issue though it is quite often quicker to recreate a new VMX file.  This can be achieved by creating a new VM and attaching the existing disks to it (ie: rather than creating a new VM with new a new disk).

So here are three potential problem areas that you may want to consider when getting a “Unable to access a file since it is locked” within ESX.

Categories: VMware