01-08-2014 01:42 PM
I have been able to run a redhat 6 build plan successfully on a virtual machine using a E1000 network adapter, but when I try to run the same build plan against a VM using a VMXNET3 adapter, the build plan fails on the "polling for maintenance mode" step with the message:
The virtual machine has not communicated back to the core. This may be due to a lack of network connectivity. Verify the IP settings and ensure the new virtual machine’s network connectivity to the core. Try logging in to the VM console to diagnose the failure.
When I look at the console the machine is at the "welcome to redhat" blue screen.
What could be going on here?
08-05-2014 10:57 AM
I am having the same issue here. I think the 'latest' vmxnet3 Linux NIC drivers (for vcenter 5.5) need to be injected into the SA boot agent. The problem I am having is im not sure which initrd.img file to inject them into.
08-06-2014 03:42 AM
Some hints on how to add drivers to pxe images:
But only contains details for winpe. I also have good procedures for linux pxe images (doen is previous SA version); but they are HP PSO intellectual property sorry.
If you have time and a lab environment... not trivial, neither impossible, good luck.
08-06-2014 02:05 PM - edited 08-06-2014 02:07 PM
Thanks for the reply Ramon.
We actually got this issue resolved. It was not a driver issue at all. It turns out Red Hats Anaconda distributes DHCP packets in unicast form, the Windows PXE environment pushes "broadcast" DHCP packets. There was a configuration on our network switches that was not allowing unicast packets to be forwarded back to the client (the new builds). A change on our network switches fixed this issue.
However - I did end up rebuilding the initrd.img file that gets loaded for OSBP's to run. I used the following link (with a few minor adjustments for RHEL6), and injected the latest vmxnet3 drivers in /opt/opsware/boot/tftpboot/rhel60/initrd.img.
RHEL6 by default does come with vmxnet3 NIC drivers provided by Red Hat. I do remember having to inject the vmxnet3 and pvscsi drivers into the RHEL5 initrd.img though.