Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

Cold Migrating a Virtual Machine from ESX Server 2.x to 3.0 Fails

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:
  1. Power off the virtual machine.
  2. Edit its settings.
  3. Change the virtual disk mode from append to undo.
  4. 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.
  5. 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

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 2182
  • Updated: Aug 14, 2009
  • Products:
    VMware ESX
  • Product Versions:
    VMware ESX 3.0.x