Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-users

[Xen-users] Using pygrub

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Using pygrub
From: Steve Kemp <steve@xxxxxxxxxxxx>
Date: Thu, 28 Dec 2006 17:00:47 +0000
Delivery-date: Thu, 28 Dec 2006 09:00:40 -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
User-agent: Mutt/1.5.9i
  Having recently become aware of pygrub I've started using it.

  In general it works well, adding "bootloader = /path/to/pygrub" in
 the domU configuration and adding a simple menu.lst file to the
 domain's file system works.

  However arguments don't appear to be passed to the kernel.  With
 a menu.lst file such as this:

--
 title Xen 3.0 rescue
 kernel /boot/vmlinuz-2.6.16.33-xen root=/dev/sda1 init=/bin/sh
 initrd /boot/initrd.img-2.6.16.33-xen
--

  The system boots and the kernel ignores the "init=/bin/sh" argument
 completely.  Looking over the code I see mention of "args" but it 
 doesn't look like it is used as I'd expect.  The following fails too:

 args init=/bin/sh

  Is there a simple method of appending kernel arguments using pygrub?

Steve
-- 
http://www.steve.org.uk/

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

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