All of lore.kernel.org
 help / color / mirror / Atom feed
From: INAKOSHI Hiroya <inakoshi.hiroya@jp.fujitsu.com>
To: xen-devel@lists.xensource.com
Subject: [Patch] Enable domU boot without xen specific arg by pygrub
Date: Mon, 09 Mar 2009 11:36:05 +0900	[thread overview]
Message-ID: <49B48095.9080808@jp.fujitsu.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 241 bytes --]

This patch makes domUs bring up without xen specific args to guest
kernels. A domU should be booted without args parameter because
tools/examples/xmexample1 doesn't have one.

Signed-off-by: INAKOSHI Hiroya <inakoshi.hiroya@jp.fujitsu.com>


[-- Attachment #2: pygrub_args.patch --]
[-- Type: text/plain, Size: 774 bytes --]

diff -r dd489125a2e7 tools/pygrub/src/pygrub
--- a/tools/pygrub/src/pygrub	Fri Mar 06 19:18:39 2009 +0000
+++ b/tools/pygrub/src/pygrub	Mon Mar 09 11:21:59 2009 +0900
@@ -605,7 +605,7 @@
     isconfig = False
 
     # what was passed in
-    incfg = { "kernel": None, "ramdisk": None, "args": None }
+    incfg = { "kernel": None, "ramdisk": None, "args": "" }
     # what grub or sniffing chose
     chosencfg = { "kernel": None, "ramdisk": None, "args": None }
     # what to boot
@@ -641,7 +641,7 @@
 
     # debug
     if isconfig:
-        chosencfg = run_grub(file, entry)
+        chosencfg = run_grub(file, entry, fs, incfg["args"])
         print "  kernel: %s" % chosencfg["kernel"]
         if img.initrd:
             print "  initrd: %s" % chosencfg["ramdisk"]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

                 reply	other threads:[~2009-03-09  2:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49B48095.9080808@jp.fujitsu.com \
    --to=inakoshi.hiroya@jp.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.