VMware Cloud Community
WadeG
Enthusiast
Enthusiast
Jump to solution

Windows 2003 x64 won't boot after conversion

Hi all, I have searched everything I can think of and not gotten any results so far.

The problem is that I am trying to convert a physical machine Windows 2003 x64 Std, into a VM. The conversion goes ok, bit when I go to boot the vm, it acts as if no disks are present.

I have tried doing a repair, but either the driver that ships with Windows doesn't work, or any of the others i could fine via google and forum searches don't work either. I have downloaded the latest driver from LSI and now have been sitting at the "Setup is starting windows" for over 40 mins.

What do I need to do to get this VM Working? We are running VI3.5 U2.

Thanks for any help yoou can provide...

Reply
0 Kudos
1 Solution

Accepted Solutions
AndreTheGiant
Immortal
Immortal
Jump to solution

We have VMWare Converter Enterprise 3.0.3

Have you tried also version 4 of the Converter?

Are you using from your source machine? Or from another machine?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro

View solution in original post

Reply
0 Kudos
15 Replies
AndreTheGiant
Immortal
Immortal
Jump to solution

During conversion have you choose to install VMware Tools?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
WadeG
Enthusiast
Enthusiast
Jump to solution

Yes I believe I did, also if I am not mistaken the actual tools install is done after the first boot. I'm not even getting that far...

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

Just to be sure...

Have you enable VT on BIOS? Do you have other x64 working VM?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
WadeG
Enthusiast
Enthusiast
Jump to solution

Hi Andre,

Yes we have other 64bit running, had the VT issue awhile back.

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

Can you see at least the boot loader?

Can you select "safe mode"?

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
WadeG
Enthusiast
Enthusiast
Jump to solution

Sorry I should have been more specific. When i try to boot the VM, it searches for PXE. Meaning it doesn't even see the SCSI controller. If I attached the Windows ISO it will boot into the setup routine, however it will hang at the "Setup will not load Windows", if I try to specify a driver using f6 during the setup boot, I either get the driver is not supported (32 bit) and is older. I have tried no less then 5 or 6 different drivers recommended on this forum, no luck though...

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

How have you do the conversion?

Which version of the Converter have you used?

You physical system has only one boot entry?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
WadeG
Enthusiast
Enthusiast
Jump to solution

We have VMWare Converter Enterprise 3.0.3 Build 89816. Did a hot clone, server was still running.

Yup only one entry in the Physical machines boot.ini:

timeout=30

default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003 Standard x64 Edition" /noexecute=optout /fastdetect

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

I see partion 2.

What you you have in partition 1? A Diagnostic utility?

PS: you can try also version 4 of the converter.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
WadeG
Enthusiast
Enthusiast
Jump to solution

I think it's the standard Dell partition. I will check out the converter 4 though, never though about that. Not sure it will fix this issue though as the tools install etc is doen after the first boot.

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

We have VMWare Converter Enterprise 3.0.3

Have you tried also version 4 of the Converter?

Are you using from your source machine? Or from another machine?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
WadeG
Enthusiast
Enthusiast
Jump to solution

After upgrading my VC Server to vSphere and Converter et all, it works perfectly.

Thanks!!

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

Good for you Smiley Wink

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
timbure96
Contributor
Contributor
Jump to solution

I am having the same problem. I'm using ESX 3.5 and VMware Infrastructure client, and I cant load an OS. I get:

PXE-E53-No boot filename received

PXE-M0F: Exiting Intel PXE Rom

Operating System not found

My VMware either doesnt load or passes the little VMware BIOS screen too fast so I get no chance to press ESC or F2 or whatever it is. Please help!! Thanks!!

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

Select your VM, Edit Settings, Options, Boot Options.

Now you can choose to add a delay for BIOS (is in milliseconds!) to press ESC and enter in boot menu.

Or enter in BIOS and change boot order.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos