*Hi*
*Recently, I met some problems in learning sheepdog.*
*I have 2 machines. They information follow:*
*Node1[10.198.3.141]*
eth1 Link encap:Ethernet HWaddr FC:48:EF:2E:47:2B
inet addr:10.198.3.141 Bcast:10.198.3.191 Mask:255.255.255.192
UP BROADCAST RUNNING
Your Host are 10.198.3.141 and 10.198.4.108 and
not in the same IP Subnet. (Are you able to ping
these host among each other at all?)
Your corosync listen to 192.168.1.1, which seem
to be no local interface on your hosts.
And your sheep processes listen to 127.0.0.1 which
is the loopback
2014-07-30 9:29 GMT+02:00 Hitoshi Mitake mitake.hito...@lab.ntt.co.jp:
Valerio, Fabian, could you test this series?
It seems to work fine.
I notice the warning message vary a bit on the node with the latest qemu
version.
root@test005:~# qemu-system-x86_64 -enable-kvm -drive file=sheepdog:test
I've been testing also kill and kill -9.
With kill the lock gets removed.
With kill -9 it doens't (as expected).
'vdi lock force-unlock' works fine but I notices 2 things:
1) the syntax doesn't mentions 'vdiname'
dog vdi lock {list|force-unlock} [-a address] [-p port] [-h] [-t]
it should be
dog
I tried to vdi check a locked vdi.
vdi check ignore the lock.
I remember from previous discussions that we must not run vdi check on used
vdi.
So I guess vdi check should exit with the same qemu warning message.
If the guest is not running (because of qemu crash etc) but the lock is
active, it's
