Since you can see that the disk in the shot above is named vm-112-disk-1.qcow2, we can search for that on our Linux/ Proxmox VE host. Since we want to keep Proxmox VE’s naming convention (and make the process easy), we are going to simply overwrite the qcow2 image that the virtual machine wizard created. There are a few different ways you can do this, including creating the VM and attaching the disk after converting the vhdx. Hyper V Vhdx To Proxmox Qcow2 Create VM With Qcow2 Local Storage Step 5: Find the VMs qcow2 image Most modern OSes are supported via KVM so you should have little issue getting things to work, especially with Linux guests. Here the key is to ensure that you make a VM that mirrors the Hyper-V VM in terms of CPU, RAM, network and disk options. At this point, we wanted to create a VM that we are going to use with the image we transferred.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |