qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <1044727@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1044727] Re: -kernel does not work for multiboot ELF kernels
Date: Tue, 04 Sep 2012 14:51:45 -0000	[thread overview]
Message-ID: <20120904145145.29136.5786.malone@wampee.canonical.com> (raw)
In-Reply-To: 20120901144552.17769.85775.malonedeb@wampee.canonical.com

Henning, please submit your patch to the qemu-devel mailing list. See
http://wiki.qemu.org/Contribute/SubmitAPatch for more details on how
patch submission works for qemu.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1044727

Title:
  -kernel does not work for multiboot ELF kernels

Status in QEMU:
  New

Bug description:
  The multiboot header of a kernel image can contain the entry point and
  memory segment information. If it does not the kernel should have an
  ELF header that describes the memory segments and contains the entry
  point.

  http://www.gnu.org/software/grub/manual/multiboot/multiboot.html
  #Header-layout

  I have such a multiboot ELF kernel that can be loaded fine with grub
  and grub2 but not with the qemu -kernel flag. According to the ELF
  spec the entry field in the ELF header should contain the virtual
  address of the multiboot entry code. Qemu sets up the memory regions
  using the paddr fields from the ELF sections and then tries to start
  the kernel using the virtual entry address. This will fail with

  >> qemu: fatal: Trying to execute code outside RAM or ROM

  I wrote a simple kernel that can be used to reproduce this bug. Get
  this archive

  http://os.inf.tu-dresden.de/~hschild/asmkernel.tar.gz

  It contains the simple kernel, its source, plus grub and grub2
  binaries to boot the kernel in qemu. The HOWTO file contains the
  command lines you should be using to rebuild the kernel and boot it an
  bare qemu or with one of the two bootloaders.

  Find a patch that will fix this issue here:
  http://os.inf.tu-dresden.de/~hschild/qemu-fix-elf-entry.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1044727/+subscriptions

  reply	other threads:[~2012-09-04 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-01 14:45 [Qemu-devel] [Bug 1044727] [NEW] -kernel does not work for multiboot ELF kernels Henning Schild
2012-09-04 14:51 ` Kevin Wolf [this message]
2012-09-07 14:24 ` [Qemu-devel] [Bug 1044727] " Aurelien Jarno
2013-05-20 17:35 ` Aurelien Jarno

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=20120904145145.29136.5786.malone@wampee.canonical.com \
    --to=1044727@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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 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).