May 07 10:15:18 pmx2 systemd[1]: Starting PVE LXC Container: 505...
May 07 10:15:18 pmx2 lxc-start[14492]: lxc-start: 505: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
May 07 10:15:18 pmx2 lxc-start[14492]: lxc-start: 505: tools/lxc_start.c: main: 371 The container failed to start.
May 07 10:15:18 pmx2 lxc-start[14492]: lxc-start: 505: tools/lxc_start.c: main: 373 To get more details, run the container in foreground mode.
May 07 10:15:18 pmx2 lxc-start[14492]: lxc-start: 505: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.
-- Unit pve-container@505.service has begun starting up.
May 07 10:31:43 pmx2 audit[5004]: AVC apparmor="DENIED" operation="mount" info="failed mntpnt match" error=-13 profile="/usr/bin/lxc-start" name="/" pid=5004 comm="lxc-start" flags="rw,
May 07 10:31:43 pmx2 kernel: audit: type=1400 audit(1525714303.665:12): apparmor="DENIED" operation="mount" info="failed mntpnt match" error=-13 profile="/usr/bin/lxc-start" name="/" pi
May 07 10:31:43 pmx2 lxc-start[4997]: lxc-start: 505: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
May 07 10:31:43 pmx2 lxc-start[4997]: lxc-start: 505: tools/lxc_start.c: main: 371 The container failed to start.
May 07 10:31:43 pmx2 lxc-start[4997]: lxc-start: 505: tools/lxc_start.c: main: 373 To get more details, run the container in foreground mode.
May 07 10:31:43 pmx2 lxc-start[4997]: lxc-start: 505: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.
May 07 10:31:43 pmx2 systemd[1]: pve-container@505.service: Control process exited, code=exited status=1
May 07 10:31:43 pmx2 systemd[1]: pve-container@505.service: Killing process 5004 (lxc-start) with signal SIGKILL.
May 07 10:31:43 pmx2 systemd[1]: Failed to start PVE LXC Container: 505.
-- Subject: Unit pve-container@505.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pve-container@505.service has failed.
--
-- The result is failed.
May 07 10:31:43 pmx2 systemd[1]: pve-container@505.service: Unit entered failed state.
May 07 10:31:43 pmx2 systemd[1]: pve-container@505.service: Failed with result 'exit-code'.
May 07 10:31:43 pmx2 pct[4994]: command 'systemctl start pve-container@505' failed: exit code 1
May 07 10:31:43 pmx2 pct[4993]: <root@pam> end task UPID:pmx2:00001382:00002916:5AF08D7F:vzstart:505:root@pam: command 'systemctl start pve-container@505' failed: exit code 1
^^^^^
FIXED IN: Linux pmx2 4.15.17-1-pve #1 SMP PVE 4.15.17-8 (Thu, 03 May 2018 08:43:38 +0200) x86_64 GNU/Linux
added pve-no-subscription, updated, resolved.
Hopefully there will be a new 5.1 ISO rolled shortly, since this is broken from install.
it's not. it's only broken if you don't setup the PVE repositories/subscription correctly after installation, ignore the warnings/errors that apt gives you because of that misconfiguration, and then install updates for Debian only but not PVE. also, your problem is not related to this thread in any way.
I would guess there are different Bios version on this server installed.I appears there is some incompatibility with the new kernel but I am not sure exactly where as they are all the same hardware except for some CPU differences but only set of CPUs is different than the others that are working.
Not trying to be difficult here, perhaps we're facing a language/translation barrier.
Statement "Hopefully there will be a new 5.1 ISO rolled shortly, since this is broken from install."
That statement is true.
If you:
1. Download 5.1 ISO
2. Install
3. Create VM's
4. Try to start them. They fail.
This is repeatable across half a dozen opteron-based machines I have in the lab.
They won't start UNTIL you (1) add the repos, and (2) update, and (3) reboot
That's broken from installation. Hence the hope that a new ISO will be rolled shortly.