I'm glad it's working for you in Traiano.  
Can you check on the boot order for your VM?  I bet it's unchanged, and what Cobbler is actually doing is setting up a "personalized" pxe boot menu for your system that just loads local disk.  I briefly checked out the pxe_just_once flag and it described how it functions but not how it accomplishes its function.  I'm guessing it works like that.

On Sun, Oct 29, 2017 at 11:54 AM, Traiano Welcome <traiano@gmail.com> wrote:
Hi Matt

On Sun, Oct 29, 2017 at 6:49 PM, Matt Luettgen <mattluettgen@gmail.com> wrote:
> There is a way to have cobbler disable DHCP after the install.  I'd have to
> login to work to tell you how to do it.  What I do is what Locane said.  Set
> the boot to Disk first, DHCP/PXE 2nd.  First VM harddisk fails, so DHCP/PXE
> is the next step.  Then cobbler installs the OS.  The next boot attempt goes
> to the OS (because the boot order says disk first...)

Thanks, that works beautifully :-)
I think the cobbler configuration option is: pxe_just_once: 1


>
> On Sun, Oct 29, 2017 at 12:19 PM, Traiano Welcome <traiano@gmail.com> wrote:
>>
>> Hi Locane
>>
>>
>> On Sun, Oct 29, 2017 at 1:40 PM, Locane <locane@gmail.com> wrote:
>> > I don't work with VMs very much, but unless Virtual Box has some kind of
>> > special API that allows you to connect to it and adjust "BIOS settings"
>> > the
>> > answer is probably No.
>>
>> That makes sense. I was hoping cobbler might include such a feature.
>>
>>
>> >
>> > Setting things like boot order or booting to a specific device requires
>> > systems support from the manufacturer, in my experience.  Supermicro's
>> > IPMI
>> > for example.
>> >
>>
>> It seems cobbler supports this via IPMI on bare metal.
>>
>>
>> > Why does your boot order have to be PXE -> Disk?  I think it should be
>> > flipped...  If the disk is empty it should try PXE next.
>> >
>>
>>
>> For the initial installation, the VM device boot order needs to be PXE ->
>> Disk.
>> Once the installation has completed, reboot happens and the order
>> needs to be disk first, or else we get a re-install loop, or hang.
>> Basically my objective is to get a smooth boot into a newly installed
>> system after the initial installation where the VM started off booting
>> with PXE.
>>
>>
>> > Again though, don't work with VMs very much.
>> >
>> > PS: SE Linux gets in the way of cobbler in pretty much everything.  Just
>> > turn it off.
>> >
>> > On Oct 29, 2017 3:13 AM, "Traiano Welcome" <traiano@gmail.com> wrote:
>> >>
>> >> Hi List
>> >>
>> >> I'm using cobbler to install virtualbox vms, which requires the boot
>> >> order to be PXE -> Disk.
>> >>
>> >> However I'm not sure how to get cobbler to reconfigure the boot order
>> >> so the VM boots off the disk after the install is complete (my VM
>> >> attempts to boot off pxe again but fails because this is disabled in
>> >> cobbler).
>> >>
>> >> Is there a confguration option in cobbler / kickstart that
>> >> reconfigures the virtualbox device boot order once the install is
>> >> complete?
>> >>
>> >> Thanks,
>> >> Traiano
>> >> _______________________________________________
>> >> cobbler mailing list -- cobbler@lists.fedorahosted.org
>> >> To unsubscribe send an email to cobbler-leave@lists.fedorahosted.org
>> >
>> >
>> > _______________________________________________
>> > cobbler mailing list -- cobbler@lists.fedorahosted.org
>> > To unsubscribe send an email to cobbler-leave@lists.fedorahosted.org
>> >
>> _______________________________________________
>> cobbler mailing list -- cobbler@lists.fedorahosted.org
>> To unsubscribe send an email to cobbler-leave@lists.fedorahosted.org
>
>
>
> _______________________________________________
> cobbler mailing list -- cobbler@lists.fedorahosted.org
> To unsubscribe send an email to cobbler-leave@lists.fedorahosted.org
>
_______________________________________________
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-leave@lists.fedorahosted.org