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 810877 - VMs started on more than one host
Summary: VMs started on more than one host
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rgmanager
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-09 14:01 UTC by Lon Hohberger
Modified: 2012-04-09 14:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-09 14:19:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 96543 0 None None None Never

Comment 2 Lon Hohberger 2012-04-09 14:01:59 UTC
Description of problem:

* If the libvirt-guests initscript is enabled while rgmanager is managing the
-same- virtual machines, the initscript, being not cluster-aware, will start
VMs already under rgmanager control on other hosts in the cluster.

* If the guests are configured to autostart using 'virsh autostart', the
libvirt tools will automatically start the virtual machines already under
rgmanager control on other hosts in the cluster.

These situations can end up with data loss in the virtual machines.

When running the cluster software to manage virtual machines, it is very
important to adhere to the following:

1) The libvirt-guests init script must be disabled.

2) All guests configured for cluster control must be disabled from an
auto-start perspective (e.g. virsh autostart --disable myvm1).

3) It is a best practice to use a non-default path for storing virtual machine
configuration files.  For example, use /mnt/guests (the default is
/etc/libvirt/qemu).  NOTE: If this is correctly done, steps (1) and (2) may not
be necessary.

4) Cluster-managed virtual machines must be managed using the cluster software.
 Do not mix usage of virt-manager, virsh, or other tools with rgmanager / luci.


The combination of these provide the following benefits:

a) Deterministic virtual machine behavior

b) Prevention of accidental management by other, non-cluster tools.


Note You need to log in before you can comment on or make changes to this bug.