Deploying ESX 5.1

Has anyone had luck with deploying ESX 5.1 via foreman provisioning methods
(PXE + Kickstart)? So far, I've made it to the kickstart phase of the
provisioning process. Note that I followed the guide on
VMware ESXi - Foreman, but adapted to
some of the changes in ESX 5.1. Here is what my configuration is so far:

PXE config:
default ESX5u1-x86_64
LABEL ESX5u1-x86_64
kernel boot/vmware/mboot.c32
MENU LABEL ESX5u1-x86_64
APPEND -c boot/vmware/boot.cfg

Boot.cfg:
bootstate=0
title=Loading ESXi installer
kernel=/boot/vmware/tboot.b00
kernelopt=ks=http://puppet.doit.missouri.edu/unattended/provision
modules=/boot/vmware/b.b00 — /boot/vmware/useropts.gz —
/boot/vmware/k.b00 — /boot/vmware/a.b00 — /boot/vmware/ata-pata.v00 —
/boot/vmware/ata-pata.v01 — /boot/vmware/ata-pata.v02 —
/boot/vmware/ata-pata.v03 — /boot/vmware/ata-pata.v04 —
/boot/vmware/ata-pata.v05 — /boot/vmware/ata-pata.v06 —
/boot/vmware/ata-pata.v07 — /boot/vmware/block-cc.v00 —
/boot/vmware/ehci-ehc.v00 — /boot/vmware/s.v00 —
/boot/vmware/weaselin.i00 — /boot/vmware/ima-qla4.v00 —
/boot/vmware/ipmi-ipm.v00 — /boot/vmware/ipmi-ipm.v01 —
/boot/vmware/ipmi-ipm.v02 — /boot/vmware/misc-cni.v00 —
/boot/vmware/misc-dri.v00 — /boot/vmware/net-be2n.v00 —
/boot/vmware/net-bnx2.v00 — /boot/vmware/net-bnx2.v01 —
/boot/vmware/net-cnic.v00 — /boot/vmware/net-e100.v00 —
/boot/vmware/net-e100.v01 — /boot/vmware/net-enic.v00 —
/boot/vmware/net-forc.v00 — /boot/vmware/net-igb.v00 —
/boot/vmware/net-ixgb.v00 — /boot/vmware/net-nx-n.v00 —
/boot/vmware/net-r816.v00 — /boot/vmware/net-r816.v01 —
/boot/vmware/net-s2io.v00 — /boot/vmware/net-sky2.v00 —
/boot/vmware/net-tg3.v00 — /boot/vmware/ohci-usb.v00 —
/boot/vmware/sata-ahc.v00 — /boot/vmware/sata-ata.v00 —
/boot/vmware/sata-sat.v00 — /boot/vmware/sata-sat.v01 —
/boot/vmware/sata-sat.v02 — /boot/vmware/sata-sat.v03 —
/boot/vmware/scsi-aac.v00 — /boot/vmware/scsi-adp.v00 —
/boot/vmware/scsi-aic.v00 — /boot/vmware/scsi-bnx.v00 —
/boot/vmware/scsi-fni.v00 — /boot/vmware/scsi-hps.v00 —
/boot/vmware/scsi-ips.v00 — /boot/vmware/scsi-lpf.v00 —
/boot/vmware/scsi-meg.v00 — /boot/vmware/scsi-meg.v01 —
/boot/vmware/scsi-meg.v02 — /boot/vmware/scsi-mpt.v00 —
/boot/vmware/scsi-mpt.v01 — /boot/vmware/scsi-mpt.v02 —
/boot/vmware/scsi-qla.v00 — /boot/vmware/scsi-qla.v01 —
/boot/vmware/scsi-rst.v00 — /boot/vmware/uhci-usb.v00 —
/boot/vmware/tools.t00 — /boot/vmware/imgdb.tgz —
/boot/vmware/imgpayld.tgz
build=
updated=0

So, my progress so far allows me to boot the ESX 5.1 installer, however
when the installer gets to the kickstart stage ("reading installation
script"), it errors out with a 404 from foreman. I get the feeling
something is off with name resolution or something… anyways I'm curious if
anyone else has had success in this arena.

Are you able to jump to a different console where errors are being logged (CRTL-ALT-F2) through CRTL-ALT-F7

Corey Osman
corey@logicminds.biz
678-348-0582 (Pacific Time)

Green IT and Datacenter Automation Specialist

··· On Jun 19, 2012, at 8:29 AM, Luke Baker wrote:

Has anyone had luck with deploying ESX 5.1 via foreman provisioning methods (PXE + Kickstart)? So far, I’ve made it to the kickstart phase of the provisioning process. Note that I followed the guide on VMware ESXi - Foreman, but adapted to some of the changes in ESX 5.1. Here is what my configuration is so far:

PXE config:
default ESX5u1-x86_64
LABEL ESX5u1-x86_64
kernel boot/vmware/mboot.c32
MENU LABEL ESX5u1-x86_64
APPEND -c boot/vmware/boot.cfg

Boot.cfg:
bootstate=0
title=Loading ESXi installer
kernel=/boot/vmware/tboot.b00
kernelopt=ks=http://puppet.doit.missouri.edu/unattended/provision
modules=/boot/vmware/b.b00 — /boot/vmware/useropts.gz — /boot/vmware/k.b00 — /boot/vmware/a.b00 — /boot/vmware/ata-pata.v00 — /boot/vmware/ata-pata.v01 — /boot/vmware/ata-pata.v02 — /boot/vmware/ata-pata.v03 — /boot/vmware/ata-pata.v04 — /boot/vmware/ata-pata.v05 — /boot/vmware/ata-pata.v06 — /boot/vmware/ata-pata.v07 — /boot/vmware/block-cc.v00 — /boot/vmware/ehci-ehc.v00 — /boot/vmware/s.v00 — /boot/vmware/weaselin.i00 — /boot/vmware/ima-qla4.v00 — /boot/vmware/ipmi-ipm.v00 — /boot/vmware/ipmi-ipm.v01 — /boot/vmware/ipmi-ipm.v02 — /boot/vmware/misc-cni.v00 — /boot/vmware/misc-dri.v00 — /boot/vmware/net-be2n.v00 — /boot/vmware/net-bnx2.v00 — /boot/vmware/net-bnx2.v01 — /boot/vmware/net-cnic.v00 — /boot/vmware/net-e100.v00 — /boot/vmware/net-e100.v01 — /boot/vmware/net-enic.v00 — /boot/vmware/net-forc.v00 — /boot/vmware/net-igb.v00 — /boot/vmware/net-ixgb.v00 — /boot/vmware/net-nx-n.v00 — /boot/vmware/net-r816.v00 — /boot/vmware/net-r816.v01 — /boot/vmware/net-s2io.v00 — /boot/vmware/net-sky2.v00 — /boot/vmware/net-tg3.v00 — /boot/vmware/ohci-usb.v00 — /boot/vmware/sata-ahc.v00 — /boot/vmware/sata-ata.v00 — /boot/vmware/sata-sat.v00 — /boot/vmware/sata-sat.v01 — /boot/vmware/sata-sat.v02 — /boot/vmware/sata-sat.v03 — /boot/vmware/scsi-aac.v00 — /boot/vmware/scsi-adp.v00 — /boot/vmware/scsi-aic.v00 — /boot/vmware/scsi-bnx.v00 — /boot/vmware/scsi-fni.v00 — /boot/vmware/scsi-hps.v00 — /boot/vmware/scsi-ips.v00 — /boot/vmware/scsi-lpf.v00 — /boot/vmware/scsi-meg.v00 — /boot/vmware/scsi-meg.v01 — /boot/vmware/scsi-meg.v02 — /boot/vmware/scsi-mpt.v00 — /boot/vmware/scsi-mpt.v01 — /boot/vmware/scsi-mpt.v02 — /boot/vmware/scsi-qla.v00 — /boot/vmware/scsi-qla.v01 — /boot/vmware/scsi-rst.v00 — /boot/vmware/uhci-usb.v00 — /boot/vmware/tools.t00 — /boot/vmware/imgdb.tgz — /boot/vmware/imgpayld.tgz
build=
updated=0

So, my progress so far allows me to boot the ESX 5.1 installer, however when the installer gets to the kickstart stage (“reading installation script”), it errors out with a 404 from foreman. I get the feeling something is off with name resolution or something… anyways I’m curious if anyone else has had success in this arena.


You received this message because you are subscribed to the Google Groups “Foreman users” group.
To view this discussion on the web visit https://groups.google.com/d/msg/foreman-users/-/w5ctu5nhi-MJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

Ah, it looks like (for some reason) the host being built was being assigned
a different DHCP address than what was configured by foreman. I ended up
blowing away the dhcpd.leases file and restarting dhcpd and the build
worked as expected.

··· On Tuesday, June 19, 2012 10:14:45 AM UTC-5, Corey Osman wrote: > > Are you able to jump to a different console where errors are being logged > (CRTL-ALT-F2) through CRTL-ALT-F7 > > > Corey Osman > corey@logicminds.biz > 678-348-0582 (Pacific Time) > > Green IT and Datacenter Automation Specialist > > > > > On Jun 19, 2012, at 8:29 AM, Luke Baker wrote: > > Has anyone had luck with deploying ESX 5.1 via foreman provisioning > methods (PXE + Kickstart)? So far, I've made it to the kickstart phase of > the provisioning process. Note that I followed the guide on > http://theforeman.org/projects/foreman/wiki/VMware_ESXi, but adapted to > some of the changes in ESX 5.1. Here is what my configuration is so far: > > *PXE config:* > default ESX5u1-x86_64 > LABEL ESX5u1-x86_64 > kernel boot/vmware/mboot.c32 > MENU LABEL ESX5u1-x86_64 > APPEND -c boot/vmware/boot.cfg > > *Boot.cfg:* > bootstate=0 > title=Loading ESXi installer > kernel=/boot/vmware/tboot.b00 > kernelopt=ks=http://puppet.doit.missouri.edu/unattended/provision > modules=/boot/vmware/b.b00 --- /boot/vmware/useropts.gz --- > /boot/vmware/k.b00 --- /boot/vmware/a.b00 --- /boot/vmware/ata-pata.v00 --- > /boot/vmware/ata-pata.v01 --- /boot/vmware/ata-pata.v02 --- > /boot/vmware/ata-pata.v03 --- /boot/vmware/ata-pata.v04 --- > /boot/vmware/ata-pata.v05 --- /boot/vmware/ata-pata.v06 --- > /boot/vmware/ata-pata.v07 --- /boot/vmware/block-cc.v00 --- > /boot/vmware/ehci-ehc.v00 --- /boot/vmware/s.v00 --- > /boot/vmware/weaselin.i00 --- /boot/vmware/ima-qla4.v00 --- > /boot/vmware/ipmi-ipm.v00 --- /boot/vmware/ipmi-ipm.v01 --- > /boot/vmware/ipmi-ipm.v02 --- /boot/vmware/misc-cni.v00 --- > /boot/vmware/misc-dri.v00 --- /boot/vmware/net-be2n.v00 --- > /boot/vmware/net-bnx2.v00 --- /boot/vmware/net-bnx2.v01 --- > /boot/vmware/net-cnic.v00 --- /boot/vmware/net-e100.v00 --- > /boot/vmware/net-e100.v01 --- /boot/vmware/net-enic.v00 --- > /boot/vmware/net-forc.v00 --- /boot/vmware/net-igb.v00 --- > /boot/vmware/net-ixgb.v00 --- /boot/vmware/net-nx-n.v00 --- > /boot/vmware/net-r816.v00 --- /boot/vmware/net-r816.v01 --- > /boot/vmware/net-s2io.v00 --- /boot/vmware/net-sky2.v00 --- > /boot/vmware/net-tg3.v00 --- /boot/vmware/ohci-usb.v00 --- > /boot/vmware/sata-ahc.v00 --- /boot/vmware/sata-ata.v00 --- > /boot/vmware/sata-sat.v00 --- /boot/vmware/sata-sat.v01 --- > /boot/vmware/sata-sat.v02 --- /boot/vmware/sata-sat.v03 --- > /boot/vmware/scsi-aac.v00 --- /boot/vmware/scsi-adp.v00 --- > /boot/vmware/scsi-aic.v00 --- /boot/vmware/scsi-bnx.v00 --- > /boot/vmware/scsi-fni.v00 --- /boot/vmware/scsi-hps.v00 --- > /boot/vmware/scsi-ips.v00 --- /boot/vmware/scsi-lpf.v00 --- > /boot/vmware/scsi-meg.v00 --- /boot/vmware/scsi-meg.v01 --- > /boot/vmware/scsi-meg.v02 --- /boot/vmware/scsi-mpt.v00 --- > /boot/vmware/scsi-mpt.v01 --- /boot/vmware/scsi-mpt.v02 --- > /boot/vmware/scsi-qla.v00 --- /boot/vmware/scsi-qla.v01 --- > /boot/vmware/scsi-rst.v00 --- /boot/vmware/uhci-usb.v00 --- > /boot/vmware/tools.t00 --- /boot/vmware/imgdb.tgz --- > /boot/vmware/imgpayld.tgz > build= > updated=0 > > > So, my progress so far allows me to boot the ESX 5.1 installer, however > when the installer gets to the kickstart stage ("reading installation > script"), it errors out with a 404 from foreman. I get the feeling > something is off with name resolution or something.. anyways I'm curious if > anyone else has had success in this arena. > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/foreman-users/-/w5ctu5nhi-MJ. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to > foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/foreman-users?hl=en. > > >