Search results

Thank you Fabian for the procedure, it works very well. I removed stretch-proposed-updates from my sources list ;) Marcori should be really relaxed after that :D

okay, thanks again apparmor 2.11.0-3+deb9u1 => not work apparmor 2.11.0-3 => work fine

Yes, thanks, but I don't have access to boot grub. This is a rental dedicated server.

Thank Wolfgang, but that does not solve my problem. I would like to downgrade my kernel, I search how to

The problem would come from the kernel pve-kernel-4.13.8-2-pve: 4.13.8-28 see : https://forum.proxmox.com/threads/pve-5-1-kvm-broken-on-old-cpus.37666/

At first, the problem occurs after one of these updates : apparmor dbus libapparmor-perl libapparmor1 libc-bin libc-dev-bin libc-l10n libc6 libc6-dev libcurl3-gnutls libdbi1 libdbus-1-3 libicu57 libpython2.7 libpython2.7-minimal libpython2.7-stdlib linux-compiler-gcc-6-x86...

Hello, Probably following an update from cron-apt (security only), lxc container does not reponse. I restarted the server and now, the container will not start. Someone would see a solution? I tried : ~# lxc-start -n 100 -F -lDEBUG -o lxc-100.log --logpriority TRACE lxc-start: 100...