From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: xen.git branch reorg Date: Fri, 24 Apr 2009 11:17:50 -0700 Message-ID: <49F2024E.5000507@goop.org> References: <643338.55074.qm@web56104.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <643338.55074.qm@web56104.mail.re3.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: bderzhavets@yahoo.com Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org Boris Derzhavets wrote: > Kernel been built based on xen-tip/next appears to have name > 2.6.30-rc2-tip > and behaves under Xen 3.4-rc2-pre as usual. No problems were noticed > with PV DomUs > for CentOS 5.3, F10, Ubuntu Server 9.04. However, remote VNC > connection to Ubuntu > Server 9.04 PV DomU seems to be extrtemely slow. VNC connection to > same DomU > from Dom0 runs fine. I'll try to test this issue for CentOS and F10 > DomUs ASAP. > I also have to notice that remote VNC connection to Ubuntu 9.04 DomU > running at the > same Xen 3.4 version Dom0 with Suse's 2.6.27.5 xen-ified kernel > behaves just fine. > IP6v connection via vinagre (for Ubuntu Server 9.04 DomU) behaves > exactly same way as old fashioned. No problems when been established > from Dom0 and almost dead remotely. > Is it always consistent with the same kernel, or does it change from boot to boot? Could you try to work out what's actually failing with tcpdump/wireshark, both from within the domU, and from dom0? Are packets getting lost on tx or rx, or very delayed, or something else? Thanks, J