Re: Kernel panics (in QEMU) when booting with GRUB2 + OVMF + QEMU.
On Monday, August 17, 2015 05:22:43 PM Andrei Borzenkov wrote: Error itself simply says that kernel cannot find root fs. It does not say anything about why it happened. Yes. It boots on hardware (dd if=test.img of=usb device). Just not on qemu + ovmf. Find pictures of the qemu OVMF error : https://drive.google.com/file/d/0Bx2cO4TT8XjeMTNLTHJRZzhiSHM/view?usp=shar ing You have incorrect kernel command line. It should be root=/dev/sda3 not root/dev/sda3. I apologize. I've fixed it. Find the errors at : https://drive.google.com/file/d/0Bx2cO4TT8XjeTnY4a0luclpNUVk/view?usp=sharing https://drive.google.com/file/d/0Bx2cO4TT8XjeRzFVRGZ1NF9ZZW8/view?usp=sharing Regards, Mark signature.asc Description: This is a digitally signed message part. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Re: Kernel panics (in QEMU) when booting with GRUB2 + OVMF + QEMU.
On Saturday, August 15, 2015 08:31:42 PM Jordan Uggla wrote: Specifically, while Mark entered something like initrd /boot/initramfs-foo-bar, and everything he had typed was echoed back to him on screen as expected, the error message he received was (if I recall correctly) something about the file /boot/initra not being found. In other words, the error message indicated that somewhere the file name entered had been truncated. I suspect that this happened when grub was interpreting the grub.cfg as well, and thus the linux command succeeded but the initramfs command failed, and while grub still tried to boot, the missing initramfs resulted in the kernel panic. That was a personal error. I was typing /vmlinuz-linux ... instead of linux /vmlinuz-linux ... . The same went for the initrd. This, along with other symptoms from previous tries, seems to indicate to me that there is memory corruption somewhere, either due to a bug in grub or in OVMF. I have reproduced the error yet again. It is the same error as I listed in the first post. Find pictures of the qemu OVMF error : https://drive.google.com/file/d/0Bx2cO4TT8XjeMTNLTHJRZzhiSHM/view?usp=sharing https://drive.google.com/file/d/0Bx2cO4TT8XjeM2dpS1RLQXJMdkE/view?usp=sharing Regards, Mark signature.asc Description: This is a digitally signed message part. ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
Kernel panics (in QEMU) when booting with GRUB2 + OVMF + QEMU.
To all,
I've encountered a bug when using GRUB2 + OVMF + QEMU on Arch Linux 64 bit.
The issue can be reproduced when running the latest git code from grub as
well.
ISSUE: Kernel panics (in QEMU) when booting with GRUB2 + OVMF + QEMU.
--
When booting using OVMF (ovmf_x64.bin) + QEMU, GRUB2 manages to load but
kernel panics when loading its menu entry. This issue is not observed in
hardware or via bios boot.
DOWNLOADS: test.img
--
To speed up testing, one can skip reproducing test.img and grab a copy at
https://drive.google.com/file/d/0Bx2cO4TT8XjeSEt2aEVkNEVsZUk/view?usp=sharing
REPRODUCE test.img:
---
# fallocate -l 3G test.img
# gdisk test.img (
o
y
n
1
+1M
ef02
n
2
+100M
ef00
n
3
w
y
)
# kpartx -l test.img /* Get the name of loop device loop */
# kpartx -a test.img
# mkfs.fat /dev/mapper/loopp2
# mkfs.ext4 /dev/mapper/loopp3
# mount /dev/mapper/loopp3 /mnt
# mkdir /mnt/boot
# mount /dev/mapper/loopp2 /mnt/boot
/* This part is Arch Linux specific */
# pacstrap /mnt base grub
/* End Arch Linux specific */
# grub-install --target=i386-pc --boot-directory=/mnt/boot /dev/loop
# grub-install --target=x86_64-efi --efi-directory=/mnt/boot --boot-
directory=/mnt/boot --removable
# echo
insmod all_video
menuentry Arch Linux {
linux /vmlinuz-linux rw root=/dev/sda3
initrd /initramfs-linux-fallback.img
}
/mnt/boot/grub/grub.cfg
# umount -R /mnt
# kpartx -d test.img
REPRODUCE QEMU ERROR:
-
/* Bios works */
# qemu-system-x86_64 -enable-kvm -cpu host test.img
/* UEFI doesn't */
# qemu-system-x86_64 -enable-kvm -cpu host -bios /usr/share/ovmf/ovmf_x64.bin
test.img
/* I get the following error */
Kernel panic - not syncing : VFS: Unable to mount root fs on Unknown-
block(0,0)
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.4-1-ARCH #1
Hardware name : QEMU Standard PC (i440FX + PIIX, 1996), BIOS
7fac344c 880006527db8 815865be
816f61b0 880006527e38 81585453
8810 880006527e48 880006527de8 7fac344c
Call Trace:
[815865be] dump_stack+0x4c/0x6e
[81585453] panic+0xd0/0x203
[818fa621] mount_block_root+0x297/0x2a6
[818fa684] mount_root+0x54/0x58
[818fa7c0] prepare_namespace+0x138/0x171
[818fa22e] kernel_init_freeable+0x1ec/0x215
[8157cbb0] ? rest_init+0x90/0x90
[8157cbbe] kernel_init+0xe/0xf0
[8157c2a2] ret_fromt_fork+0x42/0x70
[8157cbb0] ? rest_init+0x90/0x90
Kernel Offset: disabled
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(0,0)
signature.asc
Description: This is a digitally signed message part.
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
