From mboxrd@z Thu Jan 1 00:00:00 1970 From: William Pitcock Subject: Re: xen.git branch reorg Date: Tue, 28 Apr 2009 02:13:16 -0500 Message-ID: <1240902796.10269.81.camel@petrie> References: <49F0A797.1050402@goop.org> <1240709312.26370.32.camel@petrie> <49F61A85.9030505@goop.org> <1240866446.10269.65.camel@petrie> <49F64460.4070001@goop.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49F64460.4070001@goop.org> 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 Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org On Mon, 2009-04-27 at 16:48 -0700, Jeremy Fitzhardinge wrote: > William Pitcock wrote: > > Yeah, it's working here now. Thanks for that. > > > > We intend to start testing the 3.4 release candidate with 2.6.30 > > paravirt-ops dom0 in our test environment this weekend. > > > > OK, that'll be interesting. What's your test environment? Paravirtualization-only nocona-based (early EM64T) Xeon hardware, with nodes comprising of dual 2.8ghz CPUs with 8GB of memory, on Debian testing. Production is presently at 3.2 with XenLinux 2.6.18 patches rebased against 2.6.26. Production machines are dual opteron 2216 machines with 8GB-16GB of RAM, with both HVM and Paravirtualized domains. The test and production grids use the same storage backend, which is presently provided through exporting LVM volumes with AoE and cluster-lvm. I could pull a spare server out of the production grid for testing HVM under 2.6.30 if needed. William