Windows P2V migration to Proxmox

[umr3323]

I’m facing an issue with a Windows P2V migration to Proxmox and could use some guidance.


Here’s what I’ve tried: I have the `qcow2` file in my local storage under the Import section. When creating the VM, I select Windows in the OS tab and attach the VirtIO ISO. In the Disks section, I leave it with no disk initially. After the VM is created, I import the `qcow2` file to the VM and add it to the boot order.


The problem is: if I set the `qcow2` disk as the first boot device, I get "No bootable device found." If I prioritize the Windows ISO instead, it just starts a fresh Windows install. So I’m stuck in a loop with no successful boot.


Can you please guide me on the correct way to attach and boot from the existing `qcow2` disk? Or if there’s a better method for P2V migration given I have `qcow2` + `vmdk` files and remote access to the source machine, I’d really appreciate it.


You can also reach me at mumarsaleem03@gmail.com if a quick demo session is possible.

 

[d.oishi]

right after a Windows migration, if the disk is attached on a SCSI bus and the SCSI Controller Type is set to VirtIO SCSI, Windows may fail to boot if the VirtIO driver has not been installed yet.
In the VM's Hardware tab, try detaching the disk once and reattaching it as IDE or SATA.

Once Windows boots successfully, install the VirtIO drivers first, and then switch the disk back to SCSI later if needed.

If it still does not boot, please also verify that the firmware setting matches the source machine (SeaBIOS vs. OVMF).

You may also find the following P2V migration guide helpful.
Personally, I found Clonezilla easier to work with, because it feels more straightforward and I do not have to think too much about the guest OS type or whether the migration is P2V or V2V.
https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE#Clonezilla_Live_CDs