Hyper-V vNext - VM versions and new functionality

It will be about build 10565.

As you probably know, when migrating a virtual machine (hereinafter VM) from 2012 R2 to vNext, there is no automatic conversion of the VM configuration to the new version, so that the VM can be migrated back. VM functional dependency it version:

1. "Hot" adding / deleting RAM - version VM 6.0
2. "Hot" adding / removing network adapters - VM version 5.0
3. Secure Boot for Linux VM - VM version 6.0
4. Production Checkpoints - VM version 6.0
5. PowerShell Direct - VM Version 6.2
6. Virtual TPM (vTPM) - VM version 6.2
7. Virtual Machine Grouping - VM version 6.2
')
It seems to me that PowerShell Direct has already been written here, but in short it is the ability to execute PowerShell commands in a VM via VMBus.

Enter-PSSession -VMName VMName"
Invoke-Command -VMName VMName -ScriptBlock { Commands }

It works only on vNext with guest vNext, you must enable all integration components and reboot the guest.

Find out the version of VM: Get-VM | ft Name,Version Get-VM | ft Name,Version
Create VMs compatible with 2012 R2 on vNext (starting from build 10565):. New-VM -Name " " -Version 5.0
Upgrade VM version: Update-VMVersion -Name " "

When updating, the format of the configuration files will change, new versions of VMs use the following file format:

1. Configuration file - binary .vmcx
2. File Runtime State - binary .vmrs
3. Disk - .vhd \ vhdx, unchanged
4. Differential disk files - .avhdx, used for checkpoints
5. Checkpoint files - when creating a checkpoint, .vmrs / .vmcx files and a differential disk file are created.

By the way, about checkpoints, Production Checkpoints are waiting for us in vNext. What this means, when creating a checkpoint, VSS will be called inside the VM, thus it will be possible to get a consistent VM state (along with VSS aware applications). I understand that when creating such a checkpoint, the operational memory and state will not be saved, i.e. when returning to this checkpoint, the VM will be loaded “from scratch”. In addition, you can select several checkpoint modes for VMs: Standard, Production, Production Only, Disabled. It's all pretty clear the only thing - the difference between "Production" and "Production Only", is that "Production" in case of an error VSS will make an ordinary checkpoint, and "Production Only" is not.

Maybe someone will throw information about Virtual Machine Grouping? I have not found anything ...