Link to home
Start Free TrialLog in
Avatar of gaspan
gaspan

asked on

Windows 2000 virtual image using VMWare converter

Before throwing out some old servers I decided to virtualize them in the event we need to collect some old date from them. I used the VMWare Converter 4.0.1 (last one to be Win2k compatible) and the process of creating a guest went very smoothly. The virtual image was saved on an external drive. When I try to run it however I get a BSOD with a  Kernel error.

When I made the conversion I indicate a 1 processor guest although this was a multiprocessor server and OS. But wonder if that is a correct setting and the cause of the BSOD. I am running a new conversion as multiprocessor vm but wanted to check with someone that had prior experience. Creating those images takes some time...
Avatar of John
John
Flag of Canada image

If you still have the server (I am sure you do) try a newer version of VMware Converter to see if that works. There is likely a driver issue from the first conversion that is causing the issue.
Avatar of gaspan
gaspan

ASKER

The newer versions are not compatible with Windows 2000. I am using the "most recent" compatible version...
I saw a post from Andy a while back that suggested a later version (at least that is what I recall). That is why I suggested.

Can you try Driver Updates on the server and see if you can convert again.
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
and what is the BSOD ?

this will tell us what is wrong?

Storage Controller fault Stop 7b ?
Avatar of gaspan

ASKER

I decided to redo the conversion as I noticed having a single processor setting when in fact the physical machine and os are for a multiprocessor system. I will try that when it is done and return with more info. Thank you very much for your help so far
Single Processor and Multiprocessor HALs can cause BSODs, and they have to be switched manually, not plug and play like 2003.

but a single processor HAL will run on a dual processor machine, but NOT the other way round.
Avatar of gaspan

ASKER

i am attaching a screenshot of the BSOD
Capture.JPG
Please try again and click on the blue Attach File link near the bottom.
Stop 0x1E - Hardware Abstraction Layer (HAL) fault.

possibly incorrect HAL, and surrounding files.
That is what I looked up as well. Does that not render the system unable to be converted?
Common problem, when we used to convert 2000 machines. But that was a long time ago.

Re-convert, and accept the defaults. Do not change anything.

Can be converted, but you need to ensure you have correct HAL and supporting files, and take note of physical hardware and like virtual hardware.

see here

https://support.microsoft.com/en-us/kb/237556
Avatar of gaspan

ASKER

Are you implying that I need to downsize the kernel to single processor before making a virtual image?  Could it be a drive/storage issue? When I generated the image it asked me for storage type on the target and I selected Scsi.
just complete a conversion "as is" do not change anything.

and then let me know what the VM is, that's been created. Before Power On!

Storage Controller is Stop 0x7B
Avatar of gaspan

ASKER

No luck. There are no errors in the creation but I am stuck at the same error... 0x1E
ASKER CERTIFIED SOLUTION
Avatar of gaspan
gaspan

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
where did you get the Hotfix, from Microsoft ?

But this error only occurs on the conversion, not on the original physical server ?
Avatar of gaspan

ASKER

The hotfix is still available via email from Microsoft. I was surprised myself...
Avatar of gaspan

ASKER

Because I did my own research aside from the recommendations which did not solve my problem