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-users] Where does xen chache domUs grub.conf ?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Where does xen chache domUs grub.conf ?
From: Alain BARTHE <alain.barthe@xxxxxxxx>
Date: Tue, 11 Dec 2007 11:08:22 +0100
Delivery-date: Tue, 11 Dec 2007 02:09:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Hi all, I'm a newbie on this list. I'm using xen 3.0.3 on CentOS50.

I installed a new flavor of kernel in a domU via a standard RPM, which modified my grub.conf by adding a new entry to boot on the new kernel. When rebooting the domU by pygrub, I didn't see the new grub entry. I tried to restart xend, with no effect.
By googling a little, I understood that kernel files used by a domU must be present on the dom0, and it was considered as a bug. So I copied those files from the domU to the dom0... with no more effect.

By rebooting the dom0, the new entry appeared and I be able to start my domU with its new kernel. I tried to remove the domU kernel files I copied before on the dom0, and the domU continues to boot normally. So I misunderstood what google said me before.

I suppose that xen caches domU's grub.conf somewhere on the dom0. My question is: where ?

Thank you for answers.

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>