WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Remus : VM on backup not in pause state

To: Dulloor <dulloor@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Remus : VM on backup not in pause state
From: Dulloor <dulloor@xxxxxxxxx>
Date: Thu, 22 Jul 2010 16:40:58 -0700
Cc:
Delivery-date: Thu, 22 Jul 2010 16:41:46 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Oe9WN3bt4E8JeUYwwodOuK0qU9mg36aDHhnkX4JtYNw=; b=GCj96afU6UZH2+6lCq6IXwt4wQxJgrKIM2VKPSGYJs2AFLiuozVnNZdv4toeKw0qYg NzEnjzt7xads0OXdt6PAEtcFDLmWWV55FchsMla1J7S3s+ZxNnAomUXS1LIbgAuhYGbp Trch0Qmv+FYhququv9gO9CE4103pso8jDvOU8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=MxkNgwssNdNG7eGkNaQjoBU043e7+AIyo70uGV0Ee/W7s3MknyXUomVqLn/sFPsZ29 jNsZ6lotYVjcFF4dOhCv15xiUxHWBf1zQItRXQM+M5RN+NtM69jcO5wOs9lvtiSQrqKo Ul7RhAqnf76sYRk61c8o24jd6vkNgYDkffA98=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100722214913.GE3994@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimMdbYpbLEMJooOTwdq-XpjLBmEVNBlnneuPoXz@xxxxxxxxxxxxxx> <20100722214913.GE3994@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Jul 22, 2010 at 2:49 PM, Brendan Cully <brendan@xxxxxxxxx> wrote:
> 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.
>
Please find the logs attached. I didn't find anything interesting in
daemon.log.
What does remus log there ? I am not using disk replication, since I
have issues with that .. but that's for another email :)

The only visible error is in xend-secondary.log around xc_restore :
[2010-07-22 16:15:37 2056] DEBUG (balloon:207) Balloon: setting dom0 target to 5
765 MiB.
[2010-07-22 16:15:37 2056] DEBUG (XendDomainInfo:1467) Setting memory target of
domain Domain-0 (0) to 5765 MiB.
[2010-07-22 16:15:37 2056] DEBUG (XendCheckpoint:290) [xc_restore]: /usr/lib/xen
/bin/xc_restore 5 1 5 6 1 1 1 0
[2010-07-22 16:18:42 2056] INFO (XendCheckpoint:408) xc: error: Error
when reading pages (11 = Resource temporarily unavailabl): Internal
error
[2010-07-22 16:18:42 2056] INFO (XendCheckpoint:408) xc: error: error
when buffering batch, finishing (11 = Resource temporarily
unavailabl): Internal error

If you haven't seen this before, please let me know and I will try
debugging more.

-dulloor

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel