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


Re: [Xen-devel] Re: [Xen-users] Strange interaction from grub2 and XEN

To: Marco Nenciarini <mnencia@xxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] Strange interaction from grub2 and XEN
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 24 Nov 2009 17:11:09 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 24 Nov 2009 09:11:35 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B0AB64A.1010306@xxxxxxxxxxxxxx>
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
Thread-index: AcptI4dlEuMLC8flQt+XmHf+c0ye3gABZYjY
Thread-topic: [Xen-devel] Re: [Xen-users] Strange interaction from grub2 and XEN
User-agent: Microsoft-Entourage/
On 23/11/2009 16:20, "Marco Nenciarini" <mnencia@xxxxxxxxxxxxxx> wrote:

>> I'm looking for a real solution, as find where is the problem and a
>> proper correction, or a rationale that explain what I'm doing wrong.
> I finally found the the root cause of this issue on grub-devel mailing list.
> http://lists.gnu.org/archive/html/grub-devel/2009-08/msg00001.html
> Now I wonder if there is any chance to make the xen hypervisor aware of
> this behavior change in grub2.

So they've stopped passing the kernel name as a first element of the command
line, but haven't allocated a new flag or anything to indicate that new
behaviour? What are we supposed to do to detect it and act on it?

 -- Keir

Xen-devel mailing list

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