Use cmdlet to live migrate VM changing the vNetwork.
Question
-
Good morning.
I have to live migrate VMs from “Hyper-v on Server 2012” to “Hyper-v Server 2012 R2”.
Well, at the same time I have to migrate all the storage (Config, Snapshots, Pagingfiles and VHDs).
Up to here everything is ok.
At the same time without loose the VMs connectivity I have to change the vNetwork because the vNetworks on the new Hosts are different.
I will use Move-VM powershell cmdlet, example:
Move-VM $VM remoteServer –VirtualMachinePath $Path1 –SnapshotFilePath $Path1 –SmartPagingFilePath $Path1 –IncludeStorage –VHDs @(@{"SourceFilePath" = $OldVHDPath1; "DestinationFilePath" = $NewVHDPath1}, @{"SourceFilePath" = $OldVHDPath2; "DestinationFilePath" = $NewVHDPath2})
When I do it manually through the Hyper-v Console, it ask me to change it:
How can I change vSwitch at the same time that I Move the VM using a cmdlet without loosing connection?
Thanks in advance and have a nice week,
Angel Biurrun.
Answers
All replies
-
For Connect-VMNetworkAdapter:
- the name for the destination switch has to be on the local host or it fails - you can not just put the name of the destination VSwitch in - it has to actually reside at source host or the command fails.
- If you create a 'dummy' local Vswitch that is not connected to network on source host - you will lose network on VM until the migration completes. (but seems to be the only way that Connect-VMNetworkAdapter will not fail.
- The GUI actually makes the change at time of migration - only 1 ping is lost. I have NOT found a powershell way to do this.
I found that even after "adjusting the NIC" as shown in other scripts (to a new local NIC that has same name as remote server - which drops the network btw) - If I just passed the same compatibility report to the Move-VM command it would fail - as it is still 'incompatible' (changing the NIC does not update the report) - after changing the NIC I then had to refresh the compatibility report - then the migration would succeed.
Not working:
$VMReport.Incompatibilities | ?{$_.MessageID -eq 33012} | %{Connect-VMNetworkAdapter $_.source -SwitchName "vSwitch1"} Move-VM -CompatibilityReport $VMReport -AsJobError
Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- 10 Job10 NotStarted True Move-VM -Compatibi... PS C:\Windows\system32> Get-Job 10 | Receive-Job -Keep Virtual machine migration operation failed at migration destination. The virtual machine 'PACEOM01' is not compatible with physical computer '3215R05-19'. Virtual machine migration operation for 'PACEOM01' failed at migration destination '3215R05-19.MSCPEC.COM'. (Virtual machine ID E2EC2CAF-31D0-407D-860A-EC0252C1842F) The virtual machine 'PACEOM01' is not compatible with physical computer '3215R05-19'. (Virtual machine ID E2EC2CAF-31D0-407D-860A-EC0252C1842F) Could not find Ethernet switch 'MGMT'. Could not find Ethernet switch 'MGMT2'. + CategoryInfo : NotSpecified: (:) [], VirtualizationException + FullyQualifiedErrorId : UnspecifiedStep by step break down of error.
1. Run the report and see the issue with switches.
PS C:\> (Compare-VM -Name PACEOM01 -DestinationHost 3215R05-19 -IncludeStorage -DestinationStoragePath e:\Hyper-V\PACEOM01).Incompatibilities |fl * Message : Virtual machine migration operation for 'PACEOM01' failed at migration destination '3215R05-19.MSCPEC.COM'. (Virtual machine ID E2EC2CAF-31D0-407D-860A-EC0252C1842F) MessageId : 21026 Source : Message : The virtual machine 'PACEOM01' is not compatible with physical computer '3215R05-19'. (Virtual machine ID E2EC2CAF-31D0-407D-860A-EC0252C1842F) MessageId : 24000 Source : Message : Could not find Ethernet switch 'MGMT'. MessageId : 33012 Source : VMNetworkAdapter (Name = 'Network Adapter', VMName = 'PACEOM01') [VMId = 'e2ec2caf-31d0-407d-860a-ec0252c1842f'] Message : Could not find Ethernet switch 'MGMT2'. MessageId : 33012 Source : VMNetworkAdapter (Name = 'Network Adapter', VMName = 'PACEOM01') [VMId = 'e2ec2caf-31d0-407d-860a-ec0252c1842f']So I need to attach these to vSwitch1 on the destination host.
Here are my existing source switches:
Name SwitchType NetAdapterInterfaceDescription ---- ---------- ------------------------------ MGMT External QLogic BCM57800 10 Gigabit Ethernet (NDIS VBD Client) #131 MGMT2 External QLogic BCM57800 10 Gigabit Ethernet (NDIS VBD Client) #130 Corp External QLogic BCM57800 Gigabit Ethernet (NDIS VBD Client) #133
So if I now try to run the commands that everyone point at it fails - not able to find a vSwitch with that name "vSwitch1".
PS C:\> $VMReport = Compare-VM -Name PACEOM01 -DestinationHost 3215R05-19 -IncludeStorage -DestinationStoragePath e:\Hyper-V\PACEOM01 PS C:\> $VMReport.Incompatibilities Message ------- Virtual machine migration operation for 'PACEOM01' failed at migration destination '3215R05-19.MSCPEC.COM'. (Virtual machine ID E2EC2CAF-31D0-407D-860A-EC0252C1842F) The virtual machine 'PACEOM01' is not compatible with physical computer '3215R05-19'. (Virtual machine ID E2EC2CAF-31D0-407D-860A-EC0252C1842F) Could not find Ethernet switch 'MGMT'. Could not find Ethernet switch 'MGMT2'. PS C:\> $VMReport.Incompatibilities | ?{$_.MessageID -eq 33012} Message MessageId Source ------- --------- ------ Could not find Ethernet switch 'MGMT'. 33012 VMNetworkAdapter (Name = 'Network Adapter', VMName = 'PACEOM01') [VMId = 'e2ec2caf-31d0-407d-860a-ec0252c1842f'] Could not find Ethernet switch 'MGMT2'. 33012 VMNetworkAdapter (Name = 'Network Adapter', VMName = 'PACEOM01') [VMId = 'e2ec2caf-31d0-407d-860a-ec0252c1842f'] PS C:\> $VMReport.Incompatibilities | ?{$_.MessageID -eq 33012} | %{Connect-VMNetworkAdapter $_.source -SwitchName "vSwitch1"} Connect-VMNetworkAdapter : Hyper-V was unable to find a virtual switch with name "vSwitch1". At line:1 char:61 + ... 33012} | %{Connect-VMNetworkAdapter $_.source -SwitchName "vSwitch1" ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Connect-VMNetworkAdapter], VirtualizationException + FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.ConnectVMNetworkAdapter Connect-VMNetworkAdapter : Hyper-V was unable to find a virtual switch with name "vSwitch1". At line:1 char:61 + ... 33012} | %{Connect-VMNetworkAdapter $_.source -SwitchName "vSwitch1" ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Connect-VMNetworkAdapter], VirtualizationException + FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.ConnectVMNetworkAdapter
This is my workaround (with VM network outage), after creating a dummy local switch & then running the report twice - once to find the issue - fix it & a second time to create a clean report so the move will complete.
$targethost = "3215R05-19" #Read-Host "Name of target Hyper-V Host" $VMS = Get-VM | Out-Gridview -Title "Running VM’s" -Passthru ForEach ($VM in $VMS) { md \\$targethost\e$\Hyper-V\$($VM.Name) -ErrorAction SilentlyContinue $VMReport = Compare-VM -Name $VM.Name -DestinationHost $targethost -IncludeStorage -DestinationStoragePath e:\Hyper-V\$($VM.Name) ($VMReport.Incompatibilities).MessageID if ($VMReport.Incompatibilities | ?{$_.MessageID -eq 33012}) { $VMReport.Incompatibilities | ?{$_.MessageID -eq 33012} | %{Connect-VMNetworkAdapter $_.source -SwitchName "vSwitch1"} $VMReport = Compare-VM -Name $VM.Name -DestinationHost $targethost -IncludeStorage -DestinationStoragePath e:\Hyper-V\$($VM.Name) } Move-VM -CompatibilityReport $VMReport -AsJob } 21026 24000 33012 33012 Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- 11 Job11 NotStarted True Move-VM -Compatibi... 21026 24000 33012 33012 12 Job12 NotStarted True Move-VM -Compatibi... 21026 24000 33012 33012 13 Job13 NotStarted True Move-VM -Compatibi... PS C:\> Get-Job Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- 11 Job11 Running True 3173R03-32 Move-VM -Compatibi... 12 Job12 Running True 3173R03-32 Move-VM -Compatibi... 13 Job13 Running True 3173R03-32 Move-VM -Compatibi...
Nics moved to dummy vSwitch on source host
But disconnected in VM (so outage)
On destination they will attach to the real vSwitch1 on the destination host.
- Proposed as answer by NeighborGeek Monday, April 8, 2019 7:13 PM
