: Build error fix
A message that is not in the archive (sent off-list or not yet received): 20111202125100.9872.75859.sendpatchset@skywalker
Quoted 11 lines · Pradeep Kumar
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_beginfailed
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
Quoted 26 lines
Any one working on this now?
Quoted 1 line
From
827c04da6574be80d8352acd7c40b0b4524af5f4Mon Sep 17 00:00:00 2001Date: Fri, 2 Dec 2011 18:11:40 +0530
Subject: [PATCH] [Qemu][Kemari]: Build FailureSigned-off-by pradeep <[email protected]>modified:
ft_trans_file.c--- ft_trans_file.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)ft_trans_file.c +1
-1@@ -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);
Is Kemari still in active development?
Best regards,
Sterling Windmill
Quoted 53 lines · OHMURA Kei
Quoted 11 lines · Pradeep Kumar
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_beginfailedDid you use master branch?
It is not latest version. next branch is latest and fixed error.
git://kemari.git.sourceforge.net/gitroot/kemari/kemarinextThanks,
KeiQuoted 18 lines
Any one working on this now?
Quoted 1 line
From
827c04da6574be80d8352acd7c40b0b4524af5f4Mon Sep 17 00:00:00 2001Date: Fri, 2 Dec 2011 18:11:40 +0530
Subject: [PATCH] [Qemu][Kemari]: Build FailureSigned-off-by pradeep <[email protected]>modified:
ft_trans_file.c--- ft_trans_file.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)ft_trans_file.c +0
-0ft_trans_file.c static int ft_trans_send_header(QEMUFileFtTrans *s, · line 174
Quoted 1 line
ft_trans_file.c +0
-0@@ -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_tpos, int size)ft_trans_file.c static int ft_trans_send_header(QEMUFileFtTrans *s, · line 180
Quoted 7 lines
ft_trans_file.c +1
-1{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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 1 line · Sterling Windmill
Is Kemari still in active development?
No, it's not. Currently we have no intention to add new features into Kemari.
Thanks,
Kei
Quoted 59 lines
Best regards,
Sterling WindmillOn Sun, Dec 4, 2011 at 9:45 PM, OHMURA Kei <[email protected] <mailto:[email protected]>> 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 <[email protected] <mailto:[email protected]>> > 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 [email protected] <mailto:[email protected]> More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 7 lines
大村 圭 NTTソフトウェアイノベーションセンタ 分散処理基盤技術プロジェクト E-mail: [email protected] TEL: 0422-59-2823 FAX: 0422-59-2965
Is Kemari still in active development?
Quoted 51 lines · OHMURA Kei
Quoted 11 lines · Pradeep Kumar
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_beginfailedDid you use master branch?
It is not latest version. next branch is latest and fixed error.
git://kemari.git.sourceforge.net/gitroot/kemari/kemarinextThanks,
KeiQuoted 18 lines
Any one working on this now?
Quoted 1 line
From
827c04da6574be80d8352acd7c40b0b4524af5f4Mon Sep 17 00:00:00 2001Date: Fri, 2 Dec 2011 18:11:40 +0530
Subject: [PATCH] [Qemu][Kemari]: Build FailureSigned-off-by pradeep <[email protected]>modified:
ft_trans_file.c---
ft_trans_file.c | 2 +-1 files changed, 1 insertions(+), 1 deletions(-)ft_trans_file.c +0
-0ft_trans_file.c static int ft_trans_send_header(QEMUFileFtTrans *s, · line 180
Quoted 8 lines
ft_trans_file.c +1
-1@@ -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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html