StarWind Software

Hello,

I would like to migrate my physical computer to proxmox.
I go through all the settings (P2V, Entire Machine, all Volumes, Proxmox, login details, VM settings).
When I then want to restart the process, the V2V Converter closes completely.
I tested it with and without qcow2.

What could be the reason?
Windows 10
Proxmox 8.2.4.
V2V Converter 9.0.1.509

Hi,

Welcome to Starwind Forum!
We will test it internally.

Is there a log somewhere that I can provide?

I am not sure the logs will help here as the conversion did not start.
I will get back to you once I learn more.

Hi,

I have been using my day off to come up with a better P2V solution for our company.

I ran into the same issue. I load Starwinds Converter on the Windows machine and run it.

1. Select P2V
2. I have used both "Physical Disk" and "Entire Machine"
3. I select all volumes (C: volume and usually two others show)
4. Select proxmox Server
5. Add hostanme and credentials
6. Connects as I can see my server volumes, I enter a Name, numeric ID, storage and machine info.
7. I have selected and not selected qcow2 format
8. Hit convert
9. The Starwind app screen disappears and nothing happens.

Logs show nothing much but this (last two lines):
7/5 12:53:56.089 3534 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::Connect: Successfully connected to proxmoxhost
7/5 12:53:56.089 3534 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVolumeSelect

I tested on an Intel based HDMI Atom Stick, 64GB volume, WIndows 10 Pro. Second test was a Samsung laptop, 500Gb volume, Windows 10 Pro.

Both machines seemed to show something happening with high CPU usage and network usage for the few seconds after the app disappeared from screen.

Appreciate any help, great that you are supporting Proxmox.

Thanks

Thanks for your input. I will keep you posted on R&D's response.

I just tested it again on a Windows 11 system. I have the same behavior there.

Hi,
Thanks for your update. I will keep you informed on the investigation.

The solution should be included in the next build.
Thanks for your cooperation.

Cool, I'm happy about that. I still have about a week of vacation left, maybe the new build will be ready after that.

Can I see the version number of the current build somewhere? I use the link in the email to download it, but the number is not included in the file name.

I am afraid that it will take longer than one week.
Have a nice vacations.

Can confirm this also happens when moving Hyper-V to Proxmox.

8/15 8:04:55.902 1700 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::Connect: Successfully connected to proxmoxhost
8/15 8:04:55.902 1700 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVolumeSelect
8/15 8:05:46.869 1700 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eConverting
8/15 8:05:46.892 2cc0 Facility ???INFO: CPPConverting::Convert: InConvertType: 8, OutConvertType: 15
8/15 8:05:46.893 2cc0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: CreateVM
8/15 8:05:46.893 2cc0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Set disks
8/15 8:05:46.893 2cc0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: disk name i, À¼ç
8/15 8:05:46.893 2cc0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Sending request
8/15 8:05:46.915 2cc0 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Responce is received
8/15 8:05:46.915 2cc0 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Can not create virtual machine: 400
8/15 8:05:46.915 2cc0 Facility ???WARNING: CPPConverting::Convert: CANCEL

Thank you for your support in this matter!

I have the same issue with the following environment,

Windows 10 Pro
Proxmox 8.2.4.
V2V Converter 9.0.1.509

When click "Convert" at the final step, the application disappeared immediately instead of starting the conversion process.

Awaiting for the new patches in the next release.

Thank you.

The dev team is working on it. Please keep an eye on the release notes.

same issue, same versions. testing converting an ubuntu vm, if that matters. something i noticed, the disk name is rather odd.

8/29 11:12:00.295 9e4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: CreateVM
8/29 11:12:00.295 9e4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Set disks
8/29 11:12:00.295 9e4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: disk name i, à9BÚ°
8/29 11:12:00.295 9e4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Sending request
8/29 11:12:00.320 9e4 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Responce is received
8/29 11:12:00.320 9e4 Facility ???ERROR: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Can not create virtual machine: 400