Search results

Just to circle back, I clicked through the scary warning and restored the LXC without wiping my bind mounts. Thank you all for your patience!

Ok, so since mp0 and mp7 are bind mounts to directories on the host they will *not* be erased during a restore of this lxc? I'd like to verify I have all the terminology correct so I don't end up having to restore several TB from offsite :)

What does "you will lose it upon restore" mean? Does it mean the restore wipes `/shared/backups` or the restored container will be missing the mount point?

I have an LXC container with the following config running on pve-manager/7.4-15/a5d2a31e (running kernel: 5.15.102-1-pve) arch: amd64 cores: 16 hostname: backups memory: 8192 mp0: /mnt/shared/backups,mp=/shared/backups mp7: /mnt/shared/library,mp=/shared/library net0...

Upgrading to Proxmox 6.2 (5.4.34-1-pve) has fixed this. # dmesg | grep -i edac [ 0.830488] EDAC MC: Ver: 3.0.0 [ 17.087384] EDAC amd64: Node 0: DRAM ECC enabled. [ 17.087549] EDAC amd64: F17h_M70h detected (node 0). [ 17.087617] EDAC MC: UMC0 chip selects: [ 17.087618] EDAC amd64...

So I did a bit more digging and apparently it just doesn't like my Valve Index. Not sure why. I ended up passing through one of the onboard controllers to the VM and am able to use the StarTech card for USB devices used by the host.

Running: 5.3.18-2-pve #1 SMP PVE 5.3.18-2 on an AMD Ryzen 9 3900X I picked up a PEXUS313AC2V card to to pass through to a Windows guest that I need to attach a bunch of USB devices to. Passthrough sort of worked, windows saw both controllers on the card but with the default windows driver the...

I haven't had time for more testing yet, the next step would be finding a linux distro that should support ECC on Ryzen and boot from that. I'll see if I can give it a go this weekend.

Thanks for the update. I'll give the latest debian live usb a try and report back.

I think my original post has been hijacked a bit. cromantn5's issue appears to be Intel specific and unrelated to EDAC on Ryzen/x570.

Hrm EDAC works for me on another server: $ pveversion pve-manager/6.1-5/9bf06119 (running kernel: 5.3.13-1-pve) $ edac-util -v mc0: 0 Uncorrected Errors with no DIMM info mc0: 0 Corrected Errors with no DIMM info mc1: 0 Uncorrected Errors with no DIMM info mc1: 0 Corrected Errors with no DIMM...

I was trying to monitor for ECC errors and when I ran edac-util I got # edac-util -v edac-util: Error: No memory controller data found. Then looking at dmesg I see: # dmesg | grep EDAC [ 0.795765] EDAC MC: Ver: 3.0.0 [ 16.382549] EDAC amd64: Node 0: DRAM ECC enabled. [ 16.382553]...

According to https://www.reddit.com/r/ASUS/comments/cw74rl/asus_pro_ws_x570ace_ecc_compability/ ECC support has been added in the 5.4 kernel. Would it be possible to backport the set of EDAC related patches called out in that post into the 5.3 kernel used in pve 6.1?

After search around on the forums it appears I just needed to reboot the host and things are happy again.

I setup a few LXC containers with idmaps to and now I don't get any running/stopped/summary data in the webgui. The changes I made were: * Add shared users to /etc/passwd: nas-backups:x:5002:5002::/home/nas-backups:/usr/sbin/nologin nas-plex:x:5005:5005::/home/nas-plex:/usr/sbin/nologin...

I only ever did the suspend the one time. I usually just shutdown from inside the guest and for whatever reason that vmstate doesn't go away. The qm set command worked to clear the state and the VM starts cleanly from shutdown. Thanks for the quick fix!

I updated to the 1104 BIOS (AM4 combo PI 1.0.0.4 patch B) that reset my BIOS and I went and re-enabled SR-IOV, IOMMU Support, and ACS. Now I can boot into my Windows VM cleanly after a host boot. The guest also cleanly reboots.

I have a Win10 VM on proxmox-ve: 6.0-2 where it always starts in suspended state so I have to click resume as well. I did a "qm config" dump and I'm guessing the vmstate line is the culprit but I'm not sure how to get rid of it: # qm config 100 agent: 1,fstrim_cloned_disks=1 balloon: 2048...

Sorry, I need a little more detailed instruction on how to apply that patch before I can give it a try.

Found a fix! I compiled and install this driver: https://github.com/mtorromeo/r8168 Network card works now :)