All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: pvgrub2 legacy_configfile issues: /sbin/init exec error -8
Date: Sat, 11 Feb 2017 17:19:34 +0000	[thread overview]
Message-ID: <20170211171934.GJ1804@bitfolk.com> (raw)
In-Reply-To: <20170211152643.GH1804@bitfolk.com>

Hello,

On Sat, Feb 11, 2017 at 03:26:43PM +0000, Andy Smith wrote:
> Here is what the config looks like if I interrupt the boot and go to
> edit it:
> 
> set root='(hd0,1)'; set legacy_hdbias='0'
> legacy_kernel   '/boot/vmlinuz-3.16.0-4-amd64' '/boot/vmlinuz-3.16.0-4-amd64' 'root=UUID=38420e46-6123-477d-ba23-baeba8ac0d59' 'ro'
> legacy_initrd '/boot/initrd.img-3.16.0-4-amd64' '/boot/initrd.img-3.16.0-4-amd64'

Over on the xen-users list, Sarah Newman pointed out that the
legacy_initrd line should not have a repeated argument:

    https://lists.xenproject.org/archives/html/xen-users/2017-02/msg00029.html

If I edit away the repetition, so that the config line is:

legacy_initrd '/boot/initrd.img-3.16.0-4-amd64'

then this boots fine.

Should I report this in grub's bugzilla?

Thanks,
Andy


  reply	other threads:[~2017-02-11 17:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11 13:53 pvgrub2 legacy_configfile issues: /sbin/init exec error -8 Andy Smith
2017-02-11 14:46 ` Andrei Borzenkov
2017-02-11 15:26   ` Andy Smith
2017-02-11 17:19     ` Andy Smith [this message]
2017-02-11 18:45       ` Andrei Borzenkov
2017-02-11 21:07         ` Vladimir 'phcoder' Serbinenko
2017-02-11 23:36           ` Vladimir 'phcoder' Serbinenko
2017-02-12  7:06           ` Andrei Borzenkov
2017-02-12 10:52             ` Vladimir 'phcoder' Serbinenko
2017-02-24 23:22               ` Vladimir 'phcoder' Serbinenko
2017-02-25  5:27                 ` Andrei Borzenkov
2017-02-25 12:19                   ` Andy Smith

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=20170211171934.GJ1804@bitfolk.com \
    --to=andy@strugglers.net \
    --cc=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    /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.