qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: OHMURA Kei <ohmura.kei@lab.ntt.co.jp>
To: Pradeep Kumar <psuriset@linux.vnet.ibm.com>
Cc: tamura.yoshiaki@gmail.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [KVM][Kemari]: Build error fix
Date: Mon, 05 Dec 2011 11:45:31 +0900	[thread overview]
Message-ID: <4EDC304B.1030407@lab.ntt.co.jp> (raw)
In-Reply-To: <20111202125100.9872.75859.sendpatchset@skywalker>

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 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>
>    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);
>

           reply	other threads:[~2011-12-05  2:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20111202125100.9872.75859.sendpatchset@skywalker>]

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=4EDC304B.1030407@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=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).