Recent content by alatteri

  1. A

    set_eugid: setegid(1057400001) - Set SUID/SGID-Range for LXC-Container

    I modify /etc/subuid to be root:100000:10000065536
  2. A

    Safe to enable dnodesize=auto on rpool/data?

    root@vmhost:~# proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with uefi C606-33DC is configured with: uefi (versions: 5.13.19-6-pve, 5.15.107-2-pve, 5.15.108-1-pve) C606-9E7D is configured with: uefi (versions...
  3. A

    Safe to enable dnodesize=auto on rpool/data?

    Hello, Is it save to enable dnodesize=auto on rpool/data? While leave rpool and rpool/ROOT set to legacy? I know there is a GRUB problem with auto, but in theory, changing only rpool/data should not be a problem, right?
  4. A

    NFS mount with LXC fails in PVE 7.X

    Hello, Prior to PVE 7.X I used the modified lxc profile (see below) to allow LXC containers to be able to mount and serve NFS. Now this refuses to work (Permission Denied). Any thoughts on this? /etc/apparmor.d/lxc/lxc-default-with-nfsd # Do not load this file. Rather, load...
  5. A

    CT network manager not passing all info in to CentOS8 guest /etc/resolv.conf

    I am seeing this issue also with LXC CentOS8. No nameserver entry is being created in /etc/resolv.conf. This only started with recent updates.
  6. A

    e1000 driver hang

    00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-V [8086:1570] (rev 21) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (4) I219-V [8086:15d8] (rev 21) from several different generations of Intel NUCs
  7. A

    e1000 driver hang

    Dec 11 13:13:00 vmhost03 systemd[1]: Starting Proxmox VE replication runner... Dec 11 13:13:01 vmhost03 systemd[1]: pvesr.service: Succeeded. Dec 11 13:13:01 vmhost03 systemd[1]: Started Proxmox VE replication runner. Dec 11 13:13:35 vmhost03 corosync[1132]: [KNET ] link: host: 1 link: 0 is...
  8. A

    Linux Kernel 5.3 for Proxmox VE

    e1000 hang is not fixed.
  9. A

    e1000 driver hang

    still happens even after upgrade to pve 6.1
  10. A

    Primary cluster NIC stopped communicating

    look at your syslog. probably the e1000 hang.
  11. A

    e1000 driver hang

    Nope, definitely still happening even with 5.3.10

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!