What should you configure on VM1?

HOTSPOT
Your network contains two servers named Server1 and Server2 that run Windows Server
2012 R2. Server1 and Server2 have the Hyper-V server role installed.
Server1 and Server2 have different processor models from the same manufacturer.
On Server1, you plan to create a virtual machine named VM1. Eventually, VM1 will be
exported to Server2.
You need to ensure that when you import VM1 to Server2, you can start VM1 from saved
snapshots.
What should you configure on VM1?
To answer, select the appropriate node in the answer area.

HOTSPOT
Your network contains two servers named Server1 and Server2 that run Windows Server
2012 R2. Server1 and Server2 have the Hyper-V server role installed.
Server1 and Server2 have different processor models from the same manufacturer.
On Server1, you plan to create a virtual machine named VM1. Eventually, VM1 will be
exported to Server2.
You need to ensure that when you import VM1 to Server2, you can start VM1 from saved
snapshots.
What should you configure on VM1?
To answer, select the appropriate node in the answer area.

Answer:

Explanation:

Use the Processor Compatibility Mode only in cases where VMs will migrate from one
Hyper-V-enabled processor type to another within the same vendor processor family.
http://technet.microsoft.com/en-us/magazine/gg299590.aspx



Leave a Reply 5

Your email address will not be published. Required fields are marked *


Martin

Martin

From the same manufacturer? So Intel is Intel? It’s not like AMD vs Intel in this one?

MEAT HEAD

MEAT HEAD

if you look under HV manager the processor compatibility settings let you enable migration to physical computer with different processor VERSION…. so this would cover INTEL > AMD as well as INTEL Core i7 to INTEL XEON for example… there are different feature sets even between INTEL chips.

hth

James L

James L

MEAT HEAD/Serg. No. Absolutely NOT !!!

Note carefully that the decision to enable Processor compatibility mode is only a consideration when doing any form of migration that does not require shutting down the VM ie Live migration. The only other scenario of note is if you move the VM using export and import and then apply a snapshot taken on the old Hyper-V host.
This is the scenario in this question, it is not a live migration!!! but as mentioned above, the export/import with subsequent snapshot application is the other VM migration scenario where you would choose to enable it so IMO the answer is correct

For the sake of clarifying the above statement, it may be worth noting that in this scenario if there were no snapshot to be applied after the export/import there would be no need to enable the Processor compatibility mode as the VM is shut down to perform the export/import

You can of course move a VM to any Hyper-V host from any processor manufacturer/type to any processor manufacturer/type whenever you perform any method of migration that involves shutting down the VM during the move

Digixorcist

Digixorcist

What James L says, is correct.

There are important concepts to understand when using processor compatibility mode in Hyper-V:
Running virtual machines can only be migrated between virtualization hosts that use processors from the same manufacturer.
You must shut down the virtual machine before you can enable or disable processor compatibility mode.

** Processor compatibility mode is not needed for virtual machines moves that involve a stop and restart of the virtual machines. **

Any time a virtual machine is restarted, the guest operating system will enumerate the processor features that are available on the new host computer.

https://technet.microsoft.com/en-us/library/dn859550.aspx

However, the question indicates that you must start servers from SAVED snapshots. Which means the server will NOT be actually restarted! Therefore, the answer to the question (“processor compatibility”) is still correct, but the reasoning behind it is different!