Perhaps you sould take a look in PVE-Zsync.
One doesn't need to have the node in cluster, I guess.
https://pve.proxmox.com/wiki/PVE-zsync
Just an idea.
Thanks for your feedback. FWIW, Ubuntu VMs run fine on our 144-core NVIDIA Grace system, but yeah, that's an ARMv9. We still can improve compat if it's cheap to do, or maybe just some config options needs changing. Can you please open a new...
Just got it loaded up on my Ampere Altra Max 128-core system, and install was a breeze.
Once I had it running, I tried creating an Ubuntu 24.04.1 arm64 server VM, and the process was going through fine... but at a certain point when the Ubuntu...
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only.
Proxmox VE 9.2 for arm64...
Starwind has a nice tools as well...
https://www.starwindsoftware.com/starwind-v2v-converter
I never used, but got friends that did it...
I rather use clonezilla or redorescue as I pointed out... Redorescue always work for me...
But, go ahead...
Please be aware that cache=writeback may lead to data loss in case of a power failure. It also works if you set cache=none and aio=native, but I ran into issues (BTRFS metadata corruptions) within VMs. Currently, I am using cache=none and...
But I used the writeback cache in the Proxmox 8.4 as well I got bugged!
So, still, I can't explain why works on newest version of kernel and PVE.
Anyway... It's works.... That what's matter.
Thanks for your reply @Gilberto Ferreira .
The difference to my setup is your cache setting (writeback) which does not use O_DIRECT semantics and therefore does not trigger the bug.
just to validate this process, I create a 2 node cluster with Proxmox VE 8.4.19 and with the very same storage, created with Debian 13 and TargetCLI.
Now I got that error:
With Proxmox VE 9 and newer kernels, no error so far, at least here for...
So... I went ahead and create a quick and simple target iscsi with Debian and targetcli.
I've created the backstore, target and luns with sinble IP.
After that, I create the device in proxmox with:
iscsiadm -m discovery -t st -p 172.18.100.120...
Try to append this options in the grub:
pcie_aspm=off intel_iommu=off intel_idle.max_cstate=0 acpi_power_meter=off nomodeset
This options has save me for a lot of issue.
pcie_aspm=off
What it does: Disables Active State Power Management for...
I am using the very same kernel version, updated today, 07-06-2026.
Proxmox VE 9.2.4, 2-nodes.
Perhaps I don't have had the issue because the storage underlying is DRBD 9 dual-primary + pacemaker + dlm + ocfs2?
I really don't know!
@Gilberto Ferreira I just tested it with the current Proxmox kernel 7.0.14-3 and the problem still persists on my system.
Which kernel version do you have and what are your VM disk options if I may ask?