Re: Remus : VM on backup not in pause state

[Brendan Cully <brendan@cs.ubc.ca>]

On Thursday, 22 July 2010 at 13:45, Dulloor wrote:
> My setup is as follows :
> - xen : unstable (rev:21743)
> - Dom0 : pvops (branch : stable-2.6.32.x,
> rev:01d9fbca207ec232c758d991d66466fc6e38349e)
> - Guest Configuration :
> ------------------------------------------------------------------------------------------
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> name = "linux-hvm"
> vcpus = 4
> memory = 2048
> vif = [ 'type=ioemu, bridge=eth0, mac=00:1c:3e:17:22:13' ]
> disk = [ 'phy:/dev/XenVolG/hvm-linux-snap-1.img,hda,w' ]
> device_model = '/usr/lib/xen/bin/qemu-dm'
> boot="cd"
> sdl=0
> vnc=1
> vnclisten="0.0.0.0"
> vncconsole=0
> vncpasswd=''
> stdvga=0
> superpages=1
> serial='pty'
> ------------------------------------------------------------------------------------------
> 
> - Remus command :
> # remus --no-net linux-hvm <dst-ip>
> 
> - On primary :
> # xm list
> Name                                        ID   Mem VCPUs      State   Time(s)
> linux-hvm                                    9  2048     4     -b-s--     10.8
> 
> - On secondary :
> # xm list
> Name                                        ID   Mem VCPUs      State   Time(s)
> linux-hvm                                   11  2048     4     -b----      1.9
> 
> 
> I have to issue "xm pause/unpause" explicitly for the backup VM.
> Any recent changes ?

This probably means there was a timeout on the replication channel,
interpreted by the backup as a failure of the primary, which caused it
to activate itself. You should see evidence of that in the remus
console logs and xend.log and daemon.log (for the disk side).

Once you've figured out where the timeout happened it'll be easier to
figure out why.