Closed steve-todorov closed 2 years ago
Not yet... Using PXE / TFTP way may be easy for libvirt/qemu, but it will not be so easy for VirtualBox.
That is the reason why I tried to use the legacy option (with booting ISO image) as "long" as possible - because that method works "everywhere" and is easy to setup.
Thanks for the fast response!
I understand. I haven't used VirtulBox for more than 10 years now as my work mainly involves libvirt/qemu. However, I found out these links while checking out for PXE support so I decided to post them here as they might help:
- Create a
$HOME/.VirtualBox/TFTP
folder. The built-in TFTP root is at$HOME/.VirtualBox/TFTP
on Linux or%USERPROFILE%\.VirtualBox\TFTP
on Windows.- Usually, the default boot image name is
pxelinux.0
for PXE boot, but it isvmname.pxe
for the VirtualBox built-in PXE. For example, if we use pxeAndroid as the virtual machine name, we have to make a copy of pxelinux.0 and name it pxeAndroid.pxe under the TFTP root folder.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Oops... Forgot to reply in time. This is still an issue so maybe re-open it? :)
Hey,
I have been using your images for a while now - great work! :)
Since I needed Ubuntu 22.10 (KVM) for some devops experiments I decided to clone your repo and try to add the template / configuration myself. Unfortunately it looks like you can no longer use the Legacy Ubuntu Installer approach:
From what I understand the new way of doing this is through PXELinux and TFTP as mentioned here: https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
Have you had time to investigate this yet?