Connecting FOG to Virtual Machine

[Sebastian Roth]

@agray Please post a picture of the VM screen so we see to which state it actually boots.

[agray]

@Sebastian-Roth

[agray]

So i found the same issue here (https://forums.fogproject.org/topic/10160/virtualbox-pxe-boot-no-configuration-methods-succeeded).
I don’t understand the solution 100%. If I set ipxe.pxe as the boot file, wouldn’t that be what fog captures instead of my windows VM?

[Sebastian Roth]

@agray What is described in the link you posted is an issues that only occurs when you warm boot (reboot instead of shutdown and cold boot up) the VM. In this case if you don’t use ipxe.pxe as boot file (FOG uses undionly.kkpxe by default) then warm boot will result in “No configuration methods succeeded”. But if you shutdown and start up the VM it works perfectly fine.

So I guess you have a different situation here. You say that a router is serving DHCP in your network. So you installed FOG without DHCP, right? Just want to make sure. I haven’t done this kind of setup in a while but I can imagine the DHCP broadcast packets not making it through to the VM…

[agray]

@Sebastian-Roth said in Connecting FOG to Virtual Machine:

only occurs when you warm boot

Oh I have a .bat file that makes my machine shutdown and i start it when i’m ready.

My FOG Network is set up like this:

Sorry, I don’t have a topology software installed right now, had to use a white board.

It’s odd, because the broadcast packets make it to the machine that is hosting the VM. Would i have to change the host PC to DHCP also for it to make it?

[Sebastian Roth]

@agray Well, let’s try to rule out things. You seem to have Windows installed in the VM as your golden image already. If you boot that up, does it pick up the IP from your router’s DHCP server?

[agray]

@Sebastian-Roth Yes, the VM is getting it’s own DHCP IP address that is coming from the proper router.

[agray]

This post is deleted!

[Sebastian Roth]

@agray Which IP do you get within the VM (Windows booted)?

[agray]

@Sebastian-Roth 192.168.1.141

[Sebastian Roth]

@agray Maybe you have some Windows firewall security software running on the host machine?!

[agray]

@Sebastian-Roth Firewall is completely off for Domain, Private, and Public and it doesn’t have an AV

[Quazz]

Given that it connects to the DHCP server and gets an IP as we can see from the screenshot but fails after loading the IPXE file, I’d suggest serving a different IPXE boot file and see if that works.

You’ll have to modify your router DHCP settings to serve a different file (eg ipxe.pxe instead of undionly.kpxe)

[agray]

@Quazz My router doesn’t have the option to change the file. Let me try booting into iPXE.pxe and i’ll update you.

[Quazz]

@agray Well, if I’m following this thread correctly, the IP of the DHCP server initially is the FOG server itself, not the router.

If you can’t change IPXE options on the router and still want to use its DHCP server rather than FOG DHCP, then you have to set up proxyDHCP via dnsmasq on the FOG server (and disable the dhcp server on it)

[agray]

@Quazz It might be the FOG server serving IPs. I’ve never had an issue booting to PXE and FOG with a physical machine, only this VM.

[agray]

@Quazz I booted to iPXE.pxe but i’m sure what i’m doing with this CL to boot to FOG. I’ve tried ‘autoboot’ but i got the output “Nothing to boot: No such file or directory”

[Quazz]

@agray Where did you change these things?

[agray]

@Quazz I mounted the .iso to my VM and booted to it.

[Quazz]

@agray You need to serve the ipxe.pxe file that’s on the FOG server, since it seems to be the DHCP server.

That being said

I can boot VirtualBox 5.2 VMs to IPXE on undionly.kpxe as well as ipxe.pxe just fine.

Do you have the VirtualBox extension pack installed?