In a migration project to VMware vSphere 5.5 I bumped into duplicate MAC address issue (I found out after some investigation).
Some info on the setup.
There are ESXi hosts that we are migrating from 5.0 to 5.5. Some VM’s where 2 VM’s (VM1 and VM2) share the same MAC address (production and test machine).
On ESXi 5.0 these 2 VM’s can run together on the same ESXi host.
I want to move the VM’s to an already upgraded ESXi 5.5 host, the first VM (VM1 moves without any problems. ) For the second VM (VM2) I get following error during vMotion. Same error happens when I cold migrate the VM2 to the same host (ESXi 5.5) as VM1 and try to power VM2 on.
After some Google research I came across following blog
And adding the advanced setting to VM2 fixed the problem.
I get a lot of questions of students and customers about resizing a virtual disk. This is the reason for this blog.
The following procedure will guide you step by step through the process of resizing (increasing) a disk of a virtual machine.
Before you make virtual hardware changes be sure you have taken a full backup of the virtual machine.
NOTE: If you do not want any troubles only increase the disk size. Decreasing can cause loss of data.
Increase Disk using diskpart
Step 1: Edit the virtual machine settings and increase the size of the disk (VMDK).
Step 2: Open the console of this virtual machine and start a command prompt.
Step 3: Start diskpart and execute following steps.
à this gives you a list of the available partitions
select volume x
à select the partition number you want to increase
à this will add the empty disk space into the partition.
Now the partition has increased in size.
NOTE: On Windows 2008 this can be done via the Device Manager / Storage, but I have seen some weird things like showing incorrect partition sizes.
Increase Disk using Third Party tool
Step 1: Be sure you have a boot image (ISO) of the Acronis Disk Director Tool that supports your guest OS.
Step 2: Boot your virtual machine using the boot image ISO. Use the ESC button during booting your virtual machine to activate the “one time boo menu”
Step 3: Select the partition you want to increase and right mouse click on it. Then select “Resize Volume”
Step 4: Increase the disk space of the selected partitions by decreasing the unallocated space to 0
Step 5: After increasing the partition you have to commit the changes.
Step 6: Now you need to reboot your virtual machine after disconnecting the boot image.
VMware vCenter Error Call “PropertyCollector.RetrieveContents” for object “propertyCollector” on vCenter Server failed
A customer of mine called me with a weird problem with a Template which was converted back to a Virtual Machine. See here the problem which occurs when the customer wanted to edit the settings of this VM.
The cause of this problem is that an ISO was mounted from a datastore which does not exist anymore.
To solve this problem, just connect to the ESX host where the VM is registered on. Edit the setting here and put the CDROM on “Client Device”.
Then check on which datastore the VM is located. Then unregister and register the VM again in the ESX host. Now you are able again to edit jthe setting of this VM via vCenter
Since VMworld San Francisco 2010 we are waiting for this nice app for the Ipad. VMware today released this app via the iTunes store for FREE (Direct Link), just as the VMware View Client for IPAD (Direct Link).
What are the features available in this app?
- Search for vSphere hosts and virtual machines in your vSphere environment
- Monitor the performance of vSphere hosts and virtual machines
- Manage virtual machines with the ability to start, stop and suspend
- View and restore your virtual machines’ snapshots
- Reboot vSphere hosts or put them into maintenance mode
- Diagnose vSphere hosts and virtual machines using built-in ping and traceroute tools
What is required for this app to be able to manage your vCenter?
vCenter Mobile Access (vCMA) virtual appliance available from the VMware Labs: http://labs.vmware.com/flings/vcma (Now supports SSL)
NOTE: This app is available as is, with community support.
- Network connection to the vCMA virtual appliance; can use built-in VPN client
VMware vSphere and VMware vCenter Server
Look at my blog entry to see how to setup the vCMA : limited-vsphere-management-using-a-mobile-device
An overview of the architecture
Some interesting links
On the VMware Labs website you can find a free appliance that can give you limited access to the management tools available in vSphere vCenter. The appliance is called vCMA or vCenter Mobile Access.
How to install?
- Go to the vmware.com/labs website and download vCMA as a OVF. Jump to site
- Extract the zip file that contains the OVF.
- In vCenter, go File – Deploy from OVF and point to the extracted OVF file.
- Once deployed, you can start the VM.
After the VM is started, there are 3 options to change settings
Using the menus on the console (to set network, timezone, login in to the command console)
Using the web interface https://vcma-host-or-ip:5480
Or using the command console. (use login in first screen)
- By default the root account has as password vmware (remember the console is by default in qwerty)
Special configuration settings to thing about!
- Set the IP to a fixed address
- Enter the DNS servers
- Change the default hostname and domainname. (http://communities.vmware.com/message/1335001)
- Change the root default password using the passwd, in the command console
How to use?
- It is very easy to start using this app.
- Open a browser (on you PC or mobile device)
- Point to http:// vcma-host-or-ip/vim (the folder /vim is needed and I hope VMware will change this in a next release)
- Enter the vCenter server name and the userID and password you normally use in the vcenter.
Now you can do some functions like
- Edit settings of a VM
- Change Powerstates of a VM
- Etc, install and discover.
Alternative apps you need to buy!
iDatacenter http://nym.se/idatacenter/ (iPAD)
iVMControl : http://itunes.apple.com/us/app/ivmcontrol-control-vmware/id404263941?mt=8 (iPAD, iPhone)
When you use convertor to migrate a physical machine to a virtual machine you get a BusLogic Controller as SCSI controller. Following is tested on vSphere 4.1 with a Virtual Machine hardware version 7
In the Virtual Machine Settings you see this.
In your device manager it is present as a VMware SCSI controller
If you want to change this to a LSI Logic SCSI controller because some application may need it like Trend Micro Deep Security – vShield, you have to follow steps below to get it working
Steps to convert
- Install the latest VMware Tools.
- Power down the Virtual Machine (try to use the shutdown so your OS is closed correctly.)
- Edit Settings of the Virtual Machine and add a new disk (can be small because this will be removed afterwards). We cannot add a new SCSI controller without adding a disk.
When you add a new disk select a different SCSI-id then the existing SCSI Controller. First number in the ID is the number of the SCSI controller.
When the disk is updated, the type of the SCSI controller must be changed.
- When the configuration is updated, you can restart the VM
In your device manager you now see 2 types of SCSI controllers
When you see the LSI logic SCSI controller you can shut down the VM again. Then will remove the just added disk and change the type of SCSI Controller 0
- When this is finished you can restart the Virtual Machine
- After starting the Virtual Machine you see that new hardware is found, now you need to reboot once more. (Last time to reboot).
Now for best practices you need to remove all unused devices in you device manager. Therefor you need to start device manager using a special set parameter.
- set devmgr_show_nonpresent_devices=1
If you now select the SCSI and RAID Controllers, you will see some grayed-out devices. These devices should be uninstalled
- Now you are done.