VM & CT won't start

[gourou76]

Hi,

I am encountering this each time that I start :
Either : kali-linux-2022.1-raspberry-pi-arm64.img
Or : lxc Turnkey Wordpress
Or : openSUSE 15.3

sync_wait: 36 An error occurred in another process (expected sequence number 7)
TASK ERROR: startup for container '101' failed

I run a LUG (https://nui.fr ) so I would be glad to get this working so that I can make insets for the lads.

Cheers,
Jimmy

 

[Stoiko Ivanov]

Try running the container with log-level debug - this might show where the issue is rooted:
https://pve.proxmox.com/pve-docs/chapter-pct.html#_obtaining_debugging_logs

if it does not help - please post the logs you got, and the container-config (`pct config 101`) as well as `pveversion -v`

 

[gourou76]

Hi Stoiko,
Thanks for your input!
Here are the logs as requested.
Best wishes,
Jimmy

 

[Stoiko Ivanov]

this is odd - the following is the actual error :

lxc-start 101 20220425185838.729 NOTICE conf - conf.c:lxc_setup:3756 - The container "101" is set up
lxc-start 101 20220425185838.730 NOTICE start - start.c:start:2159 - Exec'ing "/sbin/init"
lxc-start 101 20220425185838.763 ERROR start - start.c:start:2162 - Exec format error - Failed to exec "/sbin/init"

it cannot exec /sbin/init - and looking a few lines above you see:

lxc-start 101 20220425185838.208 DEBUG conf - conf.c:mount_entry:2135 - Flags for "/sys/fs/fuse/connections" were 4110, required extra flags are 14
lxc-start 101 20220425185838.208 DEBUG conf - conf.c:mount_entry:2179 - Mounted "/sys/fs/fuse/connections" on "/usr/lib/aarch64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections" with filesystem type "none"
lxc-start 101 20220425185838.208 DEBUG conf - conf.c:mount_entry:2179 - Mounted "proc" on "/usr/lib/aarch64-linux-gnu/lxc/rootfs/dev/.lxc/proc" with filesystem type "proc"
lxc-start 101 20220425185838.209 DEBUG conf - conf.c:mount_entry:2179 - Mounted "sys" on "/usr/lib/aarch64-linux-gnu/lxc/rootfs/dev/.lxc/sys" with filesystem type "sysfs"

so it thinks that the container is arm-based (aarch64) - however the 101.conf says arch amd64 ...

* How did you create the container?
* did you manually change something in the PVE sources or configs (mostly lxc)?
* did you manually edit /var/lib/lxc/101/config? (please attach this file in any case)

 

[gourou76]

Hi Stoiko,

>>* How did you create the container?
I used the "wizard" to create the container, nothing special.

>>* did you manually change something in the PVE sources or configs (mostly lxc)?
No

>>* did you manually edit /var/lib/lxc/101/config? (please attach this file in any case)
No

*But* I used the Turnkey template, which could explain the amd and arm mismatch. Container 100 also looks like amd64 (please see attached) and container 100 does not launch as well.

That's very professional of you to analyze the logs and shorten the issue to the "version". As a matter of fact, I have a brand new Raspberry Pi 4B with 8GB of RAM that I would use at our LUG meetings to demonstrate PROXMOX.

Would you know if there is a repository of arm7 templates please?

Let's hope for the best.
Thanks again,
Cheers,
Jimmy

 

[Stoiko Ivanov]

Hm - thanks for the hint with the raspberry - I just now check the pveversion output:
This system is running on a raspberry (or another arm system) - the software is not really provided by us, but
by someone from the community - and sadly I don't really have experience with it - and where you could get
container templates for this - maybe ask the person who distributes the pve-stack for arm?

I hope this helps!