Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 36
  • Last Modified:

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...
0
gaspan
Asked:
gaspan
  • 8
  • 6
  • 4
1 Solution
 
John HurstBusiness Consultant (Owner)Commented:
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.
0
 
gaspanAuthor Commented:
The newer versions are not compatible with Windows 2000. I am using the "most recent" compatible version...
0
 
John HurstBusiness Consultant (Owner)Commented:
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.
1
When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
and what is the BSOD ?

this will tell us what is wrong?

Storage Controller fault Stop 7b ?
1
 
gaspanAuthor Commented:
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
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
 
gaspanAuthor Commented:
i am attaching a screenshot of the BSOD
Capture.JPG
0
 
John HurstBusiness Consultant (Owner)Commented:
Please try again and click on the blue Attach File link near the bottom.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Stop 0x1E - Hardware Abstraction Layer (HAL) fault.

possibly incorrect HAL, and surrounding files.
0
 
John HurstBusiness Consultant (Owner)Commented:
That is what I looked up as well. Does that not render the system unable to be converted?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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
0
 
gaspanAuthor Commented:
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.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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
1
 
gaspanAuthor Commented:
No luck. There are no errors in the creation but I am stuck at the same error... 0x1E
0
 
gaspanAuthor Commented:
I finally found the issue causing the BSOD. Apparently it has to do with a scsi driver that was installed as part of the Update Roll Up 1 for Windows 2000 SP4. There is a hotfix that replaces this driver and upon installation of the hotfix I was able to make a successful conversion. I did use SCSI option for storage which was the default.

There is a Microsoft discussion of this hotfix here:  https://support.microsoft.com/en-us/kb/904374

Thank you all for your input
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
where did you get the Hotfix, from Microsoft ?

But this error only occurs on the conversion, not on the original physical server ?
0
 
gaspanAuthor Commented:
The hotfix is still available via email from Microsoft. I was surprised myself...
0
 
gaspanAuthor Commented:
Because I did my own research aside from the recommendations which did not solve my problem
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 8
  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now