SCVMM Live migration issue

Hi all,
I have a SCVMM 2012 R2 on prod with a Hyper-V Host cluster having 4 nodes.
I am trying to live migrate hosts from one server to another all the virtual machine are having static IP, the migration is successful but after the migration i am getting this error :-
Error (23753)
The virtual machine or tier load balancer configuration requires an IP pool and there are no appropriate IP pools accessible from the host.
Recommended Action
Select a host with access to an appropriate IP pool and try the operation again.
I searched & found this KB related to the issue - http://support.microsoft.com/kb/2915463
but is there any other way to stop this error from reoccurring without creating an IP pool as i am having a DHCP in my network.
Please suggest.
Thanks,
Pranay.

Hi Pranay,
SCVMM has been engineered to require at least one IP pool to be configured as part of the SDN. The only way I have been able to stop this error for customers that have static assigned IP addresses on all their servers was to create a single IP
Pool against one of the logical networks and fill it with an IP range that is not in use i.e. 10.10.10.0/24.
Additionally depending on the number of servers you have, you could assign them all to a single IP pool with the correct IP range then statically assign the correct address to them from within the VM config.
Its not a great solution, but I have used the first option which will remove the error when LM VMs.
Kind Regards Michael

Similar Messages

SCVMM live migrations very slow

I'm running Hyper V with SCVMM 2012 in my test environment. 2 hosts connected to a MD1200 and set up in a cluster. Everything works perfectly, except that live migrations take a super long time. By this I mean that when I start the Migration Wizard it takes up to 5 minutes to rate the hosts, and then when it finally completes and I start the migration, it can take up to another 5 minutes to complete the move.In my production clusters this doesn't work this way, there the Migration Wizard takes seconds to rate the hosts and usually less than a minute to move the VM.The only major difference between my test environment and my production environment is that test is using direct SAS connections to the SAN, where in prod everything runs through switches. In prod one cluster is all 1gig and one cluster is 10gig and both are about the same...
This topic first appeared in the Spiceworks Community

Hey guys,
I have searched online and in MS forums, and cannot resolve my issue.
I have checked through similar articles, without any resolution.
Migrating
Mailbox From Exchange 2007 to Exchange 2010: Very Slow
Exchange 2013 Mailbox Migration Rate/Speed ?
Public Folders after migration
to Exchange 2013 are extremly slow
Exchange 2010 mailbox move to Exchange 2013
Single Mailbox Very Slow after 2003
to 2010 Migration
I have also come across the most common solution which is written here
http://support.microsoft.com/kb/2807668, however this is not my problem.
My problem is that mailbox migrations are SLOW, I'm talking about < 15MB per minute. I do NOT have any contentIndex errors on any of my databases, they are all healthy and stay healthy throughout the migrations. Both Exchange 2010 and 2013
are DAGs.
When I 'view details' from the ECP migrations page, I see things like 'Stalled duration
00:53:21 ', however like I said there is no errors, and nothing mentioned in the user report.
Get-ClientAccessServer | Test-MRSHealth this checks out fine, no problems.
I have disabled offloading on all of the NICs.
Is there anything else I can do or monitor to find out why its so slow?
Could it be because of DAG even though there are no errors and the state is healthy. Would an idea be to take down the dag during migration then add that after all is done?
Andrew Huddleston | Hillsong Church | Sydney

Hyper-v 2012 R2 Live migration issue in 2003 Domain function Level

hi Team ,
i recently build 2012 R2 Hyper-v Cluster with three node. Everrything working fine with out any issue . Cluster working also fine. Later i came across one issue when tried to Live migration virtual machine from one host to another . it failed all the time
while quick migration is working . i gone through few articles and find it is known issue with hyper-v 2012 R2 where domain functional level is set to 2003 . although they have provided Hotfix but no solution.
http://support.microsoft.com/kb/2838043
Please let me know if any one face similar issue and able to resolve by any hotfix. My host are updated .
Thanks
Ravindra
Ravi

Hi Ravi1987,
The KB2838043 is applied for Server 2012 node, Could you offer us the related cluster error event id, or you can refer the following article to check your cluster
network binding order is correct or not.
Configuring Windows Failover Cluster Networks
http://blogs.technet.com/b/askcore/archive/2014/02/20/configuring-windows-failover-cluster-networks.aspx
You can try to install recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters first, then monitor this issue again.
The KB download:
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://support.microsoft.com/kb/2920151
More information:
Windows Server 2008 R2 Live Migration – “The devil may be in the networking details.”
http://blogs.technet.com/b/askcore/archive/2009/12/10/windows-server-2008-r2-live-migration-the-devil-may-be-in-the-networking-details.aspx
I’m glad to be of help to you!

V-HBA Guest VM cannot Live Migration

Hi All,
I'm using Windows Server 2012 Data Center OS and configured the for the hyper-V server role with Fail-over cluster (4 Node – Cluster).
Each Physical server installed with Two Qlogic HBA Adapters.
We have configured following configuration on hyper-v Server and SAN (HP) storage.
Enabled the Virtual SAN Manager.
Created Each Hyper-V Host Virtual Fiber channel Switch. Each Host configured two adapters. (Fibre Channel SAN 1 / Fibre Channel SAN 2) .
Using the HP storage and enabled the switch port level (N_Port ID Virtualization (NPIV).
Created new VM and assign new two vHBA Adapters. Each adapter having two sets of wwn numbers.
Each Adapter SET A wwn Address discovered by SAN switch and configured the zone . However SET B not discovered but we manually created the zone for SET B for both Adapters.
Present the Storage to the VM and installed the MPIO. SAN disk visible on the VM disk management.
During the live migrate the VM to different host I’m getting below error.
Live migration of 'Virtual Machine TEST-Server' failed.
Virtual machine migration operation for 'TEST-Server' failed at migration destination 'HV02'. (Virtual machine ID 378AE3E3-5A4F-4AE7-92F8-D47855C2D1C5)
The virtual machine 'TEST-Server' is not compatible with physical computer 'HV02'. (Virtual machine ID 378AE3E3-5A4F-4AE7-92F8-D47855C2D1C5)
Could not find a virtual fibre channel resource pool with ID 'New Fibre Channel SAN1'
Could not find a virtual fibre channel resource pool with ID 'New Fibre Channel SAN2'
Event ID : 21502
I need some support from Expert for this issue. I’m trying to configure the Guest Cluster with HBA. The Quick Migration working fine but still failing with live migration. I want to resolve the live migration issue.
Aucsna

Hi Aucsna,
"it's issue with the Virtual SAN Switch label name."
Has the problem been solved ?
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Live Migration between two WS2012 R2 Clusters with SCVMM 2012 R2 creates multiple objects on Cluster

Hi,
I'm seeing an issue when migrating VM's between two 2012 R2 Hyper-V Clusters, using VMM 2012 R2, that have their Storage provided by a 4 Node Scale Out File Server Cluster that the two clusters share.
A migration between the two clusters is successful and the VM is operation but I'm left with two roles added to the cluster the VM has moved to instead of the expected one.
For example: Say I have a VM that was created on cluster A with SCVMM, resulting in a name of : "SCVMM Test-01 Resources"
I then do a live migration to Cluster B which has access to the same storage and then I end up with two new roles instead of one.
"SCVMM abw-app-fl-01 Resources" and "abw-app-fl-01"
The "SCVMM abw-app-fl-01 Resources" is left in an unknown state and "abw-app-fl-01" is operational.
I can safely delete "SCVMM abw-app-fl-01 Resources" and everything still works but it looks like something is failing during the process.
Has anyone else seen this?
I'll probably have one of my guys open a support ticket in the new year but was wondering if anyone else is seeing this.
Kind regards,
Jas :)

In my case the VMs where created in VMM in my one and only Hyper-V cluster (that's been created and is managed by VMM).
All Higly Available VM:s have a FCM role named "SCVMM vmname" where vmname is the name if the VM in VMM. On top of that a lot
of VM:s, but not all, have a second role name named vmname. Lots of name in that sentence.
All VMs that have duplicates are using the role named vmname.
I thought it had to do with whether a VM had been migrated so I took one that never had been migrated and did. It did not get a duplicate.
Is there any progress on this?

Vmm Protection Error, Unable to perform the live migration due to cloud protection issue for G2 system..Error (23833)

Error (23833)
The selected cloud does not support protection, or the recovery point objective requested for the virtual machine xxxx (30 seconds) is not within the range that the cloud supports.
Recommended Action
Select a different cloud, enable protection for the cloud, or change the requested recovery point objective for the virtual machine to a value greater than or equal to NO_PARAM seconds, and then try the operation again.

Microsoft has not provided me with much support on this issue, but I was able to resolve this myself. What you need to do is remove the DR Protection attribute from your VM using the command below.
Source:
Stop protecting a virtual machine
$vm = get-scvirtualmachine -Name "SQLVM1"
Set-SCVirtualMachine -VM $vm -ClearDRProtection
It is important to note that this command does nothing, unless the Azure Site Recovery provider is installed on your VMM server, and your VMM server is registered in ASR. Once I had run this command against my virtual machines, I was able to uninstall the
provider and unregister my server from ASR. Now my VM's are free to live migrate again.

Hyper-V 2012 R2 - live migration dynamic memory issue

Hi..
we use a two node hyper-v cluster.
On each node running 5 vm that shared the 64GB system memory.
The vms are configured to use dynamic memory. The sum of the startup (min) memory of the 10 vms are currently 50 GB.
So now our problem:
If we try to drain roles on node A for maintenance purpose two vms are still on node A because they wasted currently each 25GB memory and so on node B is not enough free memory to host this vms.
That sounds logical
But as all vms configured to use dynamic memory they should shrink their memory to get enough space for all vms? If we shutdown all vms, move it to one node, then everything works fine.
Is it by design that live migration do not trigger the vm to shrink their memory?
Best regards, Alexander Zirbes

Hi Alexander,
Dynamic memory means that memory can increase or decrease based on the demand of the VM, not based on the load of the Hyper-V host. If the gust OS of VM dont need that much memory, memory will be released. I dont think live migration has any role shrinking
the allocated memory of a VM.
Since you are using two node cluster, you should only load 50% resourses on each host so that incase of a failure of second node, the first node can have all the VMs.
This calculation will become more effective if you have more nodes. I am having a six node cluster and I load each host upto 80% so that in case of a single node failure, the VMs can be split on other five nodes without issues.
Cheers,
Shaba
Optimism is the faith that leads to achievement. Nothing can be done without hope and confidence.
InsideVirtualization.com

Hyper-V Live Migration Compatibility with Hyper-V Replica/Hyper-V Recovery Manager

Hi,
Is Hyper-V Live Migration compatible with Hyper-V Replica/Hyper-V Recovery
Manager?
I have 2 Hyper-V clusters in my datacenter - both using CSVs on Fibre Channel arrays. These clusters where created and are managed using the same "System Center 2012 R2 VMM" installation. My goal it to eventually move one of these clusters to a remote
DR site. Both sites are connected/will be connected to each other through dark fibre.
I manually configured Hyper-V Replica in the Fail Over Cluster Manager on both clusters and started replicating some VMs using Hyper-V
Replica.
Now every time I attempt to use SCVMM to do a Live Migration of a VM that is protected using Hyper-V Replica to
another host within the same cluster,
the Migration VM Wizard gives me the following "Rating Explanation" error:
"The virtual machine virtual machine name which
requires Hyper-V Recovery Manager protection is going to be moved using the type "Live". This could break the recovery protection status of the virtual machine.
When I ignore the error and do the Live Migration anyway, the Live migration completes successfully with the info above. There doesn't seem to be any impact on the VM or it's replication.
When a Host Shuts-down or is put into maintenance, the VM Migrates successfully, again, with no noticeable impact on users or replication.
When I stop replication of the VM, the error goes away.
Initially, I thought this error was because I attempted to manually configure
the replication between both clusters using Hyper-V Replica in Failover Cluster Manager (instead of using Hyper-V Recovery Manager).
However, even after configuring and using Hyper-V Recovery Manager, I still get the same error. This error does not seem to have any impact on the high-availability of
my VM or on Replication of this VM. Live migrations still occur successfully and replication seems to carry on without any issues.
However, it now has me concern that Live Migration may one day occur and break replication of my VMs between both clusters.
I have searched, and searched and searched, and I cannot find any mention in official or un-official Microsoft channels, on the compatibility of these two features.
I know vMware vSphere replication and vMotion are compatible with each otherhttp://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.replication_admin.doc%2FGUID-8006BF58-6FA8-4F02-AFB9-A6AC5CD73021.html.
Please confirm to me: Are Hyper-V Live Migration and Hyper-V Replica compatible
with each other?
If they are, any link to further documentation on configuring these services so that they work in a fully supported manner will be highly appreciated.
D

This can be considered as a minor GUI bug.
Let me explain. Live Migration and Hyper-V Replica is supported on both Windows Server 2012 and 2012 R2 Hyper-V.
This is because we have the Hyper-V Replica Broker Role (in a cluster) that is able to detect, receive and keep track of the VMs and the synchronizations. The configuration related to VMs enabled with replications follows the VMs itself.
If you try to live migrate a VM within Failover Cluster Manager, you will not get any message at all. But VMM will (as you can see), give you an
error but it should rather be an informative message instead.
Intelligent placement (in VMM) is responsible for putting everything in your environment together to give you tips about where the VM best possible can run, and that is why we are seeing this message here.
I have personally reported this as a bug. I will check on this one and get back to this thread.
Update: just spoke to one of the PMs of HRM and they can confirm that live migration is supported - and should work in this context.
Please see this thread as well: http://social.msdn.microsoft.com/Forums/windowsazure/en-US/29163570-22a6-4da4-b309-21878aeb8ff8/hyperv-live-migration-compatibility-with-hyperv-replicahyperv-recovery-manager?forum=hypervrecovmgr
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

2012 R2 Cluster and Live Migration

6 Node Cluster with Server 2012 R2, all VM's are Server 2012 R2
4 Fiber SAN's
Moving and Live Migration worked fine in FailOver Cluster Manager
But this time we were trying do it with SCVMM 2012 R2 and just move one VM (Gen2)
Of course it failed at 99%
Error (12711)
VMM cannot complete the WMI operation on the server (whatever) because of an error: [MSCluster_Resource.Name="SCVMM VMHost"] The cluster resource could not be found.
The cluster resource could not be found (0x138F)
Recommended Action
Resolve the issue and then try the operation again.
How do I fix this? the VM is still running. The two vhdx files it was moving are smaller then orginal's , but it change the configuration file to point to new ones, which are bad.
it says I can Repair it... Redo or Undo....of course neither of those options work.
Wait for the object to be updated automatically by the next periodic Live migrate storage of virtual machine vmhost from whatever to whatever job.
ID: 1708
Cluster has no errors, SAN's have no errors, CSV have no errors. the machine running scvmm is VM running on the cluster

How did you create this VM? if this is created outside of VMM, I recommend doing a manual refresh of the VM first to ensure that VMM can read its attributes. Then retry the operation.
Btw, are the VMs using diff disk? any checkpoints associated with them?
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Live Migration : virtual Fibre Channel vSAN

I can do live migration, from one node to another. No error. Problem / Question that I have is, is live migration really lie migration.
When I do live migration from cluster or SCVMM it save and start virtual machine. Which fro me is not live migration.
I have describe in more details : http://social.technet.microsoft.com/Forums/en-US/a52ac102-4ea3-491c-a8c5-4cf4dd14768d/synthetic-fibre-channel-hba-live-migration-savestopstart?forum=winserverhyperv
BlatniS

I can do live migration, from one node to another. No error. Problem / Question that I have is, is live migration really lie migration.
When I do live migration from cluster or SCVMM it save and start virtual machine. Which fro me is not live migration.
I have describe in more details : http://social.technet.microsoft.com/Forums/en-US/a52ac102-4ea3-491c-a8c5-4cf4dd14768d/synthetic-fibre-channel-hba-live-migration-savestopstart?forum=winserverhyperv
Virtual Fibre Channel had sense in pre-R2 times when there was no shared VHDX and you had to somehow provide fault tolerant shared storage to guest VM cluster (spawning iSCSI target on top of FC was slow and ugly). Now there\s no point in putting one into
production so if you have issues just use shared VHDX. See:
Deploy a Guest Cluster Using a Shared Virtual Hard Disk
http://technet.microsoft.com/en-us/library/dn265980.aspx
Shared VHDX
http://blogs.technet.com/b/storageserver/archive/2013/11/25/shared-vhdx-files-my-favorite-new-feature-in-windows-server-2012-r2.aspx
Shared VHDX is much more flexible and has better performance.
Good luck!
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Live migration of domains with OVMM

Can anybody point out the reference for performing live migration of domains through OVM Manager instead of CLI. Could not find it in the User's manual for OVM Server 2.2 release.

Does the same thing happen if you initiate the live migration from within SCVMM? Generally speaking, if SCVMM is in use, you should first try to perform the operation from SCVMM before trying to use the Failover Cluster Manager or the Hyper-V Manager.
Should not make any difference, but it would be another point of information.
What is so strange is that a live migration within the cluster is not doing anything with the disks. All it is doing is moving the executing VM from the memory of one node of the cluster to another node in the cluster. The virtual hard disks,
.vhd or .vhdx, are not touched, unless when you say 'live migration' you mean 'live storage migration'. Very strange that it is only happening on the VMs with .vhd.
Another thing you could try ... convert the .vhd on one of the problematic VMs to a .vhdx file and see if that fixes the issue.
. : | : . : | : . tim

Unable to Live Migrate to Some Hosts

We have been having issues where we cannot Live Migrate to some of our hosts. I have verified the VMM Agent is the same version and the Host OS are the same. I've compared all settings in VMM and Hyper-V between hosts that are Live Migration Candidates against
hosts that are not Live Migration Candidates. The Rating Message for those that we are unable to Live Migrate to is the following:
Unable to migrate or clone the virtual machine "" because the version of virtualization software on the host does not match the version of virtual machine's virtualization software on source (6.3.9600.17334). To be migrated or cloned,
the virtual machine must be stopped and should not contain any saved state.
Any help resolving this is greatly appreciated!

Hi,
i have also a few questions. You say, that you are the total noob. Therefore you should check the total noob things :)
What Version of SCVMM are you using?
What about your infrastructure? Hyper-V Cluster? And how many Cluster?
Are you trying to migrate between Hyper-V Cluster? Or between Cluster nodes?
Are the VMs made high available on your Hyper-V Host?
Does the target host have access to the shared volume?
did you check the processor version?
Check the Patch Level of the Hosts and the Agents
Are source and destination host the same OS Version and Patch level? Are they both in the same Cluster?
without knowing more about your infrastructure i could ask a lot more questions. It would be cool if you could give us some more information about your setup. OR let us know your solution if you are able to fix the problem.
regards,
Thomas
Thomas Hanrath [MCT | Regional Lead Germany]
Follow me on TWITTER
Thomas Hanrath Private Cloud Blog
Microsoft Learning and Certification Blog

Hyper-v 2012 r2 slow throughputs on network / live migrations

Hi, maybe someone can point me in the right direction, I have 10 servers 5 Dell r210s and 5 Dell R320's, I have basically converted these servers to standalone hyper-v 2012 servers, so there is no clustering on any at the moment.
Each server is configured with 2 1Gb nics teamed via a virtual switch, now when I copt files between server 1 and 2 for example I see 100MBs throughput, but if I copy a file to server 3 at the same time the file copy load splits the 100MBs throughput between
the 2 copy processes. I was under the impression if I copied 2 files to 2 totally different servers the load would basically be split across the 2 nics effectively giving me 2Gbs throughput but this does not seem to be the case. I have played around with tcpip
large send offloads, jumbo packets, disabled vmq on the cards, they are broadcoms. :-( but it doesn't really seem to make a difference with all of these settings.
The other issue is If I live migrate a 12Gb vm machine running only 2gb ram, effectively just an o/s it takes between 15 to 20 minutes to migrate, I have played around with the advanced settings, smb, compression, tcpip not real game changers, BUT if I shut
town the vm and migrate it, it takes, just under 3 and a half minutes to move across.
I am really stumped here, I am busy in a test phase of hyper-v but cant find any definitive documents relating to this stuff.

Hi Mark,
The servers (hyper-v 2012 r2) are all basically configured with ssvmm2012R2 where they all have teamed 1Gb pNics, into a virtual switch, then there are vNics for the Vmcloud, live migration etc. The physical network is 2 Netgear Gs724T switches which
are interlinked and each servers 1st nic is plugged into the switch1 and the second nic is plugged into the switch2.See Below Image) The hyper-v port is set to independent Hyper-v load balancing.
The R320 servers are running raid 5 sas drives, the R210s have 1Tb drives mirrored. The servers all are using DAS storage, we have not moved to looking at using iscsi and san is out the question at the moment.
I am currently testing between 2x 320s and 2x R210s, I am not copying data to the vm's yets, I am basically testing the transfer between the actual hosts at the moment by copying a 4Gb file manually, After testing the live migrations I decided to test to
see the transfer rates between the servers first, I have been playing around with the offload settings and rss, what I don't understand is yesterday, the copy between the servers was running up to 228Mbs ie (using both nics) when copying
the file between the servers, and then a few hours later it only was copying at 50/60Mbs, but its now back at 113Mbs seemingly to be only using one nic.
I was under the impression if you copy a file between 2 servers the nicks could use the 2gb bandwidth, but after reading many posts they say only one nic, so how did the copies get up to 2Gb yesterday. Then again if you copy files between 3 servers, then
each copy would use one nic, basically giving you 2Gbs, but this is again not being seen.
Regards Keith

Server 2012 cluster - virtual machine live migration does not work

Hi,
We have a hyper-v cluster with two nodes running Windows Server 2012. All the configurations are identical.
When I try to make a Live migration from one node to the other I get an error message saying:
Live migration of 'Virtual Machine XXXXXX' failed.
I get no other error messages, not even in event viewer. This same happens with all of our virtual machines.
A normal Quick migration works just fine for all of the virtual machines, so network configuration should not be an issue.
The above error message does not provide much information.

Hi,
Please check whether your configuration meet live migration requirement:
Two (or more) servers running Hyper-V that:
Support hardware virtualization.
Yes they support virtualization.
Are using processors from the same manufacturer (for example, all AMD or all Intel).
Both Servers are identical and brand new Fujitsu-Siemens RX300S7 with the same kind of processor (Xeon E5-2620).
Belong to either the same Active Directory domain, or to domains that trust each other.
Both nodes are in the same domain.
Virtual machines must be configured to use virtual hard disks or virtual Fibre Channel disks (no physical disks).
All of the vitual machines have virtual hard disks.
Use of a private network is recommended for live migration network traffic.
Have tried this, but does not help.
Requirements for live migration in a cluster:
Windows Failover Clustering is enabled and configured.
Yes
Cluster Shared Volume (CSV) storage in the cluster is enabled.
Yes
Requirements for live migration using shared storage:
All files that comprise a virtual machine (for example, virtual hard disks, snapshots, and configuration) are stored on an SMB share. They are all on the same CSV
Permissions on the SMB share have been configured to grant access to the computer accounts of all servers running Hyper-V.
Requirements for live migration with no shared infrastructure:
No extra requirements exist.
Also please refer to this article to check whether you have finished all preparation works for live migration:
Virtual Machine Live Migration Overview
http://technet.microsoft.com/en-us/library/hh831435.aspx
Hyper-V: Using Live Migration with Cluster Shared Volumes in Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/dd446679(v=WS.10).aspx
Configure and Use Live Migration on Non-clustered Virtual Machines
http://technet.microsoft.com/en-us/library/jj134199.aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support
I have also read all of the technet articles but can't find anything that could help.

Live Migration Fails with error Synthetic FiberChannel Port: Failed to finish reserving resources on an VM using Windows Server 2012 R2 Hyper-V

Hi, I'm currently experiencing a problem with some VMs in a Hyper-V 2012 R2 failover cluster using Fiber Channel adapters with Virtual SAN configured on the hyper-v hosts.
I have read several articles about this issues like this ones:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/baca348d-fb57-4d8f-978b-f1e7282f89a1/synthetic-fibrechannel-port-failed-to-start-reserving-resources-with-error-insufficient-system?forum=winserverhyperv
http://social.technet.microsoft.com/wiki/contents/articles/18698.hyper-v-virtual-fibre-channel-troubleshooting-guide.aspx
But haven't been able to fix my issue.
The Virtual SAN is configured on every hyper-v host node in the cluster. And every VM has 2 fiber channel adapters configured.
All the World Wide Names are configured both on the FC Switch as well as the FC SAN.
All the drivers for the FC Adapter in the Hyper-V Hosts have been updated to their latest versions.
The strange thing is that the issue is not affecting all of the VMs, some of the VMs with FC adapters configured are live migrating just fine, others are getting this error.
Quick migration works without problems.
We even tried removing and creating new FC Adapters on a VM with problems, we had to configure the switch and SAN with the new WWN names and all, but ended up having the same problem.
At first we thought is was related to the hosts, but since some VMs do work live migrating with FC adapters we tried migrating them on every host, everything worked well.
My guess is that it has to be something related to the VMs itself but I haven't been able to figure out what is it.
Any ideas on how to solve this is deeply appreciated.
Thank you!
Eduardo Rojas

Hi Eduardo,
How are things going ?
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCVMM Live migration issue

Similar Messages

Maybe you are looking for