VSAN Free on Proxmox

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
User avatar
ticktok
Posts: 25
Joined: Sat Mar 24, 2012 2:12 am

Mon Jun 30, 2025 4:32 am

I have successfully created a shared LVM volume on a Proxmox cluster of 2 nodes with a third server as a witness via QDevice.
The performance is about the same as my original Windows based 2 node cluster.
The issue I have is thin provisioning of the VM disks, with the Windows versions disk were thin provisioned. I used the Starwind Converted to convert the .vhdx to .qcow2 disks.
After I transferred these disks to a Proxmox host and then imported them:-
qm importdisk 104 /root/vm-tfs.qcow2 vg-vms
where vg-vms is the shared Starwind storage the images were then thickly provisioned.
Am I doing something wrong?
yaroslav (staff)
Staff
Posts: 3605
Joined: Mon Nov 18, 2019 11:11 am

Mon Jun 30, 2025 5:21 am

For CVM, you need to install and set up the VSAN plugin in Proxmox (recreating the LVM will be needed) https://www.starwindsoftware.com/resour ... ion-guide/
User avatar
ticktok
Posts: 25
Joined: Sat Mar 24, 2012 2:12 am

Mon Jun 30, 2025 6:11 am

Thanks for the update, when you say you'll need to recreate the LVM - I presume this is destructive and all the VM disks will need to be exported and then imported later?
Or is it auto-magical and the VM disks can stay there?
yaroslav (staff)
Staff
Posts: 3605
Joined: Mon Nov 18, 2019 11:11 am

Mon Jun 30, 2025 7:03 am

Sadly, it is a destructive procedure.
UPD: QCOW cannot be created.
User avatar
ticktok
Posts: 25
Joined: Sat Mar 24, 2012 2:12 am

Mon Jun 30, 2025 9:42 am

Hi,
Thanks for the information after issuing the last command:-
pvesm add starlvm swlun -vgname vgt-vms -content images,rootdir -shared 1
the message I received was:-
Plugin "PVE::Storage::Custom::StarLvmPlugin" is implementing an older storage API, an upgrade is recommended

is this something to worry about??

I discovered I can't just migrate the disks from the old LVM to the new one, I suppose its convert to each disk to .qcow2 and then upload to the swlun??
yaroslav (staff)
Staff
Posts: 3605
Joined: Mon Nov 18, 2019 11:11 am

Mon Jun 30, 2025 10:12 am

Plugin "PVE::Storage::Custom::StarLvmPlugin" is implementing an older storage API, an upgrade is recommended
No, it is not a problem.
I discovered I can't just migrate the disks from the old LVM to the new one, I suppose its convert to each disk to .qcow2 and then upload to the swlun??
Yes, you can convert each disk to qcow2 from non-swlun device to a swlun one (try backing up and restoring the VM too).
User avatar
ticktok
Posts: 25
Joined: Sat Mar 24, 2012 2:12 am

Tue Jul 01, 2025 12:51 am

Hi,
After creating a new lun using the starlvm call vg-thin whenever I import a disk like:-
root@pve-rose:~# qm importdisk 107 /var/lib/vz/template/qcow/ubuntu-2404.qcow2 vg-thin --format qcow2
Plugin "PVE::Storage::Custom::StarLvmPlugin" is implementing an older storage API, an upgrade is recommended
importing disk '/var/lib/vz/template/qcow/ubuntu-2404.qcow2' to VM 107 ...
format 'qcow2' is not supported by the target storage - using 'raw' instead

It converts it to raw and is then not thin provisioned??
local-lvm disk useage
Image
disks on local-lvm
Image
vg-thin useage
Image
disks on vg-thin
Image
Post Reply