Thread: Installing OSX 10.6 Snow Leopard from the original install CD on a ESXi-Server virtua

Installing OSX 10.6 Snow Leopard from the original install CD on a ESXi-Server virtual Machine

I tried different boot loader from this board to install OSX 10.6 Snow Leopard from the original install CD on a ESXi-Server virtual Machine but something goes wrong:

--------------------------------------------------
OSX86_ModCD-031111-171757.iso
--------------------------------------------------
While booting I get the error Message: "Error parsing plist file" but the system starts with Darwin/x86 boot v5.0.132 - Chameleon v2.0-RC5 r726
Build date: 2011-02-17 01:03:31
Changing to the Original Snow Leopard Install CD and pressing F5 at the boot prompt I get the messages:
...
Error parsing plist file
EBIOS read error: Error 0x31
Block 0xae Sectors 0
EBIOS read error: Error 0x31
Block 0xb0 Sectors 0
EBIOS read error: Error 0x31
Block 0xc8 Sectors 0
…
and the systems hangs

-----------------------------------
2073-nawcomBootCD.iso
-----------------------------------
Starts with ISOLINUX 3.63 2008-04-10
Kernel: /usr/standalone/i386/boot
Loading: /usr/standalone/i386/boot…
Module: /Extra/Preboot.dmg
Loading /Extra/Preboot.dmg…………………….
failed and the virtual Machine is rebooting ….

----------------------------------------------------------
2073-OSX86_ModCD-031111-171757.iso
----------------------------------------------------------
While booting I get the error Message: "Error parsing plist file" but the system starts
with Darwin/x86/ boot v5.0.132 - Chameleon v2.0-RC5 r726
Build date: 2011-02-17 01:03:31
Changing to the Original Snow Leopard Install CD and pressing F5 at the boot prompt I get the messages:
...
Error parsing plist file
EBIOS read error: Error 0x31
Block 0xae Sectors 0
EBIOS read error: Error 0x31
Block 0xb0 Sectors 0
EBIOS read error: Error 0x31
Block 0xc8 Sectors 0
…
and the systems hangs


Can anyone help me?

Thanks a lot

J.T.

Those are Read Errors...

Burn the CD`s at the slowed speed as possible and/or change your VM I/O settings...

Hallo kyndder,

Thank you for your quick response. Meanwhile I find, that the error comes from the memory allocation, it seems that 256 MB (default) is not enough and make it fails in the contrary of 512 MB. But now I get the next problems ....