Search results

Thats what i kept reading, but the services we need in the container fail to start with that error.

Long story short, our demo box (LXC is privilaged) is failing to start some services with Failed to reset devices.list: Operation not permitted This has started since we did updates to the hosts, but as it's a demo container it wasn't caught till now. I'm looking for a bit of help with...

Sorry for your loss. Backups, make a backup of the machines and contaners. Then restore them to another host to test that you can restore. Backups are only as good if they work, and you only know they work when you really really need them. Bonus points, restore them to a uptodate proxmox box...

Woot !!!

This post has some more info, but i'm using an old i5 so no numa for me ... https://forum.proxmox.com/threads/best-practice-for-numa.25934/

I'm gonna just randomly say, are you crossing NUMA nodes ? or loading up the second CPU cause of RAM being used on the other cpu, which wouldn't really show extra usage, just the CPU coming out of low power c-state adding to extra heat in the case? Not sure on your case/chassis but i've seen...

I suspect CV19 forced his/her hand a bit, but i would say check out the Level 1 forums. They might not have an answer but a lot of them play/use proxmox and linux on new hardware.

Silly question but have you used iftop when the backup is running to make sure it's using the correct nic and your not using a 1Gbps link some where ? (sorry i did try and read your post but its quite a wall of text)

Have a try of this ! https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster See if normal Debian can see the disks.

This fixed my hyper-v install issues (needed a node for voting on a cluster)

I've found 5.3-2 on the way back machine. https://web.archive.org/web/20190728182645/http://download.proxmox.com/iso/ but it just disappears after july 28th is the last 5.3 download then it becomes 5.4 download.

I've found a 5.3-2 iso on our servers, i can try and stick it up on an FTP server if you want ?

Ohhhh, i was just going by the download name.

Strange i get 5.4-1 https://www.proxmox.com/en/downloads/item/proxmox-ve-5-4-iso-installer

We have containers so use Borg as a backup method.

just googled this, might help. https://superuser.com/questions/701090/determine-pcie-device-numa-node

Just had a quick skim of this, and it looks like it has the info to figure out which cores and where (and some bash scripts and bit to fire up the machine on a set node) Tho the PCIe slots might be quicker to see the motherboards manual, or just fire up the machnie on one NUMA node and the other.

Is the GPU attached to the same PCIe lanes as the CPU socket your running on the Virtual? Your not crossing NUMA nodes are you ? Sorry, looks like your much deeper in to trouble shooting than that, but thought I'd put my 2 cents in.

Was it using NFS v4 ?

i've just checked my config after adding flags for "hv-evmcs" and "aes" and it reads cpu: host,flags=+hv-evmcs;+aes I didn't see an option in the GUI for HV-VACPI