October 22, 2015 at 16:11Hyper-V vNext - VM Versions and New Features
It will be about assembly 10565.
As you probably know, when migrating a virtual machine (hereinafter VM) from 2012 R2 to vNext, the configuration of the VM does not automatically convert to the new version so that the VM can migrate back. Dependence of the VM functional version:
1. “Hot” adding / removing RAM - VM version 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 they already wrote about PowerShell Direct, but in short it is an opportunity to execute PowerShell commands in VM through VMBus.
Works only on vNext with vNext guest, you must enable all integration components and overload the guest.
Find out the VM version:
Create a VM compatible with 2012 R2 on vNext (starting from build 10565):.
VM version upgrade:
When updating, the format of the configuration files will be changed, new versions of the VM will use the following file format:
1. Configuration file - binary .vmcx
2. Runtime State file - binary .vmrs
3. Disk - .vhd \ vhdx, no change
4. Disc difference files - .avhdx, used for checkpoints
5. Checkpoint files - when creating a checkpoint, .vmrs / .vmcx files and a difference disk file are created.
By the way, about checkpoints, in vNext Production Checkpoints are waiting for us. What does this mean, when creating a checkpoint, VSS will be called inside the VM, thus it will be possible to obtain a consistent state of the VM (together with VSS aware applications). I understand that when creating such a checkpoint, the RAM and state will not be saved, i.e. when you return to this checkpoint, the VM will boot from scratch. In addition, you can select several modes of checkpoints for VMs: Standard, Production, Production Only, Disabled. Here, everything is pretty clear, the only difference between “Production” and “Production Only” is that “Production” will make a normal checkpoint in case of a VSS error, but “Production Only” will not.
Perhaps someone will throw information about Virtual Machine Grouping? I did not find anything ...
As you probably know, when migrating a virtual machine (hereinafter VM) from 2012 R2 to vNext, the configuration of the VM does not automatically convert to the new version so that the VM can migrate back. Dependence of the VM functional version:
1. “Hot” adding / removing RAM - VM version 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 they already wrote about PowerShell Direct, but in short it is an opportunity to execute PowerShell commands in VM through VMBus.
Enter-PSSession -VMName VMName"Invoke-Command -VMName VMName -ScriptBlock { Commands } Works only on vNext with vNext guest, you must enable all integration components and overload the guest.
Find out the VM version:
Get-VM | ft Name,VersionCreate a VM compatible with 2012 R2 on vNext (starting from build 10565):.
New-VM -Name "Имя ВМ" -Version 5.0VM version upgrade:
Update-VMVersion -Name "Имя ВМ"When updating, the format of the configuration files will be changed, new versions of the VM will use the following file format:
1. Configuration file - binary .vmcx
2. Runtime State file - binary .vmrs
3. Disk - .vhd \ vhdx, no change
4. Disc difference files - .avhdx, used for checkpoints
5. Checkpoint files - when creating a checkpoint, .vmrs / .vmcx files and a difference disk file are created.
By the way, about checkpoints, in vNext Production Checkpoints are waiting for us. What does this mean, when creating a checkpoint, VSS will be called inside the VM, thus it will be possible to obtain a consistent state of the VM (together with VSS aware applications). I understand that when creating such a checkpoint, the RAM and state will not be saved, i.e. when you return to this checkpoint, the VM will boot from scratch. In addition, you can select several modes of checkpoints for VMs: Standard, Production, Production Only, Disabled. Here, everything is pretty clear, the only difference between “Production” and “Production Only” is that “Production” will make a normal checkpoint in case of a VSS error, but “Production Only” will not.
Perhaps someone will throw information about Virtual Machine Grouping? I did not find anything ...