Red Hat Bugzilla – Bug 493678
[RFE] Support Hyper-V fencing
Last modified: 2016-10-04 00:31:35 EDT
This RFE needs to get updated to the correct (fence) component once the RHEL6 component list is updated.
+++ This bug was initially created as a clone of Bug #493677 +++
Support RHEL fencing of RHEL guests running on HyperV
Two different use cases exist:
1) fencing guests that are running on W2k8-HyperV Standard (without HA)
2) fencing guests that are running on w2k8-hyperV DataCenter of Enterprise (with HA)
This RFE is to support fencing the first use case - running on W2K8-HyperV Std.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
*** Bug 614318 has been marked as a duplicate of this bug. ***
This is 3rd in priority after VMware and RHEV. Looking like a RHEL 6.3 target at the moment. No clear customer demand seen yet.
Closing this RFE for now. No current plans to support this because of lack of user interest and demand. Maybe re-opened later.
We, at the National Library of Medicine at NIH would very much like to see this feature.
We are a Red Hat Shop. We currently run clusters on vSphere, and we use the VMware fencing scripts. See our work at http://openi.nlm.nih.gov
As an educational institution, we get HyperV pracrically for free. The only thing preventing us from running Red Hat clusters on HyperV is the lack of a fencing agent. I would love to see a fencing agent for HyperV.
Just out of curiosity, what sort of demand study was done to support the statement "No clear customer demand seen yet?"
Do you use Systems Center to manage the HyperV environment?
Is this based on Win 2008 or Win2012 configurations?
Also - since you already have RHEL and the embedded hypervisor - any plans to use that?
Thanks for the quick response.
We need enterprise grade virtualization with live migration and HA. So the product that meets our needs is RHEV. RHEV is price competitive with vSphere, but as I mentioned, we get HyperV for free (Windows Server Datacenter costs us about $4 per instance). So, future VM deployments will be HyperV only for the forseeable future.
We have Microsoft System Center Virtual Machine Manager. Right now we use Win2008r2. We are looking forward to upgrading hypervisors to Win2012 when it becomes approved by NIH.
At this point, my only solution for fencing off a HyperV based VM is to reboot the entire hypervisor server via IPMI. That is not really a good method.
It should be possible to use fence agents that uses libvirt (which have support for hyperV - at least in upstream) - you can use either fence_virsh, or fence_virt daemon.