Linux VM guests have no network connectivity (PVE 8.3, Kernel 6.11)

victorhooi

Well-Known Member
Apr 3, 2018
253
20
58
38
I recently upgraded from Proxmox 8.2 to Proxmox 8.3. I also opted into the 6.11 kernel (
Code:
apt install proxmox-kernel-6.11
).

My guest VMs are mostly Debian hosts - I noticed that many of them seemed to have no network connectivity after rebooting PVE after the update. However, toggling the network interface up, then down seemed to fix it (at least until the next reboot). E.g.:

Code:
sudo ifdown enp6s18
sudo ifup enp6s18
(Although there is one particular host that bringing the interface down then up doesn't seem to work:

CleanShot 2024-12-11 at 13.37.18@2x.png

Anyway - at first I had assumed this loss of network connectivity was this Proxmox 8.3 issue:

https://www.reddit.com/r/Proxmox/comments/1gykmek/upgrading_from_8_to_83_no_network_at_boot/
https://bugzilla.proxmox.com/show_bug.cgi?id=5926

However, as per comment 6 on the bug, it seems like I might have an unrelated issue, as the latest kernel doesn't seem to resolve it for me.

My currently running kernel:
Code:
# uname -a
Linux grandstand-vm02 6.11.0-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.11.0-2 (2024-12-04T10:29Z) x86_64 GNU/Linux

Verbose output of pveversion:
Code:
# pveversion --verbose
proxmox-ve: 8.3.0 (running kernel: 6.11.0-2-pve)
pve-manager: 8.3.1 (running version: 8.3.1/fb48e850ef9dde27)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.19: 7.2-15
pve-kernel-5.13: 7.1-9
proxmox-kernel-6.11.0-2-pve-signed: 6.11.0-2
proxmox-kernel-6.11: 6.11.0-2
proxmox-kernel-6.11.0-1-pve-signed: 6.11.0-1
proxmox-kernel-6.8: 6.8.12-5
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
pve-kernel-5.19.17-2-pve: 5.19.17-2
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 16.2.15+ds-0+deb12u1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-2
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.2
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

Boot messages from journalctl:

https://gist.github.com/victorhooi/dc433e584882a67090cd9cf6646331f3 (Forum says my post has too many characters)

Does anybody have nay idea what might be going on here?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!