This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH] fix pygrub domU grub.conf timeout=0 handling

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] fix pygrub domU grub.conf timeout=0 handling
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Wed, 19 Aug 2009 20:21:28 +0300
Delivery-date: Wed, 19 Aug 2009 10:21:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

When you install Fedora 11 PV domU/guest with virt-install or virt-manager,
it will have timeout=0 in it's grub.conf. This is a new default in F11.

pygrub of Xen 3.4.1 doesn't seem to be able to handle timeout=0, instead it
waits the user to press ENTER.. this causes confusion and makes it look
like the guest has crashed. Graphical VNC console is not yet available at
this point, so the kernel can be only chosen from "xm console <f11domain>",
where pygrub is waiting for user input.

This patch fixes the problem and let's you start F11 domUs without going to
the text console to select the kernel. The change is taken from the 
RHEL5.3 version of pygrub.

Patch is tested with Fedora 11 (timeout=0) and CentOS 5.3 (timeout=5) domUs.

-- Pasi

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>