StarWind V2V Converter - Linux to Proxmox

VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator
billyg1943
Posts: 9
Joined: Sun Feb 08, 2026 1:31 am

Sun Feb 08, 2026 2:26 am

Trying to do a conversion of Alpine Linux Docker vhdx VM to Proxmox qcow2 VM.

Running MS Server 2022 Standard Hyper-V host. Running StarWind V2V there. Proxmox VE 9.1.5. Always fails as follows.

2/7 11:54:19.453 22b4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: CreateVM attempt 1/10
2/7 11:54:19.453 22b4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Set disks
2/7 11:54:19.453 22b4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: disk name scsi0, local:6144.000000,format=qcow2
2/7 11:54:19.453 22b4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace: disk name disk size = 6144.000000 Gb
2/7 11:54:19.453 22b4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace::<lambda_ff13655038bc08377f040195fc2d064a>::operator (): l
2/7 11:54:19.453 22b4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::isEnoughSpace: storage is found
2/7 11:54:19.453 22b4 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Not enough space
2/7 11:54:19.705 238c Facility ???INFO: WrapperHyperV::destroy_snapshot: DestroySnapshot returnValue.iVal = 4096
2/7 11:54:20.738 238c Facility ???INFO: WrapperHyperV::waitJob: JobState 7
2/7 11:54:20.738 238c Facility ???ERROR: CPPConverting::Convert: FAILED

There is no shortage of disk space on the Proxmox VE host
yaroslav (staff)
Staff
Posts: 4309
Joined: Mon Nov 18, 2019 11:11 am

Sun Feb 08, 2026 2:42 am

Please make sure there's enough space.
Share the screenshot that shows the VM disk space and the destination disk space.
Knowing the destination disk type will also be helpful.
billyg1943
Posts: 9
Joined: Sun Feb 08, 2026 1:31 am

Sun Feb 08, 2026 4:23 am

Thanks for your speedy reply.

Unclear how I send screenshot.
yaroslav (staff)
Staff
Posts: 4309
Joined: Mon Nov 18, 2019 11:11 am

Sun Feb 08, 2026 3:43 pm

You can attach it in attachments.
billyg1943
Posts: 9
Joined: Sun Feb 08, 2026 1:31 am

Sun Feb 08, 2026 11:35 pm

Please see attached screenshot. Lots of disk space both one source and destination computers. I am trying to convert vhdx VM on Windows 2022 Server to qcow2 VM on Proxmox VE server.
billyg1943
Posts: 9
Joined: Sun Feb 08, 2026 1:31 am

Mon Feb 09, 2026 12:01 am

I don't think you got the screenshot. When I tried to attach the PNG screenshot I got an HTTP error. I will try again.
yaroslav (staff)
Staff
Posts: 4309
Joined: Mon Nov 18, 2019 11:11 am

Mon Feb 09, 2026 4:05 am

Try attaching the screenshots with the archive
billyg1943
Posts: 9
Joined: Sun Feb 08, 2026 1:31 am

Mon Feb 09, 2026 5:41 am

"Attach with the archive"? Where? How? I think I may be too stupid to use your web page. Thank you for trying to help me, though. :?
yaroslav (staff)
Staff
Posts: 4309
Joined: Mon Nov 18, 2019 11:11 am

Mon Feb 09, 2026 8:11 am

When posting, there is an option called "Attachments" > Add files.
See the test zip file below. Also, you can use third-party services like https://imgur.com/.
I need to see
1. Disk size
2. Available capacity at the destination storage
3. Storage type for destination.
Attachments
zip test.zip
(22 Bytes) Downloaded 181 times
billyg1943
Posts: 9
Joined: Sun Feb 08, 2026 1:31 am

Mon Feb 09, 2026 11:49 am

I have tried this multiple times as well as dragging the screenshot PNG and/or ZIP into the body of the message. Always get "Error HTTP error" pop-up. I can see the files in the Attachments window, though.
billyg1943
Posts: 9
Joined: Sun Feb 08, 2026 1:31 am

Mon Feb 09, 2026 12:01 pm

Here is screenshot.

https://imgur.com/a/8hmzCxL

Cheers,
Bill
yaroslav (staff)
Staff
Posts: 4309
Joined: Mon Nov 18, 2019 11:11 am

Mon Feb 09, 2026 1:30 pm

Thanks for your update. Please try converting that VHDX as a local file and copy to Proxmox afterward.
billyg1943
Posts: 9
Joined: Sun Feb 08, 2026 1:31 am

Mon Feb 09, 2026 11:47 pm

Thanks for your reply.

Don't seem to be able to create a Proxmox VM locally.

https://imgur.com/a/NTSPr12

Steps:
1. Select the location... Microsoft Hyper-V Server, Next.
2. Enter localhost (use Windows authentication), Next.
3. Select a virtual machine or image file to convert (the VHDX VM), Next.
4. The only options presented on next step are Local file and Microsoft Hyper-V Server

If I select Local file, destination image is VHD/VHDX, which is not what I want, of course.
yaroslav (staff)
Staff
Posts: 4309
Joined: Mon Nov 18, 2019 11:11 am

Tue Feb 10, 2026 10:37 am

Try the disk(s) alone. Convert the disk alone and copy it to the destination. Create the VM there.
billyg1943
Posts: 9
Joined: Sun Feb 08, 2026 1:31 am

Tue Feb 10, 2026 11:52 pm

I guess I may not have been clear.

1. I always shut down the Hyper-V VM
2. I always select the disk (.vhdx) as the disk I want to convert.

Nevertheless when I try to convert locally, I am not able to select any "conversion" format other than Hyper-V VHDX for the destination. All other conversion options are greyed out and not selectable. My previous screenshots show this.

Time to cut my losses and try something else?
Post Reply