I have been able to successfully create a virtual machine using the VMware
compute resource. I have run into a snag though, that hopefully someone
can provide me with a fix/workaround.
On a newly created VM, the boot order is set to the default, which is 1.
removable media, 2. local HDD, 3. NICs.
The VM's very first boot works great by PXE booting and gets the build
orders successfully. However, once the VM has an OS installed it never
boots PXE again which means I never get another shot at another Build order.
> I have been able to successfully create a virtual machine using the VMware
> compute resource. I have run into a snag though, that hopefully someone
> can provide me with a fix/workaround.
>
> On a newly created VM, the boot order is set to the default, which is 1.
> removable media, 2. local HDD, 3. NICs.
>
> The VM's very first boot works great by PXE booting and gets the build
> orders successfully. However, once the VM has an OS installed it never
> boots PXE again which means I never get another shot at another Build order.
That works as intended. Unfortunately the way to change the boot
order currently is to do it in VMware.
A possible workaround would be to add an IPMI BMC interface to your hosts
in VMWare (not sure if that's available?). If configured in Foreman, it
will show you a small panel to choose the boot device in the UI, and it
will contact the BMC interface for that.
···
On 06/16, lawre wrote:
>
> Any suggestions?
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
Is this a limitation of fog, or does VMWare not actually expose the 'boot
order' option?
···
On Wed, Jun 17, 2015 at 8:12 AM, Daniel Lobato Garcia wrote:
On 06/16, lawre wrote:
I have been able to successfully create a virtual machine using the
VMware
compute resource. I have run into a snag though, that hopefully someone
can provide me with a fix/workaround.
On a newly created VM, the boot order is set to the default, which is 1.
removable media, 2. local HDD, 3. NICs.
The VM’s very first boot works great by PXE booting and gets the build
orders successfully. However, once the VM has an OS installed it never
boots PXE again which means I never get another shot at another Build
order.
That works as intended. Unfortunately the way to change the boot
order currently is to do it in VMware.
A possible workaround would be to add an IPMI BMC interface to your hosts
in VMWare (not sure if that’s available?). If configured in Foreman, it
will show you a small panel to choose the boot device in the UI, and it
will contact the BMC interface for that.
