All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH][TRIVIAL] Improve friendliness of misconfigured bootloader error
Date: Wed, 22 Jun 2005 22:37:44 -0500	[thread overview]
Message-ID: <42BA2E88.9010906@us.ibm.com> (raw)

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

If a user specifies an improper grub.conf entry for Xen (does not 
specify a module line or mispells module), Xen outputs the following error:

   FATAL ERROR: Require at least one Multiboot module.

The attached patch changes this error to:

   FATAL ERROR: dom0 kernel not specified! Check bootloader configuration.

I've had a few people ask for help debugging this problem and usually 
they have no idea what a multiboot module is so the error is not helpful 
to them.

Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>

Regards,

Anthony Liguori

[-- Attachment #2: nicer_startup_msg.diff --]
[-- Type: text/x-patch, Size: 477 bytes --]

--- xen/arch/x86/setup.c~	2005-06-22 14:45:43.000000000 -0500
+++ xen/arch/x86/setup.c	2005-06-22 22:33:13.331925064 -0500
@@ -262,7 +262,7 @@
     /* Check that we have at least one Multiboot module. */
     if ( !(mbi->flags & MBI_MODULES) || (mbi->mods_count == 0) )
     {
-        printk("FATAL ERROR: Require at least one Multiboot module.\n");
+        printk("FATAL ERROR: dom0 kernel not specified! Check bootloader configuration.\n");
         EARLY_FAIL();
     }
 

[-- 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:[~2005-06-23  3:37 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=42BA2E88.9010906@us.ibm.com \
    --to=aliguori@us.ibm.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.