Linux Container Development
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: "Muralidhar,
	Rajeev D"
	<rajeev.d.muralidhar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org"
	<criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
	"containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	Andrey Vagin <avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Subject: Re: [CRIU] Re: Error compiling CRtools-0.1..
Date: Thu, 30 Aug 2012 18:04:31 +0400	[thread overview]
Message-ID: <20120830140431.GN21422@moon> (raw)
In-Reply-To: <604C0E70D2B64644B0BCE6939D9F7D0327E6C0-yHIBzpp8AekFyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>

On Thu, Aug 30, 2012 at 01:59:16PM +0000, Muralidhar, Rajeev D wrote:
> Hi Cyril
> 
> OK I will wait for your advice. 
> 
> If I try exactly 0.1 version, this is the error I get:
> 
> rdmurali@tapovan:~/Linux-CR/crtools-0.1$ sudo ./crtools check
> Error (cr-check.c:174): Counter mismatch (or not met) 0 want 13
> Error (cr-check.c:224): TFD mismatch (or not met) 0 want 4
> Error (cr-check.c:263): WD mismatch (or not met) -1 want 1

This rather a symptom for wrong kernel version. It's important
to run "crtools-3.6-rc1" kernel, not vanilla v3.6-rc1.

	Cyrill

  parent reply	other threads:[~2012-08-30 14:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 11:10 Error compiling CRtools-0.1 Muralidhar, Rajeev D
     [not found] ` <604C0E70D2B64644B0BCE6939D9F7D0327A1C6-yHIBzpp8AekFyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-30  7:15   ` Muralidhar, Rajeev D
     [not found]     ` <604C0E70D2B64644B0BCE6939D9F7D0327E011-yHIBzpp8AekFyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-30 12:55       ` Serge Hallyn
2012-08-30 13:10         ` [CRIU] " Cyrill Gorcunov
2012-08-30 13:16           ` Muralidhar, Rajeev D
     [not found]             ` <604C0E70D2B64644B0BCE6939D9F7D0327E623-yHIBzpp8AekFyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-30 13:30               ` Cyrill Gorcunov
2012-08-30 13:43                 ` Muralidhar, Rajeev D
     [not found]                   ` <604C0E70D2B64644B0BCE6939D9F7D0327E674-yHIBzpp8AekFyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-30 13:45                     ` Cyrill Gorcunov
2012-08-30 13:47                       ` Cyrill Gorcunov
2012-08-30 13:59                       ` Muralidhar, Rajeev D
     [not found]                         ` <604C0E70D2B64644B0BCE6939D9F7D0327E6C0-yHIBzpp8AekFyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-30 14:04                           ` Cyrill Gorcunov [this message]
2012-08-30 14:27                             ` Muralidhar, Rajeev D
     [not found]                               ` <604C0E70D2B64644B0BCE6939D9F7D0327E721-yHIBzpp8AekFyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-30 14:33                                 ` Cyrill Gorcunov

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=20120830140431.GN21422@moon \
    --to=gorcunov-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
    --cc=avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
    --cc=rajeev.d.muralidhar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /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