All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Chen" <chen.zhang@intel.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Daniel Cho <danielcho@qnap.com>,
	"lukasstraub2@web.de" <lukasstraub2@web.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: RE: Network connection with COLO VM
Date: Thu, 28 Nov 2019 01:26:50 +0000	[thread overview]
Message-ID: <9CFF81C0F6B98A43A459C9EDAD400D780631A02A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20191127105121.GA3017@work-vm>



> -----Original Message-----
> From: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Sent: Wednesday, November 27, 2019 6:51 PM
> To: Daniel Cho <danielcho@qnap.com>; Zhang, Chen
> <chen.zhang@intel.com>; lukasstraub2@web.de
> Cc: qemu-devel@nongnu.org
> Subject: Re: Network connection with COLO VM
> 
> * Daniel Cho (danielcho@qnap.com) wrote:
> > Hello everyone,
> >
> > Could we ssh to colo VM (means PVM & SVM are starting)?
> >
> 
> Lets cc in Zhang Chen and Lukas Straub.

Thanks Dave.

> 
> > SSH will connect to colo VM for a while, but it will disconnect with
> > error
> > *client_loop: send disconnect: Broken pipe*
> >
> > It seems to colo VM could not keep network session.
> >
> > Does it be a known issue?
> 
> That sounds like the COLO proxy is getting upset; it's supposed to compare
> packets sent by the primary and secondary and only send one to the outside
> - you shouldn't be talking directly to the guest, but always via the proxy.  See
> docs/colo-proxy.txt
> 

Hi Daniel,

I have try ssh to COLO guest with 8 hours, not occurred this issue.
Please check your network/qemu configuration.
But I found another problem maybe related this issue, if no network communication for a period of time(maybe 10min), the first message send to guest have a chance with delay(maybe 1-5 sec), I will try to fix it when I have time.

Thanks
Zhang Chen

> Dave
> 
> > Best Regard,
> > Daniel Cho
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK



  reply	other threads:[~2019-11-28  1:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27  4:20 Network connection with COLO VM Daniel Cho
2019-11-27 10:51 ` Dr. David Alan Gilbert
2019-11-28  1:26   ` Zhang, Chen [this message]
2019-11-29  2:42     ` Daniel Cho
2019-11-29 18:04       ` Zhang, Chen
2019-12-02  3:55         ` Daniel Cho
2019-12-02  9:58           ` Dr. David Alan Gilbert
2019-12-03  9:08             ` Daniel Cho
2019-12-03 13:25               ` Dr. David Alan Gilbert
2019-12-04  8:32                 ` Zhang, Chen
2019-12-06  6:31                   ` Daniel Cho

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=9CFF81C0F6B98A43A459C9EDAD400D780631A02A@shsmsx102.ccr.corp.intel.com \
    --to=chen.zhang@intel.com \
    --cc=danielcho@qnap.com \
    --cc=dgilbert@redhat.com \
    --cc=lukasstraub2@web.de \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.