Hello,

I'm looking at virtualisation, and I have installed ESXi 3.5 onto a DL380 G4.
I connect to it using the client utils an create a new virtual machine. When I install Windows 2003, it creates the partition, copies the files, then when the server goes into reboot I get the Windows 2003 screen, but before it gets to the setup screen, I get BSOD
STOP: C000021a{fatal system error}
The Windows logon process terminated unexpectedly with a status of 0x00000080 0x00000000 0x00000000 the system has been shutdown.

When I find articles relating to the above error, they all refer to windows XP, and going back to the last known good configuration, but as there isn't a good configuration as it hasn't finished the installation I can't go back to it.

Anyone got any ideas?

Cheers
Mark

is this 32bit or 64 bit 2003?

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

This is a 32 bit OS.

when it reboots; is the media still available as a Datastore ISO file?

Stop Error:
http://support.microsoft.com/kb/156669

I would also look at the Raid driver needed at the F6 prompt during install.  The lack of or incorrect driver usage would cause this problem.  I believe I have seen a solution in this forum; try a search within EMC: Vmware.

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

Yes the CD is still available as it is connected via the client machine.  I tried using driver from VMware but I got the same issue.
As windows hasn't yet been configured, I don't think i can use the windows troubleshooting a Stop error as I haven't even set a password so I can't use recovery console.

Cheers
Mark

VMware cool doc

http://pubs.vmware.com/guestnotes/wwhelp/wwhimpl/js/html/wwhelp.htm

Find windows 2003 server on left and the scroll down half way on the right pane

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

If you are using the virtual LSI Logic SCSI adapter, Windows Server 2003 automatically installs the SCSI driver when you install the guest operating system. If you are using the virtual BusLogic SCSI adapter, you need a special SCSI driver available from the download section of the VMware Web site at http://www.vmware.com/download . Follow the instructions on the Web site to use the driver with a fresh installation of Windows Server 2003. If you have a virtual machine with a SCSI virtual disk and an earlier Windows guest operating system and want to upgrade it to Windows Server 2003, install the new SCSI driver before upgrading the operating system.
 

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

Another way to get around all of this is to build a 2003 Server on another physical server; then use the converter to P2V it.

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

Thanks,
I'll have a look.
Mark

From looking at the info you have suggested I have already tried this.  I think that it is a problem with the scsi driver.  The scsi driver mentioned doesn't exist but I have found a vmware scsi driver.  Unfortunately this didn't work either.
I may have to try doing a P2V.

Cheers for your suggestions.
Mark

Fact:  Your hardware is NOT on the ESXi compatibility list.


There are two downloads for ESXi, one with HP Insight tools, the other with out.  Which one did you use?   I suggest using the one with out the Insight tools as your server model is not on the compatibility list and there is no guarantee the tools will work, but a high probability they will cause you issues.  They did for me when I tried to load that version on my HP that is also not on the compatibility list.  

Also, have you tried running the install using either an ISO file copied to a VMFS datastore? or from the servers local CD/DVD rom?

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt        SPOOOOON!!!!!   
Senior Network Engineer
Keep IT Simple http://www.kiscc.com

Brent,
Yes I know it's not on the compatibilty list, but I want to try it and prove it before buy a new beefy server which is on the list.  I used the HP version.  I'll try the one without.  I'll also try putting the ISO onto the datastore.

Cheers
Mark

Hello,
Got it working.  I copied the .iso image to the datastore and then when it rebooted, it continued into the configuration, s I know have a working server.

Thanks to all for your assistance.