From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Burns Subject: Re: Re: F16, yum install xen, run grub2 or grubby as needed? Date: Thu, 22 Sep 2011 02:28:20 +0100 Message-ID: References: <20110915154621.GA21580@phenom.oracle.com> <20110916083533.GC884@phenom.oracle.com> <20110921180819.GE17357@phenom.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <20110921180819.GE17357@phenom.oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 21 September 2011 19:08, Konrad Rzeszutek Wilk wrote: > Oh, well, that is kind of convient. So you install new kernel and viola the new kernel boots in the hypervisor kernel? The way I achieved that, is to edit /etc/default/grub to include GRUB_DEFAULT="Xen" which matches the submenu created by /etc/grub.d/20_linux_xen so the submenu is the default chosen, and the newest kernel is automatically chosen from the top item of the submenu. I suspect there are still flies in the ointment with that, which was when I started to notice that installing a kernel had messed with the /boot/grub2/grub.cfg file If my server was in the remote data centre rather than the next room, I wouldn't be confident about rebooting it and expecting it to run the right combination of xen+kernel.