WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Strange interaction from grub2 and XEN

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Strange interaction from grub2 and XEN
From: Marco Nenciarini <mnencia@xxxxxxxxxxxxxx>
Date: Sun, 22 Nov 2009 11:27:55 +0100
Delivery-date: Sun, 22 Nov 2009 02:28:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla-Thunderbird 2.0.0.22 (X11/20091109)

I'm testing how xen and grub2 can work together.

I'm using xen 3.4.2 and grub2 1.97+20091115-1 from debian sid.

After many failed attempts I've discovered that on my system the first argument that grub2 should pass to the linux kernel is lost.

This is my working grub2 configuration:

menuentry "Xen 3.4.0 / Debian GNU/Linux, Linux 2.6.31-1-xen-amd64" {
    insmod xfs
    set root=(hd0,2)
    multiboot /boot/xen-3.4-amd64.gz
module /boot/vmlinuz-2.6.31-1-xen-amd64 dummy=dummy root=UUID=e9ed5af4-0503-4314-9d28-415a0eb7b0a0 ro quiet
    module /boot/initrd.img-2.6.31-1-xen-amd64
}

Looking in /proc/cmdline, there isn't any dummy=dummy argument

mnencia@manwe:/tmp$ cat /proc/cmdline
root=UUID=e9ed5af4-0503-4314-9d28-415a0eb7b0a0 ro quiet

Before the addition of dummy=dummy in front of line, the missing argument was the root=*, so my initrd had no idea of which root it have to mount.

BTW, the problem happens with both oldschool kernels and pvops ones.

I've googled around a bit, but I haven't found anything about this issue.

Kind regards,
Marco

--
---------------------------------------------------------------------
|    Marco Nenciarini    | Debian/GNU Linux Developer - Plug Member |
| mnencia@xxxxxxxxxxxxxx | http://www.prato.linux.it/~mnencia       |
---------------------------------------------------------------------
Key fingerprint = FED9 69C7 9E67 21F5 7D95  5270 6864 730D F095 E5E4


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users