Hello,
We are experiencing intermittent issues with live migrations hanging at the very end on Proxmox VE 9.1.2.
The migration starts correctly, runs for a while, but sometimes never finishes, remaining stuck indefinitely.
This happens only at...
I did edit both files. on the /etc/hosts file i made a change from
x.x.x.x pve.home.arpa pve to x.x.x.x nocpve.home.arpa nocpve
and on the /etc/hostname file I made the change from pve to nocpve.
restarted the box and got the screen shot...
I have an Alder Lake CPU and using the CPU host. If I enable WSL2 or Hyper-V, Windows gets stuck on boot, just like what you experienced. To get it to boot, I have to temporarily switch to Skylake-Client-v4.
Hello,
Have anyone face a strange behavior of VM Window after Backup to PBS: lagging ? I even have to force stop VM.
To avoid error 8194, I have config in Window following to the doc VM Backup Consistency - Proxmox VE : VSS set to 5, dcomcnfg...
It's quite normal for an IPv6 gateway to use a link-local address.
Does it make a difference which container you use? What distribution is it? Are you using SLAAC or static IPv6?
Stefan,
I've updated with the latest patch, here's the latest output when migrating a VM:
2025-12-16 11:13:46 use dedicated network address for sending migration traffic (10.XX.XX.XX)
2025-12-16 11:13:46 starting migration of VM 273 to node...
Stefan,
I've updated with the latest patch, here's the latest output when migrating a VM:
2025-12-16 11:13:46 use dedicated network address for sending migration traffic (10.XX.XX.XX)
2025-12-16 11:13:46 starting migration of VM 273 to node...
Thank you, @ucholak, for sharing your experience and expertise -- I really appreciated it.
You gave me a glimpse of hope, but unfortunately it faded rather quickly :)
I reformatted my NVMe drives to 4K using:
nvme format /dev/nvme2n1...
Hi,
I'm busy harding a Proxmox Host and going through the settings I see "Protection" and in the help documents it states (and I've not been able to find anything on this subject. Is this purely so users cannot delete the VM until they turn this...
This thing is not intuitive or documented (and I also looked for it arriving here), I think it is useful to add a "help" link to the documentation that specifies it as there is for other fields but not for this one.
Stefan,
I applied the patch info to the IPRoute2.pm file and was able to successfully migrate a VM as a test. I did see the following in the output during the migration:
2025-12-16 10:37:37 use dedicated network address for sending migration...
Yes, I have been through that thread, and unfortunately, nothing helped.
But today, to test, I created a new VM with CPU set to host, installed a new version of Windows on the VM disk, and it works fine. So the problem is really interesting :)
I'm doing my testing in the off-hours anyway, 6.17.11-3-test-pve is up and running and we'll have a result in the morning.
For all others: if the stalled backup crashes your VMs, please look into enabling fleecing for the scheduled backups...