The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)
View by Article ID
Cold Migrating a Virtual Machine from ESX Server 2.x to 3.0 Fails (2182)
Details
On a cold migration of a virtual machine from ESX Server 2.x to ESX Server 3.0 with an append-mode disk, I get an error that the REDO log must be committed. Do I have to do this?
Solution
This kind of cold migration is used in one of the ESX Server 2.x to ESX Server 3.0 upgrade scenarios to minimize virtual machine downtime.
You must commit the virtual machine's REDO log before the cold migration. To do this:
Power off the virtual machine.
Edit its settings.
Change the virtual disk mode from append to undo.
Power on the virtual machine again and power it off. A dialog box appears and lets you choose to keep, commit, or discard the REDO log.
Commit or discard the REDO log before trying to migrate the virtual machine.
As a best practice, you must commit or discard REDO logs of all virtual machines and change the disk mode to persistent before upgrading from ESX Server 2.x to ESX Server 3.0.
Note: This issue is resolved in ESX Server 3.0.1.
Keywords
2182; esx301
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
