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] RE: Failure to start Xen >3.4.1 and xen-3.5-unstable Dom0 us

To: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: Failure to start Xen >3.4.1 and xen-3.5-unstable Dom0 using GRUB2
From: Tim Moore <timothy.moore@xxxxxxxxxxx>
Date: Sun, 30 Aug 2009 19:14:59 +0100
Accept-language: en-US, en-GB
Acceptlanguage: en-US, en-GB
Cc: 'Christian Tramnitz' <chris.ace@xxxxxxx>
Delivery-date: Sun, 30 Aug 2009 11:16:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <h7dum6$flm$1@xxxxxxxxxxxxx>
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>
References: <367788.24971.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <809484.90887.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <h7dum6$flm$1@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcopdZUYDT1cjHbqQxyh3J9R/OxU4wAApZ6A
Thread-topic: RE: Failure to start Xen >3.4.1 and xen-3.5-unstable Dom0 using GRUB2
Hi Christian/All,

I have a similar issue with GRUB2 .. I was using grub-legacy for a while, until 
I switched to using XCI (Xen Client Initiative) which comes as standard with a 
GRUB2. (no option for alternative, as XCI uses LVM so must use GRUB2)

Then I also try GRUB2 multiboot with latest xen-unstable/pvops and received the 
attached error .. (jpg)
"Cannot access memory beyond the end of bootstrap direct-map area"

Therefore I have switched back to grub-legacy (0.97) and xen-unstable/pvops 
boots fine !

ATMO I am unable to boot XCI as grub-legacy does not support LVM - I am now 
looking to chainload GRUB>GRUB2 to enable me to start XCI.

With earlier version of xen-unstable, I was able to boot successfully. There 
has been a change in XEN that has broken compatibility with the (incomplete) 
GRUB2 multiboot specification. I would therefore say that GRUB2 needs the 
bugfix, but its XEN that actually broke compatibility.


-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Christian Tramnitz
Sent: 30 August 2009 14:26
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: Failure to setup Xen 3.4.1 Dom0 on top of Ubuntu 9.10 
Server HVM DomU ( xenified kernel)

Afaik grub2 does not pass the boot parameters "root=/dev/sda2 ro 
console=tty0" to the kernel in multiboot/module combination. I have seen 
the same problem on gentoo/grub2 and also read about this before. (This 
is not really Xen specific, but multiboot related).
My workaround was to compile the kernel options as static cmdline into 
the kernel itself...

Best regards,

Boris Derzhavets wrote:
> Karmic Server HVM DomU setup at Xen 3.4.1 Dom0 F11 via virt-install.
> Attempt to build Xen from source and xenified kernel succeeded.
> Before creating Grub 2 entry for Xen Host directive "root=UUID=.."  
> switched off by editing /etc/default/grub and update-grub run.
> Manually created entry /boot/grub/grib.cfg as advised for Debian (Grub 2)
>  Xen 3.4.1 Ubuntu 9.10 {
> multiboot (hd0,1)/xen-3.4.gz
> module    (hd0,1)/vmlinuz- root=/dev/sda2 ro console=tty0
> module    (hd0,1)/initrd-
> }
> Failure when waiting for /dev/sda2 and dropping to grub prompt
> HVM itself loads fine.
> Boris.

Xen-devel mailing list

Attachment: boot_with_grub2.jpg
Description: boot_with_grub2.jpg

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