xen_netfront appears in both of them, I’m fairly sure that’s the ethernet driver you’ll be using.
On the working system can you do ls /sys/class/net
and sudo dmesg | grep net
And show us the output. Can you then do ethtool <the nic> i.e. ethtool eth0 if eth0 is the Interface you’re having issues with and then ethtool -i <the nic>
Then on the non-working machine can you do the same ls /sys/class/net and sudo dmesg | grep net
And if the interface exists do the same ethtool <the nic> and ethtool -i <the nic>
$ show system image
Name Default boot Running
------------------------ -------------- ---------
1.5-rolling-202410280007
1.5-rolling-202406250020 Yes Yes
$ ls /sys/class/net
eth0 eth1 eth2 lo pim6reg
$ sudo dmesg | grep net
[ 0.000000] Command line: BOOT_IMAGE=/boot/1.5-rolling-202406250020/vmlinuz boot=live rootdelay=5 noautologin net.ifnames=0 biosdevname=0 vyos-union=/boot/1.5-rolling-202406250020 console=tty0
[ 0.036130] Kernel command line: BOOT_IMAGE=/boot/1.5-rolling-202406250020/vmlinuz boot=live rootdelay=5 noautologin net.ifnames=0 biosdevname=0 vyos-union=/boot/1.5-rolling-202406250020 console=tty0
[ 0.706664] audit: initializing netlink subsys (disabled)
[ 1.414550] drop_monitor: Initializing network drop monitor service
[ 2.091693] xen_netfront: Initialising Xen virtual ethernet driver
[ 17.711901] systemd[1]: Reached target network-online.target - Network is Online.
[ 17.731418] systemd[1]: Reached target stunnel.target - TLS tunnels for network services - per-config-file target.
[ 18.200665] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 21.445423] process '/usr/sbin/netplugd' started with executable stack
$ ethtool -i eth0
driver: vif
version: 6.6.35-amd64-vyos
firmware-version:
expansion-rom-version:
bus-info: vif-0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
Same VM with issue - rolling update after 20240916
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_NETDEV_BACKEND=m
CONFIG_VMXNET3=m
# CONFIG_FUJITSU_ES is not set
CONFIG_USB4_NET=m
CONFIG_HYPERV_NET=m
# CONFIG_NETDEVSIM is not set
CONFIG_NET_FAILOVER=m
# CONFIG_ISDN is not set
So I would expect it to exist in the latest nightly. Question is if there is some kind of broken dependency?
If you compare something like this between the two boxes?
sudo find / -iname "*netfront*"
Nothing obvious dependencywise that I can detect over at:
~$ sudo find / -iname "*netfront*"
find: File system loop detected; ‘/sys/kernel/debug/pinctrl’ is part of the same file system loop as ‘/sys/kernel/debug’.
/sys/module/xen_netfront
/usr/lib/live/mount/rootfs/1.5-rolling-202406250020.squashfs/usr/lib/modules/6.6.35-amd64-vyos/kernel/drivers/net/xen-netfront.ko
/usr/lib/modules/6.6.35-amd64-vyos/kernel/drivers/net/xen-netfront.ko
Seems like xen_netfront exists in both and is also running according to previous posts.
You could try on both using “sudo journalctl -b” or “dmesg” to find out how the lines looks like right after xen_netfront: Initialising Xen virtual ethernet driver if there is some warning or error there?
Other than that it feels like its 2 different VM-guests where you in the one who doesnt work forgot to enable this virtual adapter in the config of the VM-config within the VM-host.
You can also try (as troubleshoot) to manually edit /config/config.boot (take a backup first both locally and through scp or such) and in there on the one who doesnt work remove the “hw-id” lines to see if VyOS will autodetect your eth0 adapter?
I assume if the virtual adapter at the VM-host got a new MAC-address the hw-id in VyOS will try to map eth0 to a non existing MAC-address which obviously will fail and you will end up with no eth0 (I think).
Hi, thanks.
I would try to investigate more accordingly to your thoughts.
You can also try (as troubleshoot) to manually edit /config/config.boot (take a backup first both locally and through scp or such) and in there on the one who doesnt work remove the “hw-id” lines to see if VyOS will autodetect your eth0 adapter?
But definitely it doesn’t help.
Clean installation of any rolling update after 20240915 doesn’t accept simple configuration like
I mean that system doesn’t see the existing ethx despite they are all available for configure.
Other than that it feels like its 2 different VM-guests where you in the one who doesnt work forgot to enable this virtual adapter in the config of the VM-config within the VM-host.
I do that on the same VM with all the same parameters.
Simple “sudo reboot” to different images gives absolutely different result.
Old system working, new one couldn’t configure existing ethx.
I have tried different types of VM, make the clean install, check is there any incomaptibility with Debian 12 VM… Nothing helps.
All VM’s work absolutely similar.
Yeah if you reboot using the same VM guest then we can rule out that something is missing at the VM-host.
Even if VyOS is (currently) based on Debian 12 (bookworm) VyOS still uses its own custom kernel based on (if we speak about the nightly builds) latest longterm release (6.6.59 as of writing) according to https://kernel.org/ - and its often fairly quickly built when a new release pops up at kernel.org.
Current defconfig is available at:
Perhaps a crossref should be done vs the official Debian 12 debconfig in case Debian 12 when you boot the same VM-guest on a livecd works?
This seems to be the current Debian Linux Kernel config:
However it seems only to contain diffs from the kernel.org defaults (compared to the config used by VyOS who seems to properly define all available settings if they are y/n/m.
Unfortunately, playing with kernel build is far from my level of competence and sometimes i symply don’t understand what i sould do.
at the moment i understand that custom kernel build used in rollings after 20240915 based on latest kernel version 6.6.56 and become incompatible with XEN due to some build options, right?
rolling 20240915 uses 6.6.49 and works fine
Welcome to VyOS!
┌── ┐
. VyOS 1.5-rolling-202409150007
└ ──┘ current
* Support portal: https://support.vyos.io
* Documentation: https://docs.vyos.io/en/latest
* Project news: https://blog.vyos.io
* Bug reports: https://vyos.dev
You can change this banner using "set system login banner post-login" command.
VyOS is a free software distribution that includes multiple components,
you can check individual component licenses under /usr/share/doc/*/copyright
Last login: Sat Nov 2 14:04:09 2024 from
[email protected]:~$ uname -a
Linux .local 6.6.49-amd64-vyos #1 SMP PREEMPT_DYNAMIC Mon Sep 9 10:58:53 UTC 2024 x86_64 GNU/Linux