VMware Cloud Community
Gmcpaul
Contributor
Contributor

Problem installing further Servers on ESXi 3.5

Hello guys!
I have a serious problem with installing further servers on my esxi machine.
Currently there are 3 MS Server 2003 and 1 WinXppro installations perfectly running but i am not able to install a 5th machine:
- Creating the new instance is no problem (eg Server 2003, @ 20 GB partiton)
- During install of Server 2003 and WinXP on PNP install there comes a window thatys that it was not possible to install the battery driver. ?! (ive tried different install cds and versions with sp0-sp2)
- When the Server is installed and i try to install a service pack then comes a error message that the service pack exe is corrupt... => it isnt i have testet it on my pc and redownloaded it a few times...
is there a limitation of running pcs on esxi ?
does anyone have a idea how to solve this problem ? 😞
My HW setup:
Supermicro PDSMU
Intel Xeon X3210
8 GB Ram DDR2
LSI 8704EM2 + BBU
2x WD 500GB SATA HDD (Raid 1)
regards
0 Kudos
7 Replies
Gerrit_Lehr
Commander
Commander

No, there is no limitation for the number of VMs running on ESXi stand-alone. What does your .vmx file look like. Did you try to create a new VM?

Kind Regards,

Gerrit Lehr

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

Kind regards, Gerrit Lehr If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
0 Kudos
Gmcpaul
Contributor
Contributor

- I created new VMs a every time i tried to install the new System - I also tried to install with and without the Vware SCSI driver (vmscsi-1.2.0.4.flp) => didn't help - VM disk was formatted with quick and normal Format (Ntfs) => didn't help
im currently trying to install another testmachine
i will post the error msgs asap
Summary of Current Test install:
config.version = "8" virtualHW.version = "4" floppy0.present = "true" nvram = "Testmachine.nvram" deploymentPlatform = "windows" virtualHW.productCompatibility = "hosted" tools.upgrade.policy = "useGlobal" powerType.powerOff = "default" powerType.powerOn = "default" powerType.suspend = "default" powerType.reset = "default" displayName = "Testmachine" extendedConfigFile = "Testmachine.vmxf" scsi0.present = "true" scsi0.sharedBus = "none" scsi0.virtualDev = "lsilogic" memsize = "512" scsi0:0.present = "true" scsi0:0.fileName = "Testmachine.vmdk" scsi0:0.deviceType = "scsi-hardDisk" ide0:0.present = "true" ide0:0.clientDevice = "true" ide0:0.deviceType = "cdrom-raw" ide0:0.startConnected = "false" floppy0.startConnected = "false" floppy0.clientDevice = "true" ethernet0.present = "true" ethernet0.networkName = "VM Network" ethernet0.addressType = "generated" guestOSAltName = "Microsoft Windows Server 2003, Standard Edition (32-bit)" guestOS = "winnetstandard" uuid.location = "56 4d 04 08 ed bd ed 8e-59 5e 09 72 0f 87 49 42" uuid.bios = "56 4d 04 08 ed bd ed 8e-59 5e 09 72 0f 87 49 42" toolScripts.afterPowerOn = "true" toolScripts.afterResume = "true" toolScripts.beforeSuspend = "true" toolScripts.beforePowerOff = "true" scsi0:0.redo = "" ethernet0.generatedAddress = "00:0c:29:87:49:42" sched.swap.derivedName = "/vmfs/volumes/4a260ac4-24368a30-f630-00304891aa08/Testmachine/Testmachine-0c07c896.vswp" ethernet0.generatedAddressOffset = "0" hostCPUID.0 = "0000000a756e65476c65746e49656e69" guestCPUID.0 = "0000000a756e65476c65746e49656e69" userCPUID.0 = "0000000a756e65476c65746e49656e69" hostCPUID.1 = "000006f7000408000000e3bdbfebfbff" guestCPUID.1 = "000006f800010800000002010febbbff" userCPUID.1 = "000006f7000408000000e3bdbfebfbff" hostCPUID.80000001 = "00000000000000000000000120100000" guestCPUID.80000001 = "00000000000000000000000000100000" userCPUID.80000001 = "00000000000000000000000120100000" evcCompatibilityMode = "FALSE"
0 Kudos
Gmcpaul
Contributor
Contributor

see attached error message in windows server ...
this is what happens every time i try to install sp2 on the system
0 Kudos
pyosifov
Enthusiast
Enthusiast

As far as I am familiar with MS products battery drivers are installed if the image is custom build. In Windows (XP or 2003) there is no battery driver. Maybe you just got the wrong image - working fine with laptops for instance and optimized to work with such.

Also keep in mind that if you are just playing (not using licensed Microsoft Windows) for testing or whatever pourposes, in a Domain invoronment you could have issues.

Have you used the same image for the other three installs you mentioned?

Have you tried any Linux distribution?

Are you building the virtual machines from scratch, or are you copying them?

And as a last step - reinstall your ESXi. Shit happens and this may fix it.

0 Kudos
Gmcpaul
Contributor
Contributor

The install CDs are not custom.
I tried to install from the originial cd and with an iso and also different types of ms system (2003 standard, 2003 web server, xppro (maps) and xppro oem)
the virtual machines are built from scratch, yes.
esxi was reinstalled yesterday and updated to version 3.5.0, build 163429
0 Kudos
Gmcpaul
Contributor
Contributor

is it possible that i have to update to version 4 ?
i guess 3.5 x86 does not support all of the 8gb ram i got, or does it ?
0 Kudos
AndreTheGiant
Immortal
Immortal

i guess 3.5 x86 does not support all of the 8gb ram i got, or does it ?

Is not an issue of ESX.

The 32 bit architecture has a limit at 4 GB RAM.

With some trick some system (Linux or Windows Enterprise/Datacenter) can "see" more than this limit.

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
0 Kudos