[ClusterLabs] How to Fence Virtualbox VM with Windows 10 as host.

Marek Grac mgrac at redhat.com
Wed Jan 25 14:58:43 EST 2017

On Wed, Jan 25, 2017 at 7:10 PM, <durwin at mgtsciences.com> wrote:

> Marek Grac <mgrac at redhat.com> wrote on 01/25/2017 01:33:07 AM:
> > In your case it should be enough to set:
> > * ipaddr
> > * login
> > * port (= node to shutdown)
> Thank you.  man page says.
>        *-n, --plug=[id]*
>               Physical plug number on device, UUID or identification of
> machine This parameter is always required.
> How do I determine the 'plug' of the VM?  I the output of 'pcs stonith
> describe fence_vbox' refers to this as port (to my understanding, very
> misleading).

You are right. It is misleading, we have
https://fedorahosted.org/cluster/wiki/FenceArguments to maintain the table
conversion in human-readable format. We are backward compatible for 10+
years and in the ages of RHEL4 there was no virtualization for PC :)
However, with 4.1.x release we plan to synchronize the names (and be
backward compatible as before).

'plug' is a point on power switch that represent power plug that you wish
to switch off/on. In case of virtual machines it is either name or UUID of
the virtual machine.

> From your reply, am I correct in assuming nothing to support Fencing is
> required to run on the Windows host?

yes, it should be enough to have VBoxManage in the path. It should be a
configurable option but noone really asked for it yet.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20170125/7730ac2d/attachment-0003.html>

More information about the Users mailing list