Exam 70-740 topic 1 question 4 discussion

Why? It should be B. live migration between a host with different switch name may disconnect VM from network.

Answer should be B. You can Live Migrate via shared-storage or shared-nothing without causing an interruption in vm service. However, if the destination switch has a different name than the source switch, migration will pause until you select which switch to use on the destination host. From https://blogs.technet.microsoft.com/canitpro/2013/01/03/shared-nothing-live-migration-goodbye-shared-storage/ "If your virtual machine is connected to a virtual switch then you need to have an identically named virtual switch on the destination host. If not your migration will be paused while you specify which switch to use on the destination server."

Everyone is arguing about the switch. We don't even have permissions. "Server administrator at a company" means nothing. We're also not in a domain? Is a domain not required? If a VM gets paused it also disconnects...

If they are in same subnet and external switch they can do migration.

Page 419 of Craig Zackers Exam ref 70-740. "The source and destination servers should have identical virtual switches that use the same name. If they do not, the migration process will be interrupted to prompt the operator to select a switch on the destination server."

Reffrence from https://docs.microsoft.com/sr-cyrl-rs/archive/blogs/canitpro/shared-nothing-live-migration-goodbye-shared-storage My answer is B, let me know what you think. Paused VM cannot be pinged, which means its disconnected from the network. --If your virtual machine is connected to a virtual switch then you need to have an identically named virtual switch on the destination host. If not your migration will be paused while you specify which switch to use on the destination server.

-B NO "ENSURE that you can MOVE virtual machines between the hosts" This means that the task must be completed and VMs actually moved.. not paused... actually moved. "Without causing the virtual machines to disconnect from the network" Nothing more than a distraction provided that there is nothing missing from the question.

I tested. For me is B The VMs aren't disconnected from the network but you haven't achieved live migration. You need to shutdown a VM to change the virtual switch name, so this VM will be disconnected to the network.

As a result #4,#5,#6 are same questions. I think the pattern it's possible to live migration is between Host1 and Host3. However this pattern isn't included in these questions. Host1:Host2 > NO > different processor(#5) Host1:Host3 > Yes > same processor Host1:Host4 > NO > different switch Host2:Host3 > NO > different processor Host2:Host4 > NO > different processor(#6) Host3:Host4 > NO > different switch(#4)

Failed because the host hardware isn't compatible If a virtual machine doesn't have processor compatibility turned on and has one or more snapshots, the move fails if the hosts have different processor versions. An error occurs and this message is displayed: The virtual machine cannot be moved to the destination computer. The hardware on the destination computer is not compatible with the hardware requirements of this virtual machine. To fix this problem, shut down the virtual machine and turn on the processor compatibility setting. From Hyper-V Manager, in the Virtual Machines pane, right-click the virtual machine and click Settings. In the navigation pane, expand Processors and click Compatibility. Check Migrate to a computer with a different processor version. Click OK.

A is correct, the same switch name is required if you want to avoid a pause. But the pause does not mean that there is a disconnection from the network.

Answer B: Requirements Any live migration, whether it be Hyper-V or any other platform, have a number of requirements in order to work. Both hosts must have chipsets in the same family – that is, you cannot live migrate an Intel to an AMD or vice-versa. If the processors are similar enough (i7 to i5 is fine, i7 to Core2 Duo is not) then no action is necessary. In the event that you do have dissimilar processors (newer and older but still within the same family, then you have to configure your virtual machine’s CPU compatibility, as outlined in the article Getting Started with Hyper-V in Server 2012 and Windows 8 . If your virtual machine is connected to a virtual switch then you need to have an identically named virtual switch on the destination host. If not your migration will be paused while you specify which switch to use on the destination server.

I got this question (30 June 2020)

I got this question (30 June 2020)

For me it's B. https://blog.workinghardinit.work/2019/11/04/shared-nothing-live-migration-with-a-virtual-switch-change-and-vlan-id-configuration/ "For me it's B. https://blog.workinghardinit.work/2019/11/04/shared-nothing-live-migration-with-a-virtual-switch-change-and-vlan-id-configuration/ "For me it's B. https://blog.workinghardinit.work/2019/11/04/shared-nothing-live-migration-with-a-virtual-switch-change-and-vlan-id-configuration/ "For me it's B. https://blog.workinghardinit.work/2019/11/04/shared-nothing-live-migration-with-a-virtual-switch-change-and-vlan-id-configuration/ "Making Shared nothing migration work The first step is to make sure shared nothing migration works. We can achieve this in several ways. Option 1 We can disconnect the virtual machine network adapters from their virtual switch. While this allows you to migrate the virtual machines, this leads to connectivity loss. This is not acceptable. Option2 We can preemptively set the virtual machine network adapters to a virtual switch with the same name as the one on the target and enable VLAN ID. Consequently, this means you have to create those and need NICs to do so"

If switches have different names there will be a pause until you specify the target but is this pause considered as disconnection from the network?

Correct answer is A. Live migration with different switch names only pauses the migration to prompt the user for destination switch name. It does NOT disconnect/stop the migration process.