After upgrade pve kernel 6.8.12-3,container with tun can't start

chineseswish

New Member
Nov 12, 2024
3
0
1
use pct start 111 --debug find error here:

Bash:
INFO     utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "sh -c "modprobe tun"" for container "111", config section "lxc"
DEBUG    utils - ../src/lxc/utils.c:run_buffer:560 - Script exec sh -c "modprobe tun" 111 lxc autodev produced output: modprobe: FATAL: Module tun not found in directory /lib/modules/6.8.12-4-pve
ERROR    utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 1
ERROR    conf - ../src/lxc/conf.c:lxc_setup:3948 - Failed to run autodev hooks
ERROR    start - ../src/lxc/start.c:do_start:1273 - Failed to setup container "111"

Switch to 6.8.12-2 works,6.8.12-4 also failed.
 
Hi,

Can you please post the container config pct config 111 and the output of pveversion -v?
 
Hi,

Can you please post the container config pct config 111 and the output of pveversion -v?
pveversion -v :
Code:
root@pve8:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-2-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.12-3-pve-signed: 6.8.12-3
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph: 18.2.4-pve3
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
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.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.8
libpve-cluster-perl: 8.0.8
libpve-common-perl: 8.2.5
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.10
libpve-storage-perl: 8.2.5
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.4.0-4
proxmox-backup-client: 3.2.8-1
proxmox-backup-file-restore: 3.2.8-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.2.4
pve-cluster: 8.0.8
pve-container: 5.2.0
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.14-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.4
pve-qemu-kvm: 9.0.2-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

111.conf :
Code:
root@pve8:~# cat /etc/pve/lxc/111.conf
arch: amd64
cores: 2
features: nesting=1
hostname: lxc-gitea
memory: 1024
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=00:0c:29:9e:fe:3d,ip=dhcp,ip6=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: Raid5:vm-111-disk-0,size=500G
startup: order=2,up=5
swap: 512
unprivileged: 1
lxc.hook.autodev: sh -c "modprobe tun"
lxc.mount.entry: /dev/net/tun /var/lib/lxc/111/rootfs/dev/net/tun none bind,create=file
 
Thank you for the output!

Could you please try to get rid of the hook from the LXC config espeically the `modprobe tun`. You can copy the LXC config as a backup `cp /etc/pve/lxc/111.conf /root/111.conf-backup`

And try to start the LXC, and run the `modprobe tun` manually?


Can you also please post the output of `ls /lib/modules/6.8.12-4-pve` command?
 
Thank you for the output!

Could you please try to get rid of the hook from the LXC config espeically the `modprobe tun`. You can copy the LXC config as a backup `cp /etc/pve/lxc/111.conf /root/111.conf-backup`

And try to start the LXC, and run the `modprobe tun` manually?


Can you also please post the output of `ls /lib/modules/6.8.12-4-pve` command?
I try remove autodev script under 6.8.12-3,lxc start success.

Code:
arch: amd64
cores: 2
features: nesting=1
hostname: lxc-gitea
memory: 1024
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=00:0c:29:9e:fe:3d,ip=dhcp,ip6=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: Raid5:vm-111-disk-0,size=500G
startup: order=2,up=5
swap: 512
unprivileged: 1

6.8.12-4-pve modules:
Code:
root@pve8:~# ls /lib/modules/6.8.12-4-pve/
build              modules.builtin            modules.dep      modules.softdep      zfs
kernel             modules.builtin.alias.bin  modules.dep.bin  modules.symbols
modules.alias      modules.builtin.bin        modules.devname  modules.symbols.bin
modules.alias.bin  modules.builtin.modinfo    modules.order    weak-updates

If remove lxc.hook.autodev: sh -c "modprobe tun" line and start lxc succssful,and after run "modprobe tun",containers looks ok.
 
Last edited:

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!