virtualbox.org

I want to convert my physical Windows 10 (UEFI) to virtual, for use in VirtualBox, and as far as I know, the easiest method is by using the VMware converter tool, which creates a VMDK file.

1. Is there a performance penalty or known issues with using a VMDK, rather than a VDI?
2. Is there a performance penalty or known issues with using a P2V virtual disk in general?
3. After I have the virtual disk file, how should I create and configure the VM for optimum performance, for a Win10 guest? (I have i5-6500, integrated graphics, 8 GB ram)
4. Any general tips or caveats etc?

I did this once, so I know it works. But this time, I want to do it right...

I read that P2V can be done also with CloneZilla, but I am not familiar with that method.

You can also image the physical PC with Disk2VHD, or use a commercial (with free version) tool such as Macrium Reflect (*).

The performance questions regarding VMDK (or VHD) are moot, because neither is the preferred format for use in VirtualBox. So in either case you should convert to VDI before use.

For optimum performance you would share CPU and RAM resources equitably with the host, install the GAs and locate the VM on an SSD.

(*) Macrium Reflect is a backup tool, not a P2V tool, however it's almost as easy to use. You first create an "ad hoc" ISO which contains the Macrium Restore CD files plus your macrium backup image. This ISO can be reused for future P2V projects. You create a VM which is compatible with the physical PC as best you can. No need to install an OS, just create the VM. Then you boot the VM from the ad-hoc ISO. Macrium takes care of correcting partition sizes, converting between EFI and MBR BIOSes etc.

(**) An "Ad Hoc ISO" is not an actual ISO file. It's just a folder on the host PC which VirtualBox will treat as the contents of a data CD.

p.s. I believe the last time you asked a related question was here: viewtopic.php?f=2&t=85971&p=409691#p409691.

@mpack, thanks for all your help. I think I will try out the Disk2VHD method this time, and then convert it to VDI, using CloneVDI-exe-3.02

mpack wrote:create an "ad hoc" ISO which contains the Macrium Restore CD files plus your macrium backup image.

So I have Macrium Reflect, and I have a live usb with the rescue environment.
What next?

ANSWER: I found a post on the Macrium Reflect forum that explains the process.
https://knowledgebase.macrium.com/displ ... al+Machine
But it has a hitch because when the recovery environment starts up, it can't find the system image file on your file system.
So that's why you need to do it like was explained by @mpack, and create an "ad hoc" iso image.
This is how I did it:

1. Mount the Macrium recovery ISO.
2. Copy the files to a folder.
3. Make a subfolder in it, containing the Macrium system image, i.e., the actual backup file.

Create an ISO from the main folder, using ImgBurn.

Shmu26 wrote: Create an ISO from the main folder, using ImgBurn.

Yes, you can do it that way, but it involves a lot of unnecessary processing and file copying. Just create the ad hoc ISO as I mentioned before. Unfortunately VirtualBox doesn't yet have an API in the manager for doing this, so you have to launch some other VM, and use the Devices|Optical|Create ad-hoc VISO... tool. This brings up a dialog which is similar to the one you use to create ISOs in ImgBurn, except it creates a ".viso" file that you can copy elsewhere and treat as an ISO in VirtualBox.

I.e. if you were able to create a bootable ISO with ImgBurn then you also know how to create it as a VISO.

p.s. The linked Macrium help page mentions using "Redeploy". I seem to recall that "Redeploy" is not part of Macrium Reflect Free, but the free edition will do the corrections I already mentioned.

Thanks. I am on Macrium Reflect Home, which is paid, but still doesn't have redeploy.
It does have a boot fixer tool, though.
I am currently stuck at the grub rescue screen, when trying to boot my newly created P2V Win10 guest.
viewtopic.php?f=7&t=95671

mpack wrote: The performance questions regarding VMDK (or VHD) are moot, because neither is the preferred format for use in VirtualBox. So in either case you should convert to VDI before use.

This is a very important point that I did not know. I have an old VMDK that I have been using in VirtualBox for a long time, and have always been disappointed by its performance. Today I converted it to VDI with your tool, and it's zipping along now. I thought I had corrupted the disk somehow, but all it needed was a conversion to VDI.