Search results

Halleluja, after 10 months I am finally able to upgrade a Debian 10 LXC to Debian 11! This simple thing seems to have done the trick. Oddly I didn't have to send any signal. Thanks!

Hmm so this could be my issue on Debian 10 --> 11 as well? Thanks for the tip anyway, I will try this. Just means having to monitor the upgrade process and do a timely kill before the entire thing comes to a grinding halt, right?

Nesting is enabled on my containers. For the rest I can't even get as far as to be able to change systemd files. During the Deb 10 --> 11 upgrade I get: After that, the LXC is broken.

Is there any progress on this topic? I am still unable to upgrade Debian 10 LXC to Debian 11.

Is there any solution for upgrading my Debian 10 containers yet?

I still have this issue and would like some points on how to upgrade the containers.

Any tips on how to proceed?

I finished the Debian 11 upgrade now (took about 8 hours), and now the LXC will not start. Debug log: https://paste.gg/p/anonymous/140f149e23e34a0ea2a2c29fe2de5a3e/files/48616fbaefe249a08b821fb7cc123c6f/raw Config: #Nextcloud arch: amd64 features: keyctl=1,nesting=1 hostname: holt memory: 4096...

I am having a lot of issues trying to upgrade my Debian 10 containers to Debian 11, after having upgraded the host OS from Proxmox 6 to 7. Overall the upgrades take long, I see a lot of these type of messages combined with a lot of very long timeouts: Failed to reload daemon: Transport...

Well, same for me. So I downloaded the drivers from Nvidia site, the run file. You can remove the Debian packages before, or the installer will tell you to do so I believe.

Not really bothered, am using the Nvidia run-file installation now, works fine with Proxmox. Couldn't get the Nvidia Debian packages to work on Proxmox personally.

Should that blacklisting not be reverted? The related bug is 5 years old and seemingly closed/fixed (https://bugzilla.proxmox.com/show_bug.cgi?id=701).

Our problems disappeared, either from BIOS updates or kernel updates, would be my guess. Are you on latest for both?

Also need to do this on 2 machines, and would prefer to read some success stories first...:oops:

We are also on SuperMicro, specifically a H11SSL-i motherboard. We will test updated BIOS, I think we're one revision behind.

Has anyone found any info that is non-Proxmox? I would think this is a Linux kernel issue, could it be Proxmox-specific? Otherwise I would expect a lot of people with this problem online.