questions about moving existing VM to proxmox

[quattro]

After running HyperV forever, I'm FINALLY dipping my toes in the the Proxmox world.

I've found excellent tutorials on moving a hyperv disk to Proxmox, but they are all on a default Proxmox configuration with one drive.

My setup has the OS on a small SSD and a 2TB hardware raid 1 array.

I created a thinpool on the 2TB drive and created a tesst windows VM from scratch in Proxmox with the drive on that volume.

I next want to move an existing hyperv drive onto the 2TB drive array to be converted and imported. That hyperv drive is larger then the OS SSD drive.

I am unable to determine the best method of moving the hyperv drive to the 2TB drive array.

The name of my LV-Thin volume is data and it show just fine in the gui.

In a terminal window, I browse to \dev\data and can see pointer files for my existing windows guest machine, pointing to the device file dm-5.

My newbie question is where to I upload my windows hyperv disk file so that when I import it, it is stored on the LV-Think volume with the existing windows guest machine?

Thanks!

 

[gzader]

Can you mount the current drive hosting the vm file to your proxmox system? Or copy it off to USB disk? Then you can mount that, import into proxmox then move the image file via gui (hardware > hard disk >migrate) to your thin drive.


I'm new to this too so guessing a little here.

 

[alexskysilk]

I next want to move an existing hyperv drive onto the 2TB drive array to be converted and imported. That hyperv drive is larger then the OS SSD drive.

how much payload is actually on the volume? if its more then the target storage, this is a no-go. If its less, there are a number of ways to accomplish.

1. you can resize the source vdisk on hyperv
2. you can use a tool such as acronis to transfer the system target size aware
3. if you intend to grow your proxmox pool, you can use direct conversion (qemu-img or export-vm) to import and convert your vhdx onto a thin provisioned pool as is.

 

[markf1301]

You haven't mentioned what size the os is, or the hyperv-image, or what types of 'images' they are.
Here's the link for migrating data from 1 system to another. I'm in the middle of that myself, just from on older qemu server to pve. section 3 covers the import/conversion process. Mine's, mostly - a 3 step process: scp the file over from the old server to the new one, use the import process, set the network/hardware/cpu/mem info and power it up. you need to be sure that you install the qemu utils on the server before you move it over and pay attention to the 'type' of volume you have (sata/sas/etc) so that when it's imported - you can set those correctly. also, be sure to 'enable' the qemu tools on the image.