Are you really checking the blocksize or just the logical size?
After you trim, please compare the following:
ls -l image.qcow2
ls -ls image.qcow2
stat image.qcow2
Could you post these information after you fstrimmed but before you moved the VM?
BD:24 ist auch keine valide Unicast MAC, wie es die Fehlermeldung vorgibt. Proxmox sieht nicht vor, dass das I/G Bit gesetzt ist.
Siehe: https://pve.proxmox.com/pipermail/pve-devel/2019-March/035998.html
Das hat nichts mit der Proxmox OUI zu tun...
If the VM stays the same, moving the VM between nodes does not affect any licensing agreement. As long as the PC (virtual or dedicated) stays the same, the underlaying hardware or hypervisor does not matter.
Does it work when you stop your PVE-Firewall ( systemctl stop pve-firewall ) ? Usually outgoing connections are always allowed, even with the firewall enabled (and E/R incoming connections aswell).
This function already exists. You can edit the notes template for each backed up VM/Container at your will. Then, within the name, you have a NOTES section where you have exactly what you are looking for.
Würde ich nicht machen. Wenn es Dir wirklich um eine gemeinsame GUI & Administrations-Oberfläche geht, installiere Proxmox Datacenter Manager und verwalte die Knoten darüber.
Einen 2-Node-Cluster für einen "Kunden" bauen geht garnicht. 3 Knoten...
Which CPU type did you chose for your VM? Did you set it host by any chance?
Are the two nodes 100% CPU identical?
If not, please change the CPU type of the VM to AES-v2 and try again.
Please edit your /etc/hosts entry to
192.168.86.211 ctoffsite.local ctoffsite
Okay so the routing on the Proxmox box is fine now. If you restart pveproxy via systemctl restart pveproxy everything should work. Always make sure your /etc/hosts...
Could you please provde ip r
I assume your /etc/network/interfaces looks like that now, correct?
auto lo
iface lo inet loopback
iface nic0 inet manual
auto vmbr0
iface vmbr0 inet dhcp
bridge-ports nic0
bridge-stp off...