GRUB2 fails to load kernel in bochs and VirtualBox
Posted: Mon Dec 23, 2013 10:41 am
Hello,
I am using GRUB2 to boot my kernel, and this always works in qemu. But when I use bochs or VirtualBox, it only works if its built for x86. If I build it for x86_64, it doesn't successfully load the kernel.
Using `debug=all` this is what GRUB2 stalls at:
And the last lines of output from bochs:
Does anyone know what is happening/if I did anything wrong? I will provide boot code if needed, but it SEEMS as if it doesn't even make it to that point at all.
Any help on this problem would be greatly appreciated.
I am using GRUB2 to boot my kernel, and this always works in qemu. But when I use bochs or VirtualBox, it only works if its built for x86. If I build it for x86_64, it doesn't successfully load the kernel.
Using `debug=all` this is what GRUB2 stalls at:
Code: Select all
kern/dl.c:619: module name: relocator
kern/dl.c:620: init function: 0x0
kern/disk.c:196: Opening `hd96'...
kern/fs.c:56: Detecting iso9660...
kern/disk.c:295: Closing `hd96'.
kern/dl.c:572: module at 0x1f6db30, size 0x8e8
kern/dl.c:596: relocating to 0x1f6ebc0
kern/dl.c:560: flushing 0x6fe bytes at 0x1f6e490
kern/dl.c:619: module name: lsapm
kern/dl.c:620: init function: 0x1f6e664
kern/disk.c:196: Opening `hd96'...
kern/fs.c:56: Detecting iso9660...
kern/disk.c:295: Closing `hd96'.
kern/dl.c:572: module at 0x1f6b0f0, size 0x26d0
kern/dl.c:596: relocating to 0x1f6e3f0
kern/dl.c:560: flushing 0x24bb bytes at 0x1f52890
kern/dl.c:619: module name: acpi
kern/dl.c:620: init function: 0x1f53862
kern/dl.c:560: flushing 0x31cf bytes at 0x1f6a5f0
kern/dl.c:619: module name: multiboot2
kern/dl.c:620: init function: 0x1f6b184
kern/disk.c:196: Opening `hd96'...
kern/fs.c:56: Detecting iso9660...
lib/relocator.c:115: relocators_size=7Code: Select all
00017896941i[BIOS ] Booting from 07c0:0000
00017905792i[MEM0 ] allocate_block: block=0x1 used 0x3 of 0x20
00048688780i[MEM0 ] allocate_block: block=0x1e used 0x4 of 0x20Any help on this problem would be greatly appreciated.