Hi All.
I have recently updated to the latest version of Proxmox, after which it appears that nested virt no longer works. I noticed this because after the reboot docker, which is hosted in a privileged CT can no longer run any containers.
What ive tried so far:
Any ideas? What should I be looking at to diagnose this further?
CT Config as an example, but ive created a fresh CT with nesting enabled and it does not work:
Thanks for any help.
I have recently updated to the latest version of Proxmox, after which it appears that nested virt no longer works. I noticed this because after the reboot docker, which is hosted in a privileged CT can no longer run any containers.
What ive tried so far:
- Ive tried updating to the test kernel assuming it may be something with the kernel update.
- Ive created a fresh CT and attempted to run a docker container with no luck.
- Ive double checked all my config like iommu etc, but nothing has changed.
cat /sys/module/kvm_intel/parameters/nested is Y.Any ideas? What should I be looking at to diagnose this further?
Code:
Virtual Environment 8.1.10
6.5.13-5-pve < not working
6.8.4-2-pve < not workingCT Config as an example, but ive created a fresh CT with nesting enabled and it does not work:
Code:
arch: amd64
cores: 12
features: mount=cifs,nesting=1
hostname: dockerhost
memory: 20480
net0: name=eth0,bridge=vmbr0,hwaddr=BC:24:11:2D:AC:0C,ip=dhcp,ip6=dhcp,type=veth
net1: name=eth1,bridge=vmbr0,hwaddr=BC:24:11:F2:0D:8F,ip=dhcp,ip6=dhcp,type=veth
onboot: 1
ostype: fedora
rootfs: storage:subvol-102-disk-0,size=256G
swap: 8192
lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file 0, 0
lxc.mount.entry: /dev/dri dev/dri none bind,optional,create=dir
lxc.cgroup2.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net dev/net none bind,create=dir
lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=fileThanks for any help.
Last edited: