From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Derzhavets Subject: Re: xen.git branch reorg Date: Fri, 24 Apr 2009 03:33:41 -0700 (PDT) Message-ID: <643338.55074.qm@web56104.mail.re3.yahoo.com> References: <20090423182451.GV24960@edu.joroinen.fi> Reply-To: bderzhavets@yahoo.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1110229538==" Return-path: In-Reply-To: <20090423182451.GV24960@edu.joroinen.fi> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge , =?iso-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org --===============1110229538== Content-Type: multipart/alternative; boundary="0-577380358-1240569221=:55074" --0-577380358-1240569221=:55074 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Kernel been built based on xen-tip/next=A0 appears to have name 2.6.30-rc2-= tip and behaves under Xen 3.4-rc2-pre as usual. No problems were noticed with P= V DomUs for=A0 =A0CentOS 5.3, F10, Ubuntu Server 9.04. However,=A0remote VNC connec= tion to Ubuntu Server=A09.04=A0PV 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 A= SAP.=20 I also have to notice that remote=A0VNC connection to Ubuntu=A09.04 DomU ru= nning at the=A0 same Xen 3.4 version Dom0 with Suse's 2.6.27.5 xen-ified kernel behaves jus= t fine. IP6v connection via vinagre (for Ubuntu Server 9.04 DomU)=A0behaves exactly= same way as old fashioned. No problems when been established from Dom0 and= almost dead remotely. =A0 Boris. --- On Thu, 4/23/09, Pasi K=E4rkk=E4inen wrote: From: Pasi K=E4rkk=E4inen Subject: Re: [Xen-devel] xen.git branch reorg To: "Jeremy Fitzhardinge" Cc: "Xen-devel" 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=20 > with the long-threatened xen.git cleanup and reorg. >=20 > The new branch structure is similar to the old one in overall layout. =20 > There are two "merged" branches: >=20 > * 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 >=20 I'll try upgrading from dom0/hackery to xen-tip/next and see how it works for me.=20 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?=20 -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel =0A=0A=0A --0-577380358-1240569221=:55074 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Kernel been built based on xen-tip/next&= nbsp; appears to have name 2.6.30-rc2-tip
and behaves under Xen 3.4-rc2-pre as usual. No problems were noticed w= ith PV DomUs
for   CentOS 5.3, F10, Ubuntu Server 9.04. However, rem= ote VNC connection to Ubuntu
Server 9.04 PV DomU seems to be extrtemely slow. VNC connect= ion to same DomU
from Dom0 runs fine. I'll try to test this issue for CentOS and F10 Do= mUs 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 behave= s 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.
 
Boris.


--- On Thu, 4/23/09, Pasi K=E4rkk=E4inen <pasik@iki.f= i> wrote:
From: Pasi K=E4rkk=E4inen <pasik@iki.fi>
Sub= ject: Re: [Xen-devel] xen.git branch reorg
To: "Jeremy Fitzhardinge" <= ;jeremy@goop.org>
Cc: "Xen-devel" <xen-devel@lists.xensource.com&g= t;
Date: Thursday, April 23, 2009, 2:24 PM

On Thu, Apr 23, 2=
009 at 10:38:31AM -0700, Jeremy Fitzhardinge wrote:
> I finally fixed the AHCI problem with xen-tip/next and pushed forward=
=20
> with the long-threatened xen.git cleanup and reorg.
>=20
> The new branch structure is similar to the old one in overall layout. =
=20
> There are two "merged" branches:
>=20
>    * 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
>=20

I'll try upgrading from dom0/hackery to xen-tip/next and see how it works
for me.=20

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?=20

-- Pasi

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

=0A=0A=0A=0A --0-577380358-1240569221=:55074-- --===============1110229538== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1110229538==--