Search results

We/i dont have anymore any x520 cards, however if you want transceiver recommendations, it's hard, because almost everything worked here great. For the most part, we use flashable transceivers from Flexoptix. Those are amazing, because you can reflash them to any brand you need. If it has to be...

if you added your new values to /etc/modprobe.d/zfs.conf (or any other file in modprobe.d) you need to update initramfs and update-grub or proxmox-boot-tool refresh (or simply both) then reboot. One of those you have clearly missed :-)

Everyone should simply use "host" as CPU. The only exception is, if you run a Cluster and all nodes in the Cluster doesn't have the identical CPU Generation. Funny thing is, i have only a single VM in one of my Clusters, that is not working with host as CPU and freezes during migration. On all...

There is no fix. Disabling Wallpapers, changing group policys etc, nothing will help. Its simply a bug, i have the same issue on all Windows 11 Instances (Physical and VM's) where you have more as one Account on the PC/VM. There is no fix. And everyone has the same issue! BTW, This happens...

Yeah it does only in one case, if you migrate multiple VM's/Containers at the same time. But in real life thats almost never the case (at least i never use that), i usually migrate only one vm. If you Shutdown one Server from a Cluster that is in HA, it does migrate only one VM at once either...

Lacp for redundancy, but not for Performance. The only cool thing that you can do is disabling encryption for the Cluster/Migration Network. That makes migration at least twice as fast, but i would do it only if you make a separate closed vlan on the switches. (So that its still safe) I have a...

It's funny, im using pvetest since forever and never had any issues or bugs. Using qemu 9.2 since a week, - changed all Windows-VM's to 9.2 / Linux-VM's are anyway automatically on 9.2 - Have some VM's with passthrough, for NICS's and GPU And everything runs absolutely Perfect on all 11...

I have the same issue on all 7 Proxmox Servers, but only with W11 VM's (i think since the 24h2 update). On all W7/W10/Server 2016/2019/2022, there aren't any issues and everything is Perfect.

Can you try to Pin all your VM-Cores to the same Socket on your host? numactl --hardware So that all Cores of VM1 runs on Socket1, VM2 on Socket2 and so on? Dont forget to shutdown/start the VM or LXC Container after you changed the config. Just for testing, to rule that out.

Do you use primarycache=metadata or something else on zfs?

Sure i readed that and tryed almost anything on that AMD sheet. About intel, im curious either, but as far i seen the new intel chiplet design is using some sort of a silicon base for the interconnect, which is very expensive but very fast. So i have the fear that it wouldn't be an issue on...

numastat hit/misses doesnt tell the whole story sadly, we had this already. I believe that the host-kernel (numastat) cannot track anything inside a VM behind the guest kernel, but thats only an assumption so far. i knew i would start this stupid discussion again after my initial reply, but...

This would be true if the Kernel would know that vCPUs (Tasks) of a VM are belonging together. But in our case the Kernel is not aware and the vCPU tasks of a single VM starting randomly spreaded across Numa-Nodes. For example if you configure the VM with 4 vCPUs, those Tasks on the Host wont...

If you want to use Proxmox, try to avoid Numa or/and Multisocket Systems. Otherwise use ESXI or anything that supports Numa. Proxmox Numa Support is just helpfull in very rare cases, most of the time its just senseless. The Only way to get it Properly working is with CPU-Pinning (or scripts...

Sure. First you need to create a dataset on your PVE Host and mount it somewhere. Here is an example: root@proxmox:~# zfs list NAME USED AVAIL REFER MOUNTPOINT HDD_Z2 21.5T 82.2T 114K /HDD_Z2 HDD_Z2/PVE_Backup 696G 82.2T 696G /PVE_Backup...

Ja deswegen wollte ich auch eigentlich nicht Antworten und geschrieben dass ihr machen sollt was ihr wollt. Hab ja auch keine Lust auf endlose Diskussionen. Am ende ists eh egal. Wenns funkt ist super (viel Arbeit gespart) und wenn nicht kann mann halts fixen. Ist ja Linux und mann hat auch...

LXC-Container sind Managed. Ein Upgrade der Distribution könnte Änderungen an systemd, init oder anderen Kernkomponenten führen, die mit der Art wie der Container verwaltet wird, in Konflikt stehen. Hier ein teil aus ChatGPT was Managed Container bedeutet (Mann kann die auch natürlich auf...

Macht wie ihrs denkt, mir ist das egal. Ich hab alles dazu bereits geschrieben.

Neueres Image laden und dann halt alles auf den neuen Container migrieren, und ja ist natürlich umständlich... Der grund ist halt, das sich in nem LXC Container oft mehr ändert als nur die Packete, Packete werden auch grundsätzlich nie entfernt, nur upgedated/hinzugefügt. (Entfernt auch aber...

Ja mit einem upgrade auf 24.04... Würde ich beim LXC Container aber eher nicht empfehlen Distro upzugraden auch wenns funktioniert. Bei ner VM ist das natürlich kein Problem. Vielleicht helfen die Sources ja trotzdem jemandem, damit er nichtlange googeln muss halt. LG