Public bug reported:
I think that I have found a bug in qemu 0.13.0 and 0.14.0. I am
developing an own microkernel and use the Multiboot specification. I
load the kernel and its initrd directly with the flags "-kernel" and
"-initrd". With qemu 0.12.5, my code works correctly and I have access
to my initrd. By using qemu 0.13.0 or 0.14.0, my code crashes. In this
case, the physical address of the module structure (mods_addr) points
directly to the first loaded module (in my case to 0x272000). This is in
my opinion wrong. Like qemu 0.12.5, is has to point to an array (in my
case to address 0x9600), which contains the start (0x272000) and the end
address of each loaded module. Or did I misunderstand the multiboot
specification
(http://www.gnu.org/software/grub/manual/multiboot/multiboot.html#Boot-
information-format)?
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/740014
Title:
The Multiboot information data structure contains the wrong address to
the module structure
Status in QEMU:
New
Bug description:
I think that I have found a bug in qemu 0.13.0 and 0.14.0. I am
developing an own microkernel and use the Multiboot specification. I
load the kernel and its initrd directly with the flags "-kernel" and
"-initrd". With qemu 0.12.5, my code works correctly and I have access
to my initrd. By using qemu 0.13.0 or 0.14.0, my code crashes. In this
case, the physical address of the module structure (mods_addr) points
directly to the first loaded module (in my case to 0x272000). This is
in my opinion wrong. Like qemu 0.12.5, is has to point to an array (in
my case to address 0x9600), which contains the start (0x272000) and
the end address of each loaded module. Or did I misunderstand the
multiboot specification
(http://www.gnu.org/software/grub/manual/multiboot/multiboot.html
#Boot-information-format)?
