[SOLVED] Cannot start any containers after upgrading and disabling iommu

[SamTV]

I tried to get IOMMU to work. Once it worked every lxc container could not be started. I also created new containers which show the same error. I tried different disks on my machine. Even on the local lvm disk starting an lxc errors out. This is what I find in the logs:

lxc-start 100 20221119073907.167 INFO     confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 100 20221119073907.167 INFO     confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 100 20221119073907.169 INFO     lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start 100 20221119073907.169 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"
lxc-start 100 20221119073907.339 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/rootfs: special device /dev/Data/vm-100-disk-0 does not exist.

lxc-start 100 20221119073907.339 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start produced output: command 'mount /dev/Data/vm-100-disk-0 /var/lib/lxc/.pve-staged-mounts/rootfs' failed: exit code 32

lxc-start 100 20221119073907.346 ERROR    conf - ../src/lxc/conf.c:run_buffer:321 - Script exited with status 32
lxc-start 100 20221119073907.346 ERROR    start - ../src/lxc/start.c:lxc_init:847 - Failed to run lxc.hook.pre-start for container "100"
lxc-start 100 20221119073907.346 ERROR    start - ../src/lxc/start.c:__lxc_start:2008 - Failed to initialize container "100"
lxc-start 100 20221119073907.346 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "100", config section "lxc"
lxc-start 100 20221119073907.847 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "100", config section "lxc"
lxc-start 100 20221119073908.167 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 100 lxc post-stop produced output: umount: /var/lib/lxc/100/rootfs: not mounted

lxc-start 100 20221119073908.168 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 100 lxc post-stop produced output: command 'umount --recursive -- /var/lib/lxc/100/rootfs' failed: exit code 1

lxc-start 100 20221119073908.174 ERROR    conf - ../src/lxc/conf.c:run_buffer:321 - Script exited with status 1
lxc-start 100 20221119073908.174 ERROR    start - ../src/lxc/start.c:lxc_end:988 - Failed to run lxc.hook.post-stop for container "100"
lxc-start 100 20221119073908.174 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
lxc-start 100 20221119073908.174 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options

It says that the directory is not mounted. How should I mount it and why is it not mounted on startup?

 

[SamTV]

The fix is to install binutils via the Proxmox shell:
1. Click on the node under Datacenter
2. Click on Shell under the CreateCT button
3. Type in

sudo apt install bash

 

[clickinfo]

The fix is to install binutils via the Proxmox shell:
1. Click on the node under Datacenter
2. Click on Shell under the CreateCT button
3. Type in

sudo apt install bash

hi, i solved with:

apt install binutils

 

[pJonathan]

The fix is to install binutils via the Proxmox shell:
1. Click on the node under Datacenter
2. Click on Shell under the CreateCT button
3. Type in

sudo apt install bash

Thank you, I was just about to reinstall everything.

 

[t.lamprecht]

FYI: Fixed in newer pve-container 4.3-5 package, see this thread for details.

 

[SamTV]

Thanks for the information and your fast response to the problem. I just upgraded my last proxmox server. Unfortunately it currently only finds version 4.3.4.

 

[t.lamprecht]

Yeah, the sync to our repository CDN was seemingly a bit slower than usual, should be finished now.

 

[SamTV]

Yes. It just appeared as an upgrade. Worked like a charm.