solgae's Posts

This is the ks file generated. I created this for installing ESX in VMware Workstation.
with the new 0.90 appliance, I am getting this error when deploying ESX 4.0: There was a problem with the Gateway Address specified on the command line. Error: IP string contains an invalid fi... See more...
with the new 0.90 appliance, I am getting this error when deploying ESX 4.0: There was a problem with the Gateway Address specified on the command line. Error: IP string contains an invalid first octet. Press to reboot.... Any ideas? I checked and re-checked the gateway address to make sure it's valid.
With the latest version of the EDA, I found a problem with the install. When the EDA appliance is configured for DHCP, and the ESX install is started, the error message "could not locate " pop... See more...
With the latest version of the EDA, I found a problem with the install. When the EDA appliance is configured for DHCP, and the ESX install is started, the error message "could not locate " pops up. Then, I had to type in the IP address of the EDA to get the install working. Is this by design? Also, did anyone tried this with 3.5 update 4?
I imported the appliance again and added the cdrom before powering on. Now it recognized the ISO just fine. Strange.
I imported to Workstation, and I mounted the ESX 3.5 U3 ISO. When I imported the OVF, the CD-ROM wasn't present in the VM, so I had to add it manually. FYI - this is the first time I had t... See more...
I imported to Workstation, and I mounted the ESX 3.5 U3 ISO. When I imported the OVF, the CD-ROM wasn't present in the VM, so I had to add it manually. FYI - this is the first time I had this issue.
I just tried the update version, and I can't get EDA to recognize the mounted ISO. The message still says CD not mounted. Any comments?
I noticed that on the virtual appliance website, there is supposed to be version 0.87 out, but clicking on download points to your website which still has 0.85. Any comments?
@kcvman: I don't think that is possible yet, but one workaround you could do is running multiple EDA servers with separate zones, each with different ks script defined. It's a bit of a pain and a... See more...
@kcvman: I don't think that is possible yet, but one workaround you could do is running multiple EDA servers with separate zones, each with different ks script defined. It's a bit of a pain and a configuration hassle to do that way though.
Yes, I can confirm that this problem exists, when the installer asks which NIC to choose. I was working with a fresh EDA server and reimported the PXE files for that EDA.
I am getting the multiple nic issue as well, and after going thru the install, the connectivity did not work, no matter how hard I tried to fix it. The vswif0 had the correct IP address and all n... See more...
I am getting the multiple nic issue as well, and after going thru the install, the connectivity did not work, no matter how hard I tried to fix it. The vswif0 had the correct IP address and all nics were linked to vswitch0, but I was unable to ping the esx server. Also, in the script builder, I would like to see an option to create a VMkernel port that will be used for iSCSI/NAS connection, not just for VMotion. I can, of course, set it up manually using "esxcfg-vmknic -a -i (ip address) -n (netmask) (port group name)", but it would be nice to have that option. I might also add in that I believe the "Add iSCSI target" option is based on ESX 3.0, not 3.5 - the software iSCSI HBA is named vmhba32 in 3.5 instead of vmhba40.
I tried your workaround and found that site-enabled is a directory under /etc/apache2. I looked under the 000-default file and there was an alias concerning netstg2.bin. I tried commenting that... See more...
I tried your workaround and found that site-enabled is a directory under /etc/apache2. I looked under the 000-default file and there was an alias concerning netstg2.bin. I tried commenting that out, and now the install fails midpoint stating that ESX Server 3 installation tree in the directory doesn't match the boot media. Any ideas?
Just to confirm....after editing that file, I do NOT want to import PXE files if I want to keep the HBA drivers? Just leave the ESX CD mounted to the EDA server? I am testing this on VMw... See more...
Just to confirm....after editing that file, I do NOT want to import PXE files if I want to keep the HBA drivers? Just leave the ESX CD mounted to the EDA server? I am testing this on VMware workstation as I speak. Bit of a challenge to get DHCP working since I'm still a Linux noob, but everything seems to work well. Only thing I would wish is to not have to type in the host name right after the pxe boot.....for a true unattended install....
Hmm, chances are you would configure the server in the first place so that only a boot LUN would be present to the server, and disable any IDE disks. That's how VMware recommends it. It would... See more...
Hmm, chances are you would configure the server in the first place so that only a boot LUN would be present to the server, and disable any IDE disks. That's how VMware recommends it. It would be handy if we have an option to keep the HBA drivers just in case I want to boot from LUN. You could give a warning or something if we're going to do that. Boot from LUN will be required for installing ESX on diskless blade servers.
Hi, this sounds like an excellent tool, but what if I want to configure the ESX to boot from SAN?