I guess the question is, should i be using i386-qemu? For kicks i just
built a image using
./grub-mkstandalone -O i386-qemu -o grub2.img boot/grub/grub.cfg -d
grub-core
and qemu will use it, however when i connect to the VNC console all i
see is a bunch of colorful giberish.
--
Shaun
------ Original Message ------
From: "Andrei Borzenkov" <[email protected]>
To: "Shaun Reitan" <[email protected]>; "[email protected]"
<[email protected]>
Sent: 2017-02-02 12:01:58 AM
Subject: Re: Building grub2 for use as a kernel on qemu
On Thu, Feb 2, 2017 at 6:25 AM, Andrei Borzenkov <[email protected]>
wrote:
...
grub-mkimage -O i386-pc -c grub.cfg -o grub2.img at_keyboard
configfile
biosdisk ext2 linux serial halt minicmd terminal all_video cat echo
gzio
search linux16 normal disk test true fat memdisk tar ls sleep -p
/usr/src/grub/grub-core/
...
Use grub-mkstandalone to create image that includes internal memory
disk
and place your config on this memory disk. Do not include your
modules
in image itself. By default grub-mkstandalone adds all available
modules; if size is an issue (but this is really a couple of
megabytes,
so I do not expect it), you can restrict module list and other
components - see help output.
Sorry, missed that you use i386-pc platform, not i386-qemu. Then size
of boot image does matter, you may want to at least exclude themes and
translations (if any). Full standalone image that includes all bells
and whistles for GUI boot does not fit in available memory on this
platform.
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub
