Search results

  1. S

    Proxmox VE5 on ProLiant G5 Server CPU#0 stuck for 23s

    I just hit this after upgrading to Proxmox VE5 on a DL380 G4 server. The issue is not specific to Proxmox - I found mentions of similar issues on forums with kernel 4.9 as well as 4.10 with these generations of DL380 (in fact if I try boot the Debian Stretch installer on the same hardware it...
  2. S

    lxc containers have extended permissions - acl by default???

    Hi Dietmar - I've logged it there (bug 928) linking back to this thread. To sort the issue I suspect you'd have do your own tar package on PVE with either 1.27.1 patched with just that bug fix or backporting 1.28 from Stretch!
  3. S

    lxc containers have extended permissions - acl by default???

    I had an issue with mailman in a Debian Jessie container under PVE 4.1 due to those default posixacls (mailman uses umask rather the specifically setting permissions to set group write on files). When digging into the cause of the issue I could see that posixacls are enabled on the root file...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!