VMware Cloud Community
JensCoOrga
Contributor
Contributor

VM does not start after successful P2V Conversion

Hello,

after an alleged successfull (Converter Standalone finishes without errors) P2V Conversion of a Windows Small Business Server 2008 the VM will not start. The source server has two physical harddrives.


The german error message is:



Ereignisdetails:

Typ: Info

Uhrzeit: 05.05.2014 16:49:50

Aufgabendetails:

Beschreibung: Virtuelle Maschine einschalten

Fehlerstapel:

  Beim ESX-Host ist ein Fehler beim Einschalten der virtuellen Maschine RCSSRV02 aufgetreten.

  Das Starten der virtuellen Maschine ist fehlgeschlagen.

  Einschalten des Moduls DiskEarly fehlgeschlagen.

  Die Festplatte '/vmfs/volumes/52d54d75-39089066-b92d-901b0e07ec65/RCSSRV02/RCSSRV02-000003.vmdk' oder eine der Snapshot-Festplatten, auf die sie angewiesen ist, konnte nicht geöffnet werden.

  Die übergeordnete virtuelle Festplatte wurde nach dem Erstellen der untergeordneten virtuellen Festplatte geändert. Die Inhalts-ID der übergeordneten virtuellen Festplatte stimmt nicht mit der Inhalts-ID für die übergeordnete virtuelle Festplatte der untergeordneten virtuellen Festplatte überein

Zusätzliche Ereignisdetails:

  Typ- ID: Info

Ziel Objekttyp: ComputeResource

DataCenter Objekttyp: Datacenter

Host Objekttyp: HostSystem

Host-Build: 1331820

VirtualMachine Objekttyp: VirtualMachine

ChainId: 6985

Zusätzliche Aufgabendetails:

  VC-Build: 1398495

Aufgaben-ID: Task

Abbrechbar: False

abgebrochen: False

Beschreibungs-ID: Datacenter.ExecuteVmPowerOnLRO

Ereignisketten-ID: 6985

Does anyone have a clue what may be wrong?

Thank you and best regards

Jens

Reply
0 Kudos
7 Replies
POCEH
VMware Employee
VMware Employee

Could you try to reconfig your VM and then try again to power it on?

In case of failore please upload log bundle.

Reply
0 Kudos
vNEX
Expert
Expert

Hello,

its possible to post vmware.log file for that VM?

Thanks

Regards,

P.

_________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
Reply
0 Kudos
JensCoOrga
Contributor
Contributor

Thank you for your reply. How would I exactly reconfigure the VM?

Reply
0 Kudos
JensCoOrga
Contributor
Contributor

Here comes the log file plus a screenshot of the "weired" vmdk file configuration. I don't quite get it.

Thank you again and best regards

Jens

Reply
0 Kudos
vNEX
Expert
Expert

Hi,

after conversion there are leftover delta files from snapshot which are for some reason corrupted thus your VM cannot start. If the changes to the VM during the conversion were minimal you could throw away those changes in snapshot and try to boot VM from its parent disk.

To do this you must modify VM config file (vmx) and delete all references to existing delta files and point it to parent disk instead. You have to delete those delta files from datastore.

You can take this KB as reference:

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2...

You can achieve this also by editing VM config via client by removing all existing disks and add back those exiting parents..."RCSSRV02.vmdk" first try to delete all existing snapshots.

If the steps above are no applicable to you (you want to preserve existing snapshot) or you get stuck here or if it doesn't work please follow KB article below:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100796...

Sorry for limited info I am out of office and in time pressure...;)

Regards,

P.

_________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
Reply
0 Kudos
JensCoOrga
Contributor
Contributor

Dear vNEX,

thank you for your efforts.

There were no snapshots present in the snapshot manager. So I removed the one disk which was present from the VM by client and added the parent disk again. The VM would then boot however crash shortly after showing the first windows server boot progress bar into a blue screen.

Since this VM is mean while outdated anyway and I have to rerun the P2V conversion, how would I prevent this from happening again? Your help is greatly appreciated.

Jens

Reply
0 Kudos
vNEX
Expert
Expert

Hi Jens,

in situations where are no snapshots present in snapshot manager the proper steps to cleanup all obsolete snapshots entries in machine directory follow this KB:

VMware KB: Committing snapshots when there are no snapshot entries in the Snapshot Manager

Just short list ...before you will start new conversion process I would recommend:

1. Rigorously clean you physical machine from any 3rd party monitoring software which is bound to physical hardware of your machine (RAID config utils etc...)

2. Remove/uninstall any unnecessary 3rd party software from machine (including antivirus SW etc...)

3. During/before conversion try to minimaze load and changes made to the OS ...

For complete checklist see:

VMware KB: Troubleshooting checklist for VMware Converter

Regards,

P.

_________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
Reply
0 Kudos