Auto Deploy - Unable to properly boot ESXi 5.1 properly on HP Blade Servers

We have recently upgraded our vCenter to 5.1.0b, and ofcourse I wanted to update our running (stateless) ESXi blades right away. It appeared this is a little harder then I expected it to be. The image building works fine, the HP tools are included without problems just like the be2net driver. Except the blades I'm using to test my image keep on stalling on starting the hp-ams.sh script/agents.

Then after a while it continues but it goes to the main screen, but I am unable to use any keys. I can't look at the log, it doesn't seem to exit from the 'screensaver' (dark screen).

The method I used to build these Images to run our stateless bladeservers hasn't changed at all, except that I'm using the ESXi 5.1 image to build it now. I have already updated all the firmware of the BL460c G7 blade, so that shouldn't be a problem.

I am also unable to view the logs during the crash so I have no idea how to find out what the problem could be. I have created a script to build ESXi images which I use for Auto Deploy.

 

# Add VMware's Online Depot so we can get the latest Image Profiles and Software Packages

Add-EsxSoftwareDepot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

# Add HP's Online Depot to get access to all of HP's Software Packages

Add-EsxSoftwareDepot http://vibsdepot.hp.com/hpq/oct2012/index.xml

# Add vSphere HA agent

Add-EsxSoftwareDepot https://ap-gda00-vc.its.centric.lan/vSphere-HA-depot/index.xml

# Network Drivers

Add-EsxSoftwareDepot D:\Images\be2net-4.0.355.1-487292\be2net-4.0.355.1-offline_bundle-487292.zip

#

#

# Vars used to set the ESXi image profile name, basically just a time stamped name

$DATESTAMP=get-date -Format yyyMMdd

# Sort the image profiles from VMware's online depot to get the latest image profile

$ImageProfiles = Get-EsxImageProfile | Where-Object {$_.Name -like "*standard*" -and $_.Name -notlike "*s-*" } | Sort-Object "ModifiedTime" -Descending

$ImageProfile = $ImageProfiles[1]

$PROFILEAME="CENTRIC-$DATESTAMP-"+$ImageProfile.Name

# Create a copy of the latest image profile from VMware's online depot

New-EsxImageProfile -CloneProfile $ImageProfile -AcceptanceLevel PartnerSupported -Vendor "Centric" -name $PROFILEAME

# Remove old net-be2net driver package

Remove-EsxSoftwarePackage -ImageProfile $PROFILEAME -SoftwarePackage net-be2net

# Add the HP related packages to the our new image profile

Get-EsxSoftwarePackage -vendor "Hewlett*" | Add-EsxSoftwarePackage -ImageProfile $PROFILEAME

Get-EsxSoftwarePackage -vendor "hp" | Add-EsxSoftwarePackage -ImageProfile $PROFILEAME

# Add the HA Agent related packages to the our new image profile

Get-EsxSoftwarePackage -Name vmware-fdm | Add-EsxSoftwarePackage -ImageProfile $PROFILEAME

# Add the correct be2net-driver to the our new image profile

Get-EsxSoftwarePackage -Name net-be2net | Add-EsxSoftwarePackage -ImageProfile $PROFILEAME

# Export the image profile to a bundle

Export-EsxImageProfile -ImageProfile $PROFILEAME -ExportToBundle -FilePath D:\Images\$PROFILEAME.zip

And finally I apply the Image Profile to an existing entry or Deploy Rule, but to no avail.

Does anyone have ideas how to debug this problem or should I just open up a new case at VMware Support?