Could not start download: Operation not supported
-
Linux Version: Ubuntu 18.04
FOG Version: 1.5.4I have just started my first FOG setup and have gotten to the last part of the setup and of course it fails. My setup for my FOG environment is I have Oracle VM VirtualBox running on my windows 10 computer. On that I have my Linux image with FOG running on it and and in another image in VirtualBox I have my Win10 image that I have made and is ready to deploy. We use our Dell SonicWall router for our DHCP server. I am getting this error when I boot up my Win10 image in VirtualBox so I can capture the image. I can provide any additional information.
-
@BaileyMoore From the picture you posted it looks like the VM is set to UEFI but it tries to load
undionly.kpxe
which is the iPXE binary for old legacy BIOS machines. Try setting toipxe.efi
on your DHCP server and see how it goes.Somewhere in the back of my mind I think I remember that UEFI PXE booting in VirtualBox has an issue. But give it a go and see how things work for you.
-
@Sebastian-Roth Same thing happened, thanks for the reply though
-
@baileymoore do you know if the VM is booting in uefi or not? If you can boot them via via legacy use the ipxe.pxe boot file rather than undionly.kpxe. I would often see similar issues when I was running virtual box as my host environment. I found, way back then, using the ipxe.pxe file worked on cold start or warm boot of the vms I was working with.
-
@tom-elliott It’s doing the same thing, thanks for the reply though.
-
I was finally able to find the solution to my issue, this can be marked as solved.
https://wiki.fogproject.org/wiki/index.php/Other_DHCP_Configurations#0.32_and_below_5 -
@baileymoore Just for clarity, if you are using pxelinux.0 you will find no joy with current hardware and FOG 1.5.4. The FOS kernels will not boot correctly (or at all) with pxelinux.0 in the picture.
-
@george1421 Yeah I was finally able to get it working with undionly.kpxe. Thanks for the help though!
-
Oracle Virtualbox only supports legacy PXE booting, which is why ipxe.efi didn’t (and couldn’t) work.