Search results

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...

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.

I think he is asking about the bare metal file based backups.

CentOS 8 LXC has this issue too.

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

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...

e1000 hang is not fixed.

still happens even after upgrade to pve 6.1

correct

look at your syslog. probably the e1000 hang.

Nope, definitely still happening even with 5.3.10

5.3.10-1-pve although I haven't had the issue in several day, there is a chance what I see in the log happened before I rebooted with the new kernel.

I'm still getting the e1000 hangs with kernel 5.3

I'm still getting the e1000 hangs with Kernel 5.3.

We've been seeing all sorts of strange network port related errors the past 2 weeks.

I have the same problem. Only started with he latest Proxmox updates. Same hardwares has been running fine previous for years, without issue. There must be a bug in the latest kernel.

In the past week we are seeing random e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang failuresacross all our nodes, even different hardware hosts. Must do a reset of the host. There are lots of references to this issue going back 5+ years. Was there a driver change with the latest...

Would it still be necessary to set MTU 9000 in the guest also, if you set it in the host bridge?

Latest installer fixes this.

Hello, I am installing a fresh 5.0 on Intel NUC7I5BNK with a Samsung 960 EVO Series - 500GB NVMe - M.2 Internal SSD (MZ-V6E500BW). Once it gets to the creating partitions stage, it just sits at 0% forever. Any thoughts?