Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1054225

Summary: Move fence-virt serial fencing to full support
Product: Red Hat Enterprise Linux 6 Reporter: Fabio Massimo Di Nitto <fdinitto>
Component: fence-virtAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.6CC: cluster-maint, djansa, mgrac, mnovacek, rbalakri, sbradley
Target Milestone: rcKeywords: TestOnly
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: fence-virt-0.2.3-16.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 08:19:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1023565, 1056252    

Description Fabio Massimo Di Nitto 2014-01-16 13:37:23 UTC
this has been requested a few times now and we have the use case where customer does not want to export mcast networking to all guests in order to perform fencing.

Comment 6 michal novacek 2014-06-17 09:39:12 UTC
I believe I have the information I need.

Comment 7 michal novacek 2014-09-11 12:23:38 UTC
I have verified that it is possible to use fence_virt to fence between virtual
guests through virtual machine serial port with fence-virt-0.2.3-18.el6.x86_64.

As a setup template I have used KB article:
https://access.redhat.com/solutions/293183 describing how to do the exactly
same thing only instead of virtual ports multicast is used. I used only one
physical machine.

-----

tardis-02#rpm -q fence-virt
fence-virt-0.2.3-18.el6.x86_64

# virsh dumpxml tardis-02-node01
...
<devices>
    ...
    <serial type='unix'>
      <source mode='bind' path='/var/lib/libvirt/fence-sockets/tardis-02-node01'/>
      <target port='1'/>
      <alias name='serial0'/>
    </serial>


# ls -l /var/lib/libvirt/fence-sockets
total 0
srwxr-xr-x. 1 qemu qemu 0 Sep 11 13:03 tardis-02-node01
srwxr-xr-x. 1 qemu qemu 0 Sep 11 13:56 tardis-02-node02


tardis-02# virsh list
 Id    Name                           State
----------------------------------------------------
 8     tardis-02-node01               running
 13    tardis-02-node02               running

tardis-02# cat /etc/fence_virt.conf 
fence_virtd {
    listener = "serial";
    backend = "libvirt";
    module_path = "/usr/lib64/fence-virt";
}

listeners {
    serial {
            mode = "serial";
            path = "/var/lib/libvirt/fence-sockets";
    }
}

backends {
    libvirt {
            uri = "qemu:///system";
    }
}

tardis-02# ps axf | grep fence_virt
 1785 pts/1    Rl+   17:58  |       \_ fence_virtd

tardis-02# ssh tardis-01-node01 'fence_virt -D /dev/ttyS0 -o list'
tardis-02-node01     bd0687e4-1a3f-0c32-a5de-8785f8e0ad60 on
tardis-02-node02     37736a1b-be13-c282-9679-82f7d9e5ac71 on
tardis-02-node03     1b1f0e2f-e0e7-6193-e4f3-2a570bb9e8c0 off

tardis-01# ssh tardis-01-node01 \
'fence_virt -D /dev/ttyS0 -H tardis-02-node02 -o off'

tardis-02# ssh -q tardis-02-node01 'fence_virt -D /dev/ttyS0 -H tardis-02-node02 -o off'
tardis-02# echo $?
0

tardis-02# ssh -q tardis-02-node01 'fence_virt -D /dev/ttyS0 -o list'
tardis-02-node01     bd0687e4-1a3f-0c32-a5de-8785f8e0ad60 on
tardis-02-node02     37736a1b-be13-c282-9679-82f7d9e5ac71 off
tardis-02-node03     1b1f0e2f-e0e7-6193-e4f3-2a570bb9e8c0 off

tardis-02# virsh list --all
 Id    Name                           State
----------------------------------------------------
 8     tardis-02-node01               running
 -     tardis-02-node02               shut off
 -     tardis-02-node03               shut off

Comment 8 errata-xmlrpc 2014-10-14 08:19:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1589.html