.
As mentioned in the Serial Terminal wiki [0], you can configure a VM's serial console to listen on a local TCP port instead of the default socket:
By doing this, the Proxmox VE host exposes the VM's serial console through a raw TCP socket...
Following links are propably of interest:
Smoother migration for WindowsVMs: https://forum.proxmox.com/threads/a-small-game-changer-for-windows-migration-to-proxmox.181582/ This is especially useful for migrations with minimal downtime as...
I will answer here since this is the original thread. Please avoid creating duplicate threads for the same topic.
Q1
The described configuration looks good and should be fine for production.
If you haven't already,ensure to check the wiki...
I haven't tested this specifically, therefore this Just my 2 cent:
In case not already done, make sure to read thoroughly the wiki Migrate to Proxmox VE:
https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE
Test the migration process first with a...
I think this is a different concern.
The CPU usage reported in Proxmox between 8% to 11% when idle while taskmanager in the VM reports below 1% might be expected in certain cases, I found related thread below [0]...
Do you also only observe this with Windows Server 2025 ?
Please share vm config:
qm config [VMID]
The known issue is mentioned for Intel:
https://pve.proxmox.com/wiki/Roadmap#9.2-known-issues...
Where is this mentioned? could you please add link to wiki or pve doc mentioning this?
I have tested with local lvm for linux vm it work with no error (I will check win vms as well and share result whenever I got time):
root@node3:~# grep...
Okay, I will test this and update you hopefully tomorrow.
If possible please also share journalctl log from the source pve covering the migration time, for example:
root@pve :# journalctl --since "2026-08-xx xx:00:00" --until "2026-08-yy...
Hmm so the problem only occurs whenever you use qcow2, Interesting finding.
I am not aware of such problems when using snapshot-as-volume chain. I will try to reproduce and share my result.
Hmm I think this config should work as explained in thread [0].
Could you also share the output for vgs from both nodes.
0] https://forum.proxmox.com/threads/cant-seem-to-move-disks-between-local-lvm-storage.128770/post-563425
I am not entirely sure if i understand your question, do you mean to show how many cpu on the host pve server, and the remaining cpu to assign? Similar to how you see storage now?
The thing is, with the Virtualization you can overcommit CPU, and...
Did you test this and got the error above?
I assume since the migration network on a different network it should work, assuming you still have corosync quorum on the other nodes.
Always welcome. I will keep an eye on the thread.
In case it reoccur share journalctl again covering issue time:
root@pve2 :# journalctl --since "2026-07-xx xx:00" --until "2026-07-yy yy:yy" > /tmp/syslog.txt.gz