Size increase of the disk when converting from VHDX

EngChiVi

Member
Sep 21, 2020
11
2
8
Greetings,

I want to bring my first VM as P2V of Windows 10 to Proxmox. Within Proxmox I have a cluster of 3 nodes where on each I have the following storage - 1 TB local-lvm , local, and 1TB zfs that i hoped to use for VM storage. My disk images are coming from NAS via NFS share.

My source has two physical disks, each 1TB in size, however only small amounts are used by partitions
Disk1 1TB physical, C:\ drive, 60GB Partition (data cleaned up and partition shrank down to 60 GB) , file1.VHDX of 60GB created by disk2vhd tool
Disk2 1TB physical, D:\ drive, 20GB Partition (data cleaned up and partition shrank down to 20 GB) , file2.VHDX of 20GB created by disk2vhd tool

I have on hand two VHDX files that total 80 GB of space. When I try to import , however Proxmox is trying to create 1TB files for each source drive (vs 60 GB)
When I try Solarwind converter, it similarly tries to create 1TB drives.

What am I missing?
and should I be trying clonezilla instead - I want destination drive on target VM to be 60GB and 20GB in size, not 1TB +1TB

Thank you. first VM. awesome software. first cluster I have set up
 
I think my problem is that my sources are 'dynamic disks' and tools I use dont know what to do with them and see them as 1TB drives.. Will be doing some more reading of what to do with it..
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!