qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: Rene Rebe <rene@exactcode.de>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] Add multi-boot kernel loading support
Date: Tue, 03 Feb 2009 15:31:49 +0100	[thread overview]
Message-ID: <49885555.4020102@suse.de> (raw)
In-Reply-To: <49884D56.8000603@exactcode.de>

Rene Rebe schrieb:
> Hi,
> 
> Kevin Wolf wrote:
>> Rene Rebe schrieb:
>>> Hi all,
>>>
>>> Alexander Graf implemented multi-boot kernel loading during
>>> his work to run Darwin inside Qemu/KVM. As the boot loader
>>> expects to load the kernel in an EFI environment a custom
>>> booter is used to load the kernel using a legacy BIOS.
>>>
>>> This is a port of the patch to the new extload / INT 19
>>> machinery (including minor cleanups).
>>
>> The memory map doesn't seem to work. It's all zeros for me (haven't
>> looked for the reason yet) and that kills my kernel. When I disable the
>> memory map part, the kernel seems to boot correctly and it sees all the
>> modules with the right command lines.
>>
>> Once these basic things work, another nice feature would be gzip
>> support. It took me some minutes until I realized that I tried to feed
>> it a gzipped kernel which didn't work, of course.
> 
> I think I noticed the same with the GRUB example kernel. I'll
> take a look at some later hour.
> 
> Is your kernel something you can share for testing?

Sure. I tried it with with several homebrew kernels from
http://lowlevel.brainsware.org/wiki/index.php/Kategorie:Betriebssystem
(page is in German) - to be precise it was tyndur, meinOS, Xantorix and
lightOS. Links to the sources and/or binaries for each one are in the
respective Wiki articles.

I could also send you a tarball with all of them off-list if you like.

Kevin

  reply	other threads:[~2009-02-03 14:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 18:08 [Qemu-devel] [PATCH] Add multi-boot kernel loading support Rene Rebe
2009-02-02 18:15 ` Nathan Froyd
2009-02-02 18:17   ` Alexander Graf
2009-02-02 18:25     ` Nathan Froyd
2009-02-02 22:42 ` Anthony Liguori
2009-02-03  8:15   ` Rene Rebe
2009-02-03  8:23     ` Alexander Graf
2009-02-03  8:27       ` Rene Rebe
2009-02-03  8:25   ` Alexander Graf
2009-02-03  8:29     ` Rene Rebe
2009-02-03 10:53     ` Jamie Lokier
2009-02-03 11:12       ` Alexander Graf
2009-02-03 12:58 ` Kevin Wolf
2009-02-03 13:57   ` Rene Rebe
2009-02-03 14:31     ` Kevin Wolf [this message]
2009-02-04 10:36       ` Rene Rebe
2009-02-04 13:05         ` Kevin Wolf
2009-02-03 13:01 ` Paul Brook
2009-02-03 14:00   ` Rene Rebe

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=49885555.4020102@suse.de \
    --to=kwolf@suse.de \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=rene@exactcode.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).