Restarting libvirtd on a cluster node causes vms to fail and relocate in RHEL

Solution Unverified - Updated -

Issue

  • When I update or add a libvirt VM configuration and restart libvirtd, several VMs managed by the cluster fail and restart or relocate.
  • After installing a new VM using virt-clone and restarting the libvirt daemon before adding the new VM into cluster.conf, all the VMs on the node we cloned the new VM will be moved to another cluster node.

Environment

  • Red Hat Enterprise Linux (RHEL) 5 Advanced Platform Clustering
  • Red Hat Enterprise Linux RHEL 6 with the High Availability Add-On
  • cluster-managed VM resources

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content