Search results

Wow. Flashback here. This is so eerily similar to the issue I had trying to run PVE as a container (empty /etc/pve/ dir), but this time it's not. This was a full-blown install of Deb11 and then trying to install PVE7 on top of it. Due to this issue (which I'm not convinced apparmor alone is...

Just purged it and tried installing again as actual root user instead of sudo. Same issues at the same spots. Here's a note of interest: Setting up lxc-pve (4.0.9-2) ... apparmor_parser: Unable to replace "/usr/bin/lxc-start". Profile doesn't conform to protocol apparmor_parser: Unable to...

Title says it. I'm most of the way through setting up a new PVE 7 system on top of a default Debian 11 install. Basically using this guide with some tweaks. https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch I used this PVE 7 repo: deb [arch=amd64]...

root@proxmox:/# uname -a Linux proxmox 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 GNU/Linux My host is Ubuntu 16.04 LTS. PVE is a LXC container with the default LXC image for Deb8: Debian, Jessie, AMD64. I know it's odd to run PVE like this, so here's my setup: Home...

After more playing around: root@proxmox:/# service pve-cluster restart Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details. root@proxmox:/# systemctl -l status pve-cluster.service ● pve-cluster.service - The Proxmox VE cluster...

I saw "SOLVED" in the title hoping to find the solution, but no-go. Reboots don't help. I just installed a fresh PVE 4.3 setup as a LXC container (minimal Deb8, then upgraded to PVE as per the wiki). No issues EXCEPT for this one which seems to be plaguing others so too. I do NOT have any...