Hello! I am very interested in your work with Fractal and have been trying to set it up. I am encountering an issue where the OS crashes immediately upon boot when using the GRUB ISO method described in the README. I have tested this across multiple hypervisors and host systems with the exact same result.
Environment
Host OS: Kali Linux and Windows
Hypervisors Tested: QEMU, VirtualBox, VMWare
Target Architecture: x86_64 (BOARD=QEMU)
Steps to Reproduce
1._ Built the toolchain successfully using: ./mk_toolchain.sh all
2._ Built the kernel using make.
3._ Build ext2 file on filesys using make.
4._ Created the ISO structure by copying the generated kernel from the bin/ directory and the filesystem from the filesys/ directory
mkdir -p iso_root/boot/grub
mv grub.cfg iso_root/boot/grub/
cp bin/fractal.release.qemu.x86_qemu iso_root/fractal.release.x86
cp filesys/disk.x86_64.ext2 iso_root/
grub-mkrescue -o fractal.iso iso_root/
Booted the resulting fractal.iso using QEMU (also tested by mounting the ISO in VMWare and VirtualBox):
qemu-system-x86_64 -cdrom fractal.iso -m 1024-serial stdio -no-reboot
Actual Behavior
The system simply closes/crashes right after the initial boot sequence. VMWare and VirtualBox do not provide any additional information, even in debug mode. QEMU, on the other hand, prints the initial boot sequence to the serial console before crashing.
In QEMU, the terminal prints the initial boot output but stops abruptly after ASIDs V2: DISABLED.
###Here is the exact serial output I receive before the crash:
Fractal Bootloader
Jumping to long mode...
FRACTAL STARTED
CPU: x86_64
Board: qemu
Variant: release
Kernel: fractal
Version: fractal-x86_64-HEAD-1
ASIDs V2: DISABLED
Hello! I am very interested in your work with Fractal and have been trying to set it up. I am encountering an issue where the OS crashes immediately upon boot when using the GRUB ISO method described in the README. I have tested this across multiple hypervisors and host systems with the exact same result.
Environment
Host OS: Kali Linux and Windows
Hypervisors Tested: QEMU, VirtualBox, VMWare
Target Architecture: x86_64 (BOARD=QEMU)
Steps to Reproduce
1._ Built the toolchain successfully using: ./mk_toolchain.sh all
2._ Built the kernel using make.
3._ Build ext2 file on filesys using make.
4._ Created the ISO structure by copying the generated kernel from the bin/ directory and the filesystem from the filesys/ directory
mkdir -p iso_root/boot/grub
mv grub.cfg iso_root/boot/grub/
cp bin/fractal.release.qemu.x86_qemu iso_root/fractal.release.x86
cp filesys/disk.x86_64.ext2 iso_root/
grub-mkrescue -o fractal.iso iso_root/
Booted the resulting fractal.iso using QEMU (also tested by mounting the ISO in VMWare and VirtualBox):
qemu-system-x86_64 -cdrom fractal.iso -m 1024-serial stdio -no-reboot
Actual Behavior
The system simply closes/crashes right after the initial boot sequence. VMWare and VirtualBox do not provide any additional information, even in debug mode. QEMU, on the other hand, prints the initial boot sequence to the serial console before crashing.
In QEMU, the terminal prints the initial boot output but stops abruptly after ASIDs V2: DISABLED.
###Here is the exact serial output I receive before the crash:
Fractal Bootloader
Jumping to long mode...
FRACTAL STARTED
CPU: x86_64
Board: qemu
Variant: release
Kernel: fractal
Version: fractal-x86_64-HEAD-1
ASIDs V2: DISABLED