This article provides information that can help when troubleshooting Hyper-V virtual Fibre Channel issues. This article covers topics on configuration and runtime that are needed to troubleshooting issues that might arise.
Applies to: Windows Server 2012, Windows Server 2012R2 Table of Contents Before you continueIntroduction Requirements for Virtual Fibre ChannelLimitationsInteroperability with other Hyper-V featuresIs Fibre Channel over Ethernet (FCoE) supported?What is the virtual port creation process?Sample event log entries Virtual machine startup Example event log where LUN’s failed to appear as available on virtual machine startupExample event log when LUN’s successfully appear as available on virtual machine startup.Virtual machine running Example event logs showing LUN addition for a running virtual machineExample event log showing LUN removal for a running virtual machineVirtual machine power off Example event log showing virtual machine PowerOffVirtual machine save Example event log showing the successful completion of a save operationVirtual machine pauseVirtual machine resetVirtual machine restore Example event logs showing a successful restore operation of a virtual machineExample event logs showing Failure in discovering LU mappings on VM restoreVirtual Fibre Channel and Live MigrationVirtual Fibre Channel and Quick MigrationTroubleshooting samples
The following is a list of Hyper-V features that are compatible with virtual Fibre Channel.
The following is a list of Hyper-V features that are not compatible with virtual Fibre Channel
Virtual tape libraries configured with a virtual Fibre Channel adapter are only supported when using System Center Data Protection Manager 2012 R2 U3 or later with certified hardware. For more information, see Compatible Tape Libraries for System Center 2012 DPM. To determine if a tape library is supported by virtual Fibre Channel adapter, contact the tape library hardware vendor or run the DPM Tape Library Compatibility Test tool. For additional information about the DPM Tape Library Compatibility Test took, see Verify tape library compatibility.
· UI: “This device or driver does not support virtual Fibre Channel.”
· Event Log: Warning 32170 logged by VMMS at startup
· WMI: Msvm_ExternalFcPort property IsHyperVCapable = False upon running the following query :
· gwmi -n root\virtualization\v2 Msvm_ExternalFcPort -Property InstanceId, WWPN, IsHyperVCapable
· If Querying for MSFC_FibrePortNPIVMethodsEx or MSFC_FibrePortNPIVAttributes returns Invalid Class then Rebuild portion of WMI store Mofcomp /i c:\windows\system32\wbem\npivwmi.mof
· If the HBA is from Emulex, use OneCommand to set Host Driver Parameter “EnableNPIV” to Enabled, then reboot
· If the above remediation steps are not applicable or do not work, contact the server or HBA vendor for driver, firmware updates
Remediation - Check the status of each HBA assigned to the virtual SAN and repair if necessary Evidence: Event Log events state "No physical port available to satisfy the request".
Log Name: Microsoft-Windows-Hyper-V-SynthFc-Admin
Source: Microsoft-Windows-Hyper-V-SynthFcVdev
Date: 7/23/2013 12:03:37 PM
Event ID: 32161
Task Category: None
Level: Error
Keywords:
User: NT VIRTUAL MACHINE\F0F713F5-BFD6-4EB5-B3CC-44F734E170EF
Computer: TestComputer
Description:
'VM1': Operation for virtual port (C003FFC780230002) failed with an error: No physical port available to satisfy the request (Virtual machine ID F0F713F5-BFD6-4EB5-B3CC-44F734E170EF).
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Event ID: 12004
'VM1' Synthetic FibreChannel Port: Failed to start reserving resources with Error 'Insufficient system resources exist to complete the requested service.' (0x800705AA). (Virtual machine ID F0F713F5-BFD6-4EB5-B3CC-44F734E170EF)
Event ID: 12030
· HBA failing to remove virtual port
· Host unresponsiveness
· The failure of the HBA to remove the virtual port can be confirmed by:
o Verifying that no running VM is using same WWPN
o Checking for virtual port removal failures in event log (see below in example event logs)
· Mitigation: Remove the port using HBA management tools or by using a WMI call or by rebooting the host. Escalate the issue with the HBA and fabric vendors
· If a host hang is confirmed by identifying fabric ports using fabric management tools, reboot connected host or disable the offending fabric port
· WWPN “A” and “B” not included in zones and masking sets
· Virtual SAN on remote node missing
· Destination host has fewer paths to target than the origin host
· LUNs associated with the VM do not appear as available at the destination node
· Analyze the event logs on the destination:
o If Virtual SAN missing, log will have specific details. Create SAN to fix
o If LUNs are missing:
§ Double check Virtual SAN’s assigned HBAs are connected to same fabric
§ Confirm WWPN “A” and “B” are included in zones and masking sets
§ Confirm the number of paths to target will be the same
I found the problem. What I was seeing was the infamous "unknown LUN 0", which all the systems hooked to the fibre channel are showing the same unknown device, even the Hyper-V hosts. The reason why I did not see the disk is because I had the WWN entered incorrectly in LUN mask on the RAID enclosure. Once I fixed the mapping, the disk appeared just as it should. Live migration is working perfectly as well.
I have a strange situation in Hyper-V 2012R2 with a 2008R2 guest. The VM starts, the "Microsoft Hyper-V Fibre Channel HBA" device and SAN disk exist in Device Manager, I have confirmed on the Fibre switch that it swaps the NPIV entries between WWN A and WWN B during live migration.
So here is the problem: the drive says "The Device Is Not Ready" when I try and do anything with it, and under disk properties it says "Unknown" and reports 0 MB. It also shows LUN 0 no matter what LUN I map it to. I know it's the drive device because the device name matches the enclosure model. Also, if I mask the LUN or disable that zone, the drive disappears.
How can I troubleshoot this?
@yoniphile Thank you for the feedback and the updated information. We are currently verifying the information you provided and will update the article appropriately.
Hi. I work at EMC where we qualified/tested Data Domain virtual tape library for use with virtual fibre channel and Microsoft DPM at Microsoft's request. Therefore, the caveat that "Tape libraries are not currently supported on virtual machines configured with a Virtual Fibre Channel adapter" should be removed from this article. (It looks like I have the ability to do that myself but didn't want to...)
Storage accessed through a virtual Fibre Channel adapter supports devices that 'resent' logical units... I think you meant "present".
Still, with 2008 server, how do you troubleshoot NOT EVEN HAVING THE CHOICE OF AN "Add Hardware > Fibre Channel Adapter" to a new VM? Neither do I see the "Virtual SAN Manager" in the Hyper-V Manager (that I have in 2012 Hyper-V). This is perplexing.
Great article. Congratulations.