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: Wed, 04 Feb 2009 14:05:24 +0100	[thread overview]
Message-ID: <49899294.5060507@suse.de> (raw)
In-Reply-To: <5C0CBE70-6FE4-4756-B1D1-0B8D7D83D9E8@exactcode.de>

Rene Rebe schrieb:
>>> 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.
> 
> From reading the last mails I thought you would have your own kernel.

Well, I didn't say that I'm not involved in one of these. tyndur is the
one, even if the broken multiboot patch proved that there is room for
improvement in the error handling. (*cough* Triple fault... ;-))

> I now have the mmap, memory sizes (kB, not Bytes) fixed and some
> other comments from the list taken into account (ARRAY_SIZE, etc.).
> 
>  
> http://svn.exactcode.de/t2/trunk/package/emulators/kvm/09-qemu-multiboot.patch
> 
> 
> As I did not yet feel like extracting all the kernels and their modules
> from the cited disk / floppy images so it's not yet tested with those
> "homebrew" kernels.

Looks much better now. Not all systems complete the boot (I would
suspect the OSes to be buggy here though), but no horrible crashes any more.

Well, except that with the lightOS kernel I still managed to get a qemu
segfault in the fread in pc.c:939 when loading a module, and other
modules failed to load ("read error on multiboot module abc (0 != x)").
Interestingly the same modules are loaded without any problem if I use a
different kernel. I guess we'd better fix that before committing.

Kevin

  reply	other threads:[~2009-02-04 12:58 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
2009-02-04 10:36       ` Rene Rebe
2009-02-04 13:05         ` Kevin Wolf [this message]
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=49899294.5060507@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).