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 188.8.131.52 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.
--- On Thu, 4/23/09, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] xen.git branch reorg
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Thursday, April 23, 2009, 2:24 PM
On Thu, Apr 23, 2009 at 10:38:31AM -0700, Jeremy Fitzhardinge wrote:
> I finally fixed the AHCI problem with xen-tip/next and pushed forward
> with the long-threatened xen.git cleanup and reorg.
> The new branch structure is similar to the old one in overall layout.
> There are two "merged" branches:
> * xen-tip/master - will try to keep as a known-working branch, with
> only tested changes
> * xen-tip/next - current bleeding edge; should at least compile
I'll try upgrading from dom0/hackery to xen-tip/next and see how it works
Btw how does dom0 upstreaming look at the moment? Ingo sent pull request
about some changes, and those got merged, but how about the rest?
Xen-devel mailing list