New VMware customer. We have 2 new DL385 G5p servers. There was a bug where the optical drive wasn't supported in build 123629and would prevent the ESXi install. We have gotten past this point through the disconnect optical drive workaround and then installing newest ESXi patch 143129. Reconnected the optical drive, but it still isn't usable (SCSI?). But at least we can boot ESXi. Good.
The current issue is that I can create a virtual machine but it won't boot up with an iso file. The iso file was uploaded to the datastore residing on the DL385 SAS drives (same place as the ESXi install). I tried both a Windows 2003 Server iso file and also the same ESXi iso file I installed from (just to try a known good iso file).
When I boot the VM, I get a lot of network boot messages (which fail since there is no network boot setup). I cannot tell if it is actually trying to boot from the iso file.
Network boot from AMD Am79C9C970A
Copyright (C) 2003-2005 VMware, Inc.
Copyright (C) 1997-2000 Intel Corporation
CLIENT MAC ADDR: 00 50 56 9A 22 BF GUID: 501A94DA-2837-C11B-8709-345F94B05437
PXE-E51: No DHCP or proxyDHCP offers were received.
PXE-M0F: Exiting Intel PXE ROM.
Network boot from AMD Am79C970A #2
Copyright (C) 2003-2005 VMware, Inc.
Copyright (C) 1997-2000 Intel Corporation
CLIENT MAC ADDR: 00 50 56 9A 16 BF GUID: 501A94DA-2837-C11B-8709-345F9-345F94B05437
PXE-E51: No DHCP or proxyDHCP offers were received.
PXE-M0F: Exiting Intel PXE ROM
Operating System not found
My virtual machine properties are:
CD/DVD Drive 1, Connect at power on, Device Type = Datastore ISO file = esxi.iso
Is it actually trying to boot the iso file and thinks it is invalid? Or is it not even trying to boot from iso? Can I turn off the network boot attempts (I didn't see any options in the VM BIOS)?
I can boot using the Client Device option (with Windows Server 2003 cd in my pc optical drive).