Fedora 38 ARM64 Kernel Panic after VM update

Discussion in 'Linux Virtual Machine' started by Pdub41, Jan 1, 2025.

  1. Pdub41

    Pdub41 Bit poster

    Messages:
    4
    Hello, I'm running a Fedora 38 ARM64 VM on a MacBook Air M2 Sequoia through Parallels 20.1.3.
    A few days ago I did a system update in Fedora and now can't boot the virtual linux instance. Instead I get the the following error:
    error../../grub-core/fs/fshelp.c:257:file
    '/initramfs-6.12.6-200.fc41.aarch64.img' not found.

    This is followed by the Kernel Panic screen and VFS: Unable to mount root fs on unknown-block(0,0)
    Any advice would be appreciated
     
  2. Pdub41

    Pdub41 Bit poster

    Messages:
    4
    I was able to install Fedora 40 through the Parallels Control Centre which booted fine but again when I installed Fedora system updates, I got the same error message.
     
  3. JeffreyO4

    JeffreyO4 Bit poster

    Messages:
    9
    I ran into a very similar issue. There's also another post having the same stating compile fails for the latest kernel. For now I have to run Fedora without Parallel Tools if using the latest kernel. My advice is set grub to use an earlier kernel.
     
  4. JeffreyO4

    JeffreyO4 Bit poster

    Messages:
    9
    Tried finding a solution, but couldn't find an "easy one". It seems this problem has been snowballing for months and Parallels never did anything about it, and now it's hitting the main ones they supposedly support... bleh. Anyways, I'd suggest booting up on a live cd (can setup in config -> hardware -> boot order ) and try to remove their broken kernel module and build / reinstall the latest kernel along with a new initramfs
     
  5. Pdub41

    Pdub41 Bit poster

    Messages:
    4
    Thanks Jeffrey, I updated Fedora excluding the new kernel. Working now with parallel tools enabled.
     
  6. tytso

    tytso Bit poster

    Messages:
    3
    "Snowballing for months" is a bit unfair. The 6.12 Linux kernel was released on November 17, 2024, and Parallel Tools compiled using the 6.11 kernel. So it's been broken for at most two months, and most distributions didn't actually go to the 6.12 kernel until relatively recently. It looks like fixing it shouldn't be that hard; I just haven't bothered yet, since I'm a bit busy at the moment, but it looks like it should be relatively easy fix in /var/lib/dkms/parallels-tools/20.1.2.55742/build/prl_fs/SharedFolders/Guest/Linux/prl_fs/inode.c adjusting the funcction protoype of the function prlfs_write_end().
     
  7. JeffreyO4

    JeffreyO4 Bit poster

    Messages:
    9
    Except they literally promote this product for automated testing, but clearly they don't even do it themselves. Fedora 40 is listed as a supported guest OS and they didn't do the bare minimum for testing. Fedora even runs test events for kernel releases. Here it is two months later and things are breaking. Why pay for a product that breaks when the free alternatives run fine. Then they make it worse by hiding the recovery menu and not documenting the boot parameters for whatever they have setup in their automated install to easily fix the issue.
     
    ParallelsU1393 likes this.
  8. Pdub41

    Pdub41 Bit poster

    Messages:
    4
    Thanks tytso, I excluded the latest kernel from the Fedora update which did the trick.
     

Share This Page