Search results

Yes Proxmox makes sure that you can always migrate to a newer node (but not back from the new node to an older one). Livemigration is no problem, have fun!

Moin! Auf der Proxmox Linkedin Seite wurde das Event beworben. XING ist tot, Linkedin ist sehr aktiv (finde ich zumindest). Im Forum würde ich mich auch freuen. Eventuell gibts hierfür eine Möglichkeit im deutschen Bereich? Wir melden uns bei Daniela (@ aaron) Ansonsten ja es sind einige...

"Drop the VM.Monitor privilege and instead require the Sys.Audit privilege for basic access to the KVM monitor.Commands besides basic informational commands require the Sys.Modify privilege, and some commands are restricted to the root user." https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_9.0...

Thanks! A side-question to that topic. If a user puts an ip for the web-ui/mgmt on the vmbr0 (access-vlan, no tagged-vlan-adapters) - is this still a bad idea in 2025? Any downside, because vms can identify the hypervisor or is this information outdated nowdays? Cant find the reasons for it...

Has someone actually tcpdumped and checked or knows: what happens if a vm with a tagged vm-hw-adapter gets its vlan tag overwritten when user sets them inside the vm? will the vmbridge-adapter drop the "wrong" vlan-tag because it does not match?

This used to work in pve 8, any way to troubleshoot this? Ceph isnt even installed on that machine, normaly the wizard "Do you want to install ceph" pops up. This error does only appear on the ceph dashboard, I havent found any other issue yet (VNC Working, Login Working, Even Ceph Submenus like...

Thanks! Will the pool be auto-encrypted on boot or is it possible to encrypt it manually?

Thanks! What about migration, should also be not possible right? when moving a vm from a encrypted pool to a different node with another encrypted pool?

Hello Fireon! Is this still valild in 2025? "Also an migration or replication from the Proxmoxwebinterface is not available anymore, because encrypted datasets/VM's are not supported via the webinterface yet." Does this only apply to the boot-pool or any zfs pool you want to encrypt?

The "real" name does not exist anymore. pvea bis pveq are sdn-simple-zones just in case your wondering about these. root@training4:~# udevadm test-builtin net_id /sys/class/net/ /sys/class/net/bond0 /sys/class/net/nic3 /sys/class/net/pvee /sys/class/net/pvej /sys/class/net/pveo...

Hi Stefan! I also tried this on my Minisforum MS-A2 Machines and this happened: root@training5:~# proxmox-network-interface-pinning generate This will generate name pinning configuration for all interfaces - continue (y/N)? y Name for link 'enp3s0' will change to 'nic0' Name for link 'enp4s0'...

Usually the most important feature to look for is the PLP (Power Loss Protection) so ssd-cache does not get lost on power-failure. This ssd according to google has power loss protection. I personally dont have experience with Kingston SSDs.

I know, but you would have more performance on frr setup which is also full meshed without switch

I upgraded all 3 nodes one after another without using sdn in between.

Are you sure the gateways correct?

Thanks we changed nic1 to fit the mac, rebootet and also changed frr. This is how my /etc/frr/daemons file looks like, should all the lines with "yes" be switched to "no" and then systemctl restart frr? root@PMX7:~# cat /etc/frr/daemons # This file tells the frr package which daemons to start...

root@PMX8:~# cat /usr/local/lib/systemd/network/50-pve-nic0.link [Match] MACAddress=14:23:f2:e6:86:f0 Type=ether [Link] Name=nic0 root@PMX8:~# cat /usr/local/lib/systemd/network/50-pve-nic1.link [Match] MACAddress=14:23:f2:e6:86:f0 Type=ether [Link] Name=nic1 root@PMX8:~# cat...

1. We do not have ip-communication on all vms and ct since upgrading to pve9 (cant reach 10.26.0.1) -- untouched pve8.4.5 clusters work well on the same subnet including their vms/ct 2. the same lan works well on the pve-hosts itself (they can reach the gw 10.26.0.1) 2. I did use the...

Possible issue: after using nic-naming-tool no ip-communication inside vms and ct via vmbr0 since upgrade to pve9 (test-cluster) I did made a new post, because it seems to be a lot to post here: https://forum.proxmox.com/threads/pve-9-beta-different-network-errors-since-upgrade.168729/ Edit...

proxmox does generate a whitelist, you can check it via "pve-firewall localnet". Host on that Subnet are automatically allowed for 22/8006 and some other ports aswell.