Hello, there,
we host some Debian Stretch (9) virtual machines on our Hyper-V. I configured these systems as Generation 1 virtual machine and used dynamically growing VHDX files as hard disk.
The odd thing is that the hard disk files (VHDX) grew to the configured maximum size of the hard disk, although the operating system only used 20-40% of the hard disk.
On Windows machines, the size of the hard disk file is always about the same as the size of the system that is occupying the hard disk.
What could be the reason for this?
As I understood it, the guest Windows recognizes the virtual hard disk as SSD and sends TRIM commands to the host. Thus Hyper-V knows which sectors are no longer in use and can reuse them. Is it necessary to enable such a feature in Debian? With ext4, for example, this is the discard feature.
Is it also better to switch to the second generation of virtual machines? I also wonder if it is better to connect the virtual hard disk via a SCSI controller or IDE controller?
we host some Debian Stretch (9) virtual machines on our Hyper-V. I configured these systems as Generation 1 virtual machine and used dynamically growing VHDX files as hard disk.
The odd thing is that the hard disk files (VHDX) grew to the configured maximum size of the hard disk, although the operating system only used 20-40% of the hard disk.
On Windows machines, the size of the hard disk file is always about the same as the size of the system that is occupying the hard disk.
What could be the reason for this?
As I understood it, the guest Windows recognizes the virtual hard disk as SSD and sends TRIM commands to the host. Thus Hyper-V knows which sectors are no longer in use and can reuse them. Is it necessary to enable such a feature in Debian? With ext4, for example, this is the discard feature.
Is it also better to switch to the second generation of virtual machines? I also wonder if it is better to connect the virtual hard disk via a SCSI controller or IDE controller?