Problem
After you enable Virtual Fibre Channel on a Hyper-V VM it takes forever to start up. In this instance forever equals about two minutes. The VM is stuck in the Starting… stat for most of this period.
Analysis
During startup, the Hypervisor waits for LUNs to appear on the virtual HBA before the VM is allowed to boot the OS. When there are no LUNs defined for a VM, i.e. when you are deploying a new VM, the Hypervisor patiently waits for 90 seconds before it gives up. Thus startup of the VM is delayed by 90 seconds if there are no LUNs presented to the VM, or if the SAN is down or misconfigured. Event ID 32213 from Hyper-V-SynthFC is logged:
Solution
Depending on your specific cause, one of the following should do the trick:
- Present some LUNs
- Remove the Virtual HBA adapters if they are not in use
- Correct the SAN config to make sure the VM is able to talk to the SAN
I have the same issue , as soon as i add VFC to VM , the VM stuck at startup for up to 60-70 sec. And in case of live migration the delay is also 60-70 sec. But i cannot find this event in event viewer.
Any idea how to solve this issue.
Sounds like you may be experiencing a similar issue. Have you checked the Hyper-V event logs on both hosts during migration?
Also, ask your SAN admin about multipath-settings and check if the LUNs are mirrored on the SAN-side. I have seen some trouble related to MPIO path verification. If it is disabled on the VM and/or host, try enabling it. If it is enabled, try to disable it.
The most common issue I see is where the LUNs are only presented to the one set of virtual WWNs. Both sets are used during migration of the VM.
FC switches (the physical ones) may also be worth looking in to. You may have to update their firmware to properly support virtual FC. The firmware on the SAN itself may also be an issue.
The LUNs are properly configured on the SAN and after 60 sec delay the VMs starts properly and show all LUNs. The issue is delay in startup & live migration.