From: Brendan Cully <brendan@cs.ubc.ca>
To: taojiang628 <taojiang628@163.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: a problem about xen4.0 remus
Date: Thu, 8 Jul 2010 18:05:07 -0700 [thread overview]
Message-ID: <20100709010507.GB28972@kremvax.cs.ubc.ca> (raw)
In-Reply-To: <201007090859577034343@163.com>
I have no idea where that kernel comes from or how old it is. It may
be missing event-channel suspend support. Try building the 2.6.18 tree
hosted at xenbits: http://xenbits.xen.org/linux-2.6.18-xen.hg
On Friday, 09 July 2010 at 08:59, taojiang628 wrote:
>
> My guest kernel is 2.6.18-128.e15xen . So what should I do about this problem. Thank you!
>
> 2010-07-09
>
>
>
> taojiang628
>
>
>
> 发件人: Brendan Cully
> 发送时间: 2010-07-07 01:44:14
> 收件人: taojiang628
> 抄送: xen-devel
> 主题: Re: [Xen-devel] a problem about xen4.0 remus
>
> On Tuesday, 06 July 2010 at 15:20, taojiang628 wrote:
> > hello:
> > I have a problem about the remus, I use xen-4.0-test.hg+linux-2.6.18-xen.hg ,anyone know what should I do about this problem. Thank you!
> > [root@localhost ~]# remus -i 100 centos5.4 192.168.10.190
> > Disk is not replicated: tap:aio:/root/xen/domains/centos-5.4/disk.img,xvda,w
> > modprobe -q ifb
> > WARNING: suspend event channel unavailable, falling back to slow xenstore signalling
> > Had 0 unexplained entries in p2m table
> > 1: sent 65252, skipped 284, delta 23066ms, dom0 24%, target 0%, sent 92Mb/s, dirtied 0Mb/s 365 pages
> > 2: sent 365, skipped 0, delta 128ms, dom0 29%, target 0%, sent 93Mb/s, dirtied 10Mb/s 41 pages
> > 3: sent 41, skipped 0, Start last iteration
> > PROF: suspending at 1278311972.985159
> > installing buffer on imq0... done.
> > SUSPEND shinfo 0000027b
> > delta 55ms, dom0 94%, target 5%, sent 24Mb/s, dirtied 69Mb/s 117 pages
> > 4: sent 117, skipped 0, delta 3ms, dom0 100%, target 0%, sent 1277Mb/s, dirtied 1277Mb/s 117 pages
> > Total pages sent= 65775 (0.97x)
> > (of which 0 were fixups)
> > All memory is saved
> > PROF: resumed at 1278311973.044589
> > PROF: flushed memory at 1278311973.048302
> > PROF: suspending at 1278311973.101436
> > timeout polling fd
> > ERROR Internal error: Suspend request failed
> > ERROR Internal error: Domain appears not to have suspended
> > Save exit rc=1
> > Exception exceptions.KeyError: 'imq0' in <bound method BufferedNIC.__del__ of <xen.remus.device.BufferedNIC object at 0xb7971a4c>> ignored
> > [root@localhost ~]#
> What kernel are you using for your guest? The event channel warning
> suggests it's not 2.6.18. If you can, use the Xen 2.6.18 kernel for
> your guest as well. Also, take a look at the instructions here:
> http://nss.cs.ubc.ca/remus/doc.html
next prev parent reply other threads:[~2010-07-09 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 7:20 a problem about xen4.0 remus taojiang628
2010-07-06 17:44 ` Brendan Cully
2010-07-09 0:59 ` taojiang628
2010-07-09 1:05 ` Brendan Cully [this message]
2010-07-09 5:16 ` Pasi Kärkkäinen
2010-07-09 5:40 ` Keir Fraser
2010-07-09 13:01 ` Re: [Xen-devel] " taojiang628
2010-07-09 12:53 ` Re: " taojiang628
2010-07-09 17:28 ` Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100709010507.GB28972@kremvax.cs.ubc.ca \
--to=brendan@cs.ubc.ca \
--cc=taojiang628@163.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).