From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: [PATCH] fix pygrub domU grub.conf timeout=0 handling Date: Thu, 20 Aug 2009 11:12:22 +0300 Message-ID: <20090820081222.GP19938@edu.joroinen.fi> References: <20090819172708.GG19938@edu.joroinen.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline 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" List-Id: xen-devel@lists.xenproject.org On Thu, Aug 20, 2009 at 08:32:34AM +0100, Keir Fraser wrote: > On 19/08/2009 18:27, "Pasi K=E4rkk=E4inen" wrote: >=20 > >> pygrub of Xen 3.4.1 doesn't seem to be able to handle timeout=3D0, i= nstead it > >> waits the user to press ENTER.. this causes confusion and makes it l= ook > >> like the guest has crashed. Graphical VNC console is not yet availab= le at > >> this point, so the kernel can be only chosen from "xm console ", > >> where pygrub is waiting for user input. > >>=20 > >> This patch fixes the problem and let's you start F11 domUs without g= oing to > >> the text console to select the kernel. The change is taken from the > >> RHEL5.3 version of pygrub. > >>=20 > >> Patch is tested with Fedora 11 (timeout=3D0) and CentOS 5.3 (timeout= =3D5) domUs. > >>=20 > >=20 > > And actually attached this time. >=20 > Really this is a reversion of c/s 19322, which was a dodgy bugfix for > Solaris. So I just checked it in as a reversion. >=20 Thanks! -- Pasi