jamesmayers
Contributor
Contributor

VMWare ESX 3.5 U3 + BESR 8.5 - Server 2k8 will not boot

Hello,

We have installed ESX 3.0.2 and the vCentre management server. We are using Symantec Backup Exec System Recovery to image production servers to bring them into the VMWare envirionment for testing and development work. I have sucessfully moved over Windows Server 2003 R2, Windows Server 2000 SP4 and Windows XP SP2 clients - however when I come to import a Windows Server 2008 image the process completes but the VM will not start up. The VMWare Converer process completes fully and only displays one error "Unable to configure the source image." If this message is oked the process then completes. I have v2i images of 2 differant windows server 2008 boxes - both have the same issue!

When the VM starts, just after Post the windows boot manager comes up with a stop code of 0xc0000225

Has anyone discovered this problem before and/or have a workaround/solution for the problem?

Thanks

James

0 Kudos
14 Replies
jamesmayers
Contributor
Contributor

Hello

We are using ESX v3.5 U3...

Here is a screenshot of the error we are getting...

0 Kudos
paul_xtravirt
Expert
Expert

Your VM is not booting properly as the conversion with converter is not completing properly; the configuring VM process that fails is critical to the process.

You have not mentioned what version of Vmware Converter you are using, but if it is up to and including VMware Converter 3.0.3 | 5/6/2008 | Build 89816, then Windows Server 2008 is not supported. You backup file produced by Symantec may be supported, but the backed up guest has to be as well.

You will need to use Version 4 Convertor -

If you found this helpful, please consider awarding points

If you found this helpful, please consider awarding some points
0 Kudos
jamesmayers
Contributor
Contributor

Thanks Paul

We are using VMWare Converter v4.0.2

We are using the version which is integrated with vCentre....I am considering downloading the trial of the stand alone version to see if this converts the v2i differantly...

Ta

James

0 Kudos
paul_xtravirt
Expert
Expert

Hey James,

At least you are on 4 so that makes life easier. So, we just have to work out why you are recieving the following error:

"Unable to configure the source image."

Let me do some further investigation and see what I can find.

If you found this helpful, please consider awarding points

If you found this helpful, please consider awarding some points
paul_xtravirt
Expert
Expert

incorrect

If you found this helpful, please consider awarding some points
0 Kudos
jokke
Expert
Expert

There are a few issues with symantec images listed in the release notes for converter. Have you checked?

An alternative way of could be to have the Backup Exec image be restored into a vm with a Backup Exec restore disk (iso). Then let converter "configure machine" on the newly created vm.

There should not be compatibility issues with BE85 images, as I've done direct conversions on those before. But beware of the known issues.

Joakim

0 Kudos
victorg
VMware Employee
VMware Employee

Ahem. It's a little embarassing. The vCenter integrated version 4.X.X IS NOT the same as standalone 4.0. In fact, it's much older. I would suggest using standalone 4.0.

jamesmayers
Contributor
Contributor

I have tried vmware converter 4.0 standalone and get the same error!

0 Kudos
victorg
VMware Employee
VMware Employee

Please attach the log bundle and provide some information about your source. Is it multi-boot? What's the disk layout? You could try restoring your image in VM using Symantec's software.

0 Kudos
jamesmayers
Contributor
Contributor

Thanks Victor

How do i get the log bundle - i presume you mean the vmware converter bundle?

The guest OS is a single boot windows server 2008 box, the OS is on a raid1 set...its a poweredge 2950....

0 Kudos
CWedge
Enthusiast
Enthusiast

We are getting this same error.

Only we are doing a simple clone (vm off) with NO guest custimzation.

We can't even SCP the windows 2008 vmdks and get it to boot ever again. (yes we change the appropiate file names and register in VC)

We just keep getting the same as the picture above. And this is just merely cloning a VM that was never a P2V

0 Kudos
jamesmayers
Contributor
Contributor

Hello

I have now managed to get this working - unfortunatly i do not quite know what i did!

I am going to replicate the problem and make a not of what i did

once i know what i did i will post it up on here....

James

0 Kudos
RajatMishra
Contributor
Contributor

Hi James,

Do you remember what you did to fix this problem. I get same problem when I tried P2V Win2008 R2 SP1 to ESXi 4 using PlateSpin Migrate9. Thank you in advance for your help.

Rajat

0 Kudos
jokke
Expert
Expert

If switching to v5 of converter I would guess you're fine..

0 Kudos