Update Version: 1.3.0-RC-14, Can't capture image from Virtualbox.
-
Did your fog server’s IP change? What is it’s IP?
-
Update
Regular Computers manages to connect to the server.
Server IP is still the same. -
@ek_N Doublecheck your VM settings, and try a new VM and see if it network boots or not. It doesn’t need an OS to do this, it can be totally blank.
-
Servers IP is still the same. 10.1.101.60
-
What’s the boot file you’re using? Try ipxe.pxe please.
-
@Tom-Elliott said in Update Version: 1.3.0-RC-14, Can't capture image from Virtualbox.:
ipxe.pxe
I have Windows DHCP so i’ve changed it. Still doesn’t work but i guess it might take some time before it applies.
-
If this is a freshly created VM, IS the NIC bridged or NAT?
-
@Tom-Elliott Bridged, tried NAT as well but didn’t work either.
-
@Tom-Elliott I’m stupid. ipxe.pxe solved it. I was in the wrong scope of vlan. Thank you so much!
-
@Tom-Elliott Is undionly.kpxe not used anymore? Long time since i set this up.
-
@ek_N undionly.kpxe works fine, but it has never worked that good for VirtualBox.
The only fix I ever got to subsequently reboot VBox systems was by using ipxe.pxe.
If you still want to use undionly.kpxe the VBox reboot needs to be cold started (power off, power back on).
-
@ek_N said in Update Version: 1.3.0-RC-14, Can't capture image from Virtualbox.:
i guess it might take some time before it applies.
No, changes in Windows DHCP are immediate.
