kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: OHMURA Kei <ohmura.kei@lab.ntt.co.jp>
To: Sterling Windmill <sterling@ampx.net>
Cc: tamura.yoshiaki@gmail.com, qemu-devel@nongnu.org,
	Pradeep Kumar <psuriset@linux.vnet.ibm.com>,
	kvm@vger.kernel.org
Subject: Re: [KVM][Kemari]: Build error fix
Date: Fri, 29 Jun 2012 04:13:38 +0900	[thread overview]
Message-ID: <4FECACE2.9080100@lab.ntt.co.jp> (raw)
In-Reply-To: <CACYggxPBhjMLgkZLf6ey5W24ngT5_T1FdqTznWR1090bQBZZFA@mail.gmail.com>

On 2012/06/28 5:34, Sterling Windmill wrote:
> Is Kemari still in active development?

No, it's not. Currently we have no intention to add new features into
Kemari.

Thanks,
Kei

>
> Best regards,
> Sterling Windmill
>
> On Sun, Dec 4, 2011 at 9:45 PM, OHMURA Kei <ohmura.kei@lab.ntt.co.jp <mailto:ohmura.kei@lab.ntt.co.jp>> wrote:
>
>     On 2011/12/02 21:51, Pradeep Kumar wrote:
>      > It fixes build failure.
>      >
>      > I hit this error, after succsfull migration and sync.
>      >
>      > (qemu) qemu-system-x86_64: fill buffer failed, Interrupted system call
>      >
>      > qemu-system-x86_64: recv header failed
>      >
>      > qemu-system-x86_64: recv ack failed
>      >
>      > qemu_transaction_begin failed
>
>     Did you use master branch?
>     It is not latest version. next branch is latest and fixed error.
>
>     git://kemari.git.sourceforge.net/gitroot/kemari/kemari <http://kemari.git.sourceforge.net/gitroot/kemari/kemari> next
>
>     Thanks,
>     Kei
>
>      >
>      > Any one working on this now?
>      >
>      >>From 827c04da6574be80d8352acd7c40b0b4524af5f4 Mon Sep 17 00:00:00 2001
>      > Date: Fri, 2 Dec 2011 18:11:40 +0530
>      > Subject: [PATCH]  [Qemu][Kemari]: Build Failure
>      >    Signed-off-by: pradeep <psuriset@linux.vnet.ibm.com <mailto:psuriset@linux.vnet.ibm.com>>
>      >    modified:   ft_trans_file.c
>      >
>      > ---
>      >  ft_trans_file.c |    2 +-
>      >  1 files changed, 1 insertions(+), 1 deletions(-)
>      >
>      > diff --git a/ft_trans_file.c b/ft_trans_file.c
>      > index 4e33034..dc36757 100644
>      > --- a/ft_trans_file.c
>      > +++ b/ft_trans_file.c
>      > @@ -174,7 +174,7 @@ static int ft_trans_send_header(QEMUFileFtTrans *s,
>      >  static int ft_trans_put_buffer(void *opaque, const uint8_t *buf, int64_t pos, int size)
>      >  {
>      >      QEMUFileFtTrans *s = opaque;
>      > -    ssize_t ret;
>      > +    ssize_t ret = 0;
>      >
>      >      trace_ft_trans_put_buffer(size, pos);
>      >
>     --
>     To unsubscribe from this list: send the line "unsubscribe kvm" in
>     the body of a message to majordomo@vger.kernel.org <mailto:majordomo@vger.kernel.org>
>     More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>


-- 
大村 圭

NTTソフトウェアイノベーションセンタ
分散処理基盤技術プロジェクト
E-mail: ohmura.kei@lab.ntt.co.jp
TEL: 0422-59-2823
FAX: 0422-59-2965

  reply	other threads:[~2012-06-28 19:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111202125100.9872.75859.sendpatchset@skywalker>
2011-12-05  2:45 ` [KVM][Kemari]: Build error fix OHMURA Kei
2012-06-27 20:34   ` Sterling Windmill
2012-06-28 19:13     ` OHMURA Kei [this message]
2012-06-27 20:36   ` [Kemari]: " Sterling Windmill

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=4FECACE2.9080100@lab.ntt.co.jp \
    --to=ohmura.kei@lab.ntt.co.jp \
    --cc=kvm@vger.kernel.org \
    --cc=psuriset@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sterling@ampx.net \
    --cc=tamura.yoshiaki@gmail.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).