From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0 Date: Wed, 09 Jun 2010 11:16:27 -0700 Message-ID: <4C0FDA7B.8040101@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" , Boris Derzhavets , =?ISO-8859-1?Q?Paul_K=F6l?=, =?ISO-8859-1?Q?le?= , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 06/09/2010 05:02 AM, Keir Fraser wrote: > On 09/06/2010 12:15, "Boris Derzhavets" wrote: > > >> Via my experience in meantime Xen 4.0 official release doesn't have either >> origin/xen/stable or origin/xen/stable-2.6.32.x branch generating kernel >> supporting it's Dom0. >> > We'll get a 4.0.1 release out by end of the month. The next 3.4 release is > further out, but I don't think many users of that branch are going to be > flirting with pv_ops dom0. If they are, they can always upgrade to 4.0 > branch. > Things are pretty bad in the meantime, if they use a pvops kernel. Maybe I should create a specific xen 4.0.0 branch? Any chance of a hotfix for just this particular issue? J