From: Andrey Borzenkov <arvidjaar@gmail.com>
To: Beeblebrox <zaphod@berentweb.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: PXE-Grub has no menu - File not found
Date: Fri, 27 Jun 2014 20:08:26 +0400 [thread overview]
Message-ID: <20140627200826.6b9ab414@opensuse.site> (raw)
In-Reply-To: <20140627092605.38ea0961@rsbsd.rsb>
В Fri, 27 Jun 2014 09:26:05 +0300
Beeblebrox <zaphod@berentweb.com> пишет:
>
> > How did you create your netboot directory and grub image? Your grub
> > requests /boot/grub/i386-pc/normal.mod, *NOT* grub/i386-pc/normal.mod.
> > It has wrong prefix.
>
> my tftp & dhcp are running in a jail (consider it like a VM) and the
> jail(VM)'s root (data/amd64) is NFS exported so that it can be mounted
> as " / ro ".
>
> My settings for tftp & dhcp:
> tftp: -s /boot
> dhcp for Grub: filename "grub/i386-pc/core.0";
> dhcp for btx: filename "pxeboot";
>
> As far as boot sequence goes, the tftp + dhcp combined path as
> "/boot/grub/i386-pc/core.0" should be correct?
This path should be accessible by your tftp server. It is unlikely that
both paths are correct.
> Netboot dir made as:
> cd /data/amd64 && grub-mknetdir --net-directory=./
>
How /data/amd64 is related to /boot which is your tftp root?
grub-mknetdir should have printed exact instructions how you need to
configure your boot server; but it assumes that --net-directory points
to your tftp server root.
next prev parent reply other threads:[~2014-06-27 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 18:11 PXE-Grub has no menu - File not found Beeblebrox
2014-06-08 5:22 ` Andrey Borzenkov
2014-06-09 5:20 ` Beeblebrox
2014-06-23 19:39 ` Beeblebrox
2014-06-24 15:19 ` Beeblebrox
2014-06-25 17:36 ` Andrey Borzenkov
2014-06-26 15:58 ` Andrey Borzenkov
2014-06-27 6:26 ` Beeblebrox
2014-06-27 16:08 ` Andrey Borzenkov [this message]
2014-07-02 6:24 ` Beeblebrox
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=20140627200826.6b9ab414@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=zaphod@berentweb.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.