tlkdev 18.1 built appliances no network connection in Proxmox 8.3.2

[claflico]

Updated my lab tkl host to Proxmox 8.3.2 last night after being powered off a year or so. Downloaded the tkldev 18.1 iso and installed it to a VM. Everything works as expected.

Use tkldev to create a custom iso of my docker appliance to convert it to podman and after installing ISO in a new proxomx VM, have no networking. Boot to a different ISO to confirm that VM is getting a dhcp IP.

Use tkldev to create ISOs from the cloned core & mysql appliance repos, install them and they also don't have networking. After considerable troubleshooting, compare /etc/default/grub in the VM created from the tkldev ISO with /etc/default/grub in the VM created from the ISOs built using tlkdev and they are different.

In my vm installed from the tlkdev iso:

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=3
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="consoleblank=0"
GRUB_CMDLINE_LINUX="net.ifnames=0 "

In my vm installed from the custom isos created using tlkdev:

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

Looking in the common folder in the tlkdev VM, I see that the template is correct:

root@tkldev .../products/mysql# cd common
/turnkey/fab/common
root@tkldev .../fab/common# grep -air GRUB_HIDDEN_TIMEOUT_QUIET= ./
./overlays/turnkey.d/x86.d/grub/etc/default/grub:GRUB_HIDDEN_TIMEOUT_QUIET=false

but it seems like the make command isn't updating grub

[JedMeister]

Hi @claflico - If you haven't already, could you build a test core iso to see if that works? I'd do it myself but I'm on holidays ATM :grinning:

Either way I'll be back at my desk in about a week.

[JedMeister]

@OnGle could you please have a look at this one when you get a chance?

[OnGle]

Woops, sorry for the late reply.

My guess is that because net.ifnames=0 is being omitted from the kernel commandline this is causing misconfigured network interfaces. We probably shouldn't still be relying on the old ifnames, but that's something to handle another day.

We did have an issue with some of the arm compat code causing this, but I don't think that was merged when this issue was first posted.

If you're still having issues (I know you might've moved on by now). Please post back and I'll see if I can help.