[drbd-mc] Some VMs ignored by drbd-mc - strange recovery
rasto.levrinc at gmail.com
Mon Sep 5 13:46:54 CEST 2011
On Thu, Sep 1, 2011 at 5:47 PM, Whit Blauvelt <whit.drbd at transpect.com> wrote:
> After confirming that 0.9.4 and 0.9.5 had the same problem with showing all
> the VMs as 0.9.7, I was logged into a different VM by ssh (called "geos_x")
> - not on a DRBD resource in this case, but drbd-mc had recognized it as
> existing. In the ssh session I did a shutdown. I also had a console opened
> into it via drbd-mc at the time, and the VMs list open in drbd-mc.
> On shutting down geos_x, drbd-mc blinked a number of times, and finally
> stabilized with the "missing" VMs showing in the VMs list.
> Okay, what's that about?
first there can be some mix-up with uuids, like having the same uuid
for different VMs across the cluster.
DRBD MC looks for the /etc/libvirt/qemu/*.xml to get a list of VMs. If
you use sudo make sure the user can read this directory.
Then it calls e.g. "virsh dominfo geos3" and "virsh dumpxml geos3" to
see if they are defined.
you can also try to execute "/usr/local/bin/drbd-gui-helper-0.9.7
get-vm-info" on all cluster nodes to see what is going on.
More information about the drbd-mc