VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
ipod86
- Posts: 13
- Joined: Fri Jul 05, 2024 6:54 am
Sun Apr 13, 2025 6:14 am
Hi all,
I'm trying to migrate a local physical Windows machine to Proxmox using StarWind V2V Converter. The physical disk is 500 GB in size, but only about 80 GB is actually used.
The destination Proxmox node has only 300 GB free space, so in theory, this should be enough – especially since I selected the QCOW2 format during conversion.
However, the conversion keeps failing with an error in the log saying there's not enough space available.
It seems like StarWind is trying to allocate the full 500 GB size of the source disk, rather than just the used space. Is there any way to force StarWind to only convert the used portion of the disk, or to manually define the size of the target virtual disk?
Any help or workaround would be appreciated!
Thanks in advance.
-
yaroslav (staff)
- Staff
- Posts: 3424
- Joined: Mon Nov 18, 2019 11:11 am
Sun Apr 13, 2025 6:34 am
you are about to overprovision that VM. That's not a recommended way to go. I will try to discuss with my colleagues if there is anything we can do about it.
-
ipod86
- Posts: 13
- Joined: Fri Jul 05, 2024 6:54 am
Sun Apr 13, 2025 7:07 am
Thank you very much. I would migrate the VM, then shrink the hard drive in Windows and then in Proxmox. I would be very reluctant to shrink the hard drive on the PC I'm converting.
-
yaroslav (staff)
- Staff
- Posts: 3424
- Joined: Mon Nov 18, 2019 11:11 am
Sun Apr 13, 2025 7:58 am
Yes, it is always better to have the source disk of the right size. But be really careful with shrinking (i.e., keep a copy of the original disk)
-
ipod86
- Posts: 13
- Joined: Fri Jul 05, 2024 6:54 am
Sun Apr 13, 2025 8:08 am
I won't shrink the original disk. I don't want to destroy the system. It has quite complex software installed, and the provider no longer exists to configure the installed software. Therefore, I want to virtualize the PC, as it's much easier to secure that way.
-
ipod86
- Posts: 13
- Joined: Fri Jul 05, 2024 6:54 am
Sun Apr 13, 2025 9:58 am
I've been trying that the whole time. Unfortunately, I can't copy the log as text. I can only access the computer via RDP from my phone.
EDIT
Code: Select all
4/13 11:45:42.017 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetStorageContent: Get storage info lists
4/13 11:45:42.061 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetDiskPath: Get storage info lists
4/13 11:45:42.083 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetDiskPath: Get storage info lists
4/13 11:45:42.125 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetDiskPath: Get storage info lists
4/13 11:45:42.168 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetDiskPath: Get storage info lists
4/13 11:45:42.210 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetDiskPath: Get storage info lists
4/13 11:45:42.253 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetStorageContent: Get storage info lists
4/13 11:45:42.295 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetStorageContent: Get storage info lists
4/13 11:45:42.339 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetDiskInfo: Get disk information
4/13 11:45:42.381 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetDiskInfo: Get disk information
4/13 11:45:42.389 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::GetDiskInfo: Get disk information
4/13 11:45:42.398 2808 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::Connect: Successfully connected to proxmox host
4/13 11:48:24.900 1940 Facility ???INFO: ICPPage::OnWizardNext: eVolumeSelectVM
4/13 11:48:24.908 1940 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage – eESXConnectionTo
4/13 11:48:24.913 3c8 Facility ???INFO: CPPConverting::Convert: In ConvertType: 3, outConvertType: 15
4/13 11:48:24.913 3c8 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: CreateVM
4/13 11:48:24.913 3c8 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Set disks
4/13 11:48:24.913 3c8 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: disk name ide0, Pool2:477.000000, format=raw
4/13 11:48:24.913 3c8 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Not enough space
4/13 11:48:24.913 3840 Facility ???WARNING: CPPConverting::Convert: CANCEL
-
Attachments
-

- Screenshot_20250413_114145_Microsoft Remote Desktop.jpg (139.85 KiB) Viewed 3547 times
-

- Screenshot_20250413_114843_Microsoft Remote Desktop.jpg (91.07 KiB) Viewed 3550 times
-

- Screenshot_20250413_114746_Microsoft Remote Desktop.jpg (135.31 KiB) Viewed 3550 times
-
yaroslav (staff)
- Staff
- Posts: 3424
- Joined: Mon Nov 18, 2019 11:11 am
Sun Apr 13, 2025 10:39 am
I will discuss your incident internally. I will keep you posted. Thanks for additional details. As a workaround for now, use disk2vhd > convert a local file to Proxmox.
-
ipod86
- Posts: 13
- Joined: Fri Jul 05, 2024 6:54 am
Tue Apr 15, 2025 10:07 am
I just tested something else. It's not just the partition. I just successfully moved the computer to an ESXi. There's plenty of space there. I shrunk the volume in Windows to 100GB. So, 400GB of the hard drive is unallocated. Now I've tried migrating to Proxmox using P2V. I still get the same error. It's as if it's somehow taking the unallocated space into account.