Problems with Convert Physical Machine to Proxmox

[yaroslav (staff)]

Is the source disk name ASCII?
Please wait for the next build for converting quemu.

[swigle]

it doesn't matter if i select the qcow2 checkbox or not, the disk name is english alphnumeric, no spaces, but the disk name in the log always has either AÚ or BÚ in the middle, even trying to convert different machines with very different disk names.

from back to back runs

Code: Select all

8/29 13:15:57.338 2018 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: disk name i,  =BÚ°
8/29 13:17:28.263 2118 Facility ???INFO: Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: disk name i, `8BÚ°

also, while running tcpdump on the proxmox host does show several connection to the api after clicking convert, there are several 200 queries that are the information gathering then the last line in the pveproxy access.log is

Code: Select all

root@pam [29/08/2024:13:44:42 -0700] "POST /api2/json/nodes/**redacted**/qemu HTTP/1.1" 400 79

[yaroslav (staff)]

Conversion to QUEMU does not run smoothly for this build. Should be fixed in the next build.

[swigle]

is there an estimated date for it's release yet?

[yaroslav (staff)]

From what I heard from the R&D team representative, the build should be ready in 2-3 weeks.

[jean.tech]

We experience the same problem. And would love to have a solution.

[ryanmelitante]

same problem for me

[yaroslav (staff)]

The build should be there soon.

[tig_jeff]

Seems that the issue (and excuse me if this has already been said) is that the source disk, on Hyper-V, has a space in the name (or invalid characters). Rename the disk and re-attach it to the VM. Test it out, to make sure, and then you should be able to convert it.

This has worked for me.

[yaroslav (staff)]

Yes, that's a very good point.

[lblaesius@merios.de]

Hi,
are there any updates on the new release?
We got the same Problem:
Proxmox::WrapperProxmox::WrapperProxmoxImpl::CreateVM: Can not create virtual machine: 400

I´m hoping the new release is coming soon. This is curently the best way to get from AWS to Proxmox.

[yaroslav (staff)]

Hi,

The dev and QA teams are still working on the update. Please keep an eye on the release notes https://www.starwindsoftware.com/v2v-co ... ease-notes.

[wolf]

Waiting desperately for the next build. Tried renaming the local volumes on a windows 10 physical machine (system, data) and rebooted before trying again. Same behavior: Application crash after entering all the details for the vm on the proxmox server.

[hatho]

I installed the new version (Version 9 (build 554)).
I wanted to migrate win10 machine to Proxmox but unfortunately, I still get the same error, or rather no error at all. The window simply disappears without an error message.

I already had the same error with the previous version. Should the error be fixed with the current release?

[yaroslav (staff)]

That's a known issue of the build you are using (same as the OP, I think).
The fix should be in the next build. Stay tuned!
As a workaround, try converting the disks to the remote non-Proxmox host.