VMware Communities
Matt_M1
Contributor
Contributor

Guest Image hangs on startup

Hi,

I am running Workstation version 6.05 Build - 109488. My Host system is Vista 64 Bit Sp1. My Laptop has 4 GB of memory.

When starting a Windows 2003 32 bit guest image, I constantly encounter one of the below problems on startup:

1) The Windows 2003 guest image reports one of the following problems:

windows could not start because the following file is missing or corrupt

<Windows root>\system32\ntoskrnl.exe

OR

<Windows root>\system32\hal.exe

2) The guest image shell screen is just black and sits there forever. (hangs) (The most I have left it is approx 10 minutes).

If one of the above scenarios occurs (1 or 2) , I then Stop the image using the Stop Button on the VMWare Console. It then takes approx. 5 minutes for

the image to shut down with the summary view then appearing again

I then start the guest image again, and occasionally the problem will repeat ( 1) or 2) as described above) , but eventually the guest image will start normally.

Once the guest image is up and running, I have no problems.

I have attached a log file.

Any assistance would be appreciated.

Thanks,

Matt

0 Kudos
2 Replies
continuum
Immortal
Immortal

that log doesn't help - post vmware.log from the VMs directory

___________________________________

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
Matt_M1
Contributor
Contributor

Thanks Very much for the response.

Attached is log file, from a hanged startup of the guest image.

I have in the meantime tried one thing, and that was to change the configuration :

FROM:

Number of Processors -> 2

TO:

Number of Processors -> 1

I tried starting the Windows 2003 32 bit guest image six times in a row, with no problems.

I checked the bios on my laptop. It was set with Virtualization -> Enabled.

Really not sure if having Number of Processors set to 2, has a performance advantage.

Anyway's for now, I will leave Number of Processors -> 1 , and hopefully this will fix the problem.

Thanks,

Matt.

0 Kudos