This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] xen.git branch reorg

To: bderzhavets@xxxxxxxxx
Subject: Re: [Xen-devel] xen.git branch reorg
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Fri, 24 Apr 2009 11:17:50 -0700
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 24 Apr 2009 11:18:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <643338.55074.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <643338.55074.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090320)
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 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?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>