From: Connor Kuehl <cipkuehl@gmail.com>
To: Manuel Quintero Fonseca <manuel@uas.edu.mx>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: QEMU end Kernel panic - not sysncing: VFS: Unable to mount toor fs on unknown
Date: Wed, 19 Jun 2019 15:52:12 -0700 [thread overview]
Message-ID: <CAC_QXZTTKDd_bjU8wBeQiSF9f4Kc3RpXdX+ef2dtZYBmS8uyJw@mail.gmail.com> (raw)
In-Reply-To: <CAPegGh_10=YiZHYgAvhav5C6t4J1TB-QgMh6RCqhy83bjOs93A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1453 bytes --]
On Wed, Jun 19, 2019 at 10:47 AM Manuel Quintero Fonseca <manuel@uas.edu.mx>
wrote:
> Hello, I have been wanting to learn how to use QEMU for the development of
> the linux kernel, at the kernelnewbies.org page I did not find any
> information, in google I found this page:
> https://www.collabora.com/news-and-blog/blog/2017/01/16/setting-up-qemu-kvm-for-kernel-development/
>
> Following the first examples, it gives me two problems, I hope you can
> guide me.
>
> $qemu-system-x86_64 -kernel /boot/vmlinuz-`uname -r`
>
> end Kernel panic - not sysncing: VFS: Unable to mount toor fs on
> unknown-block(0,0)
>
>
> aku@openSUSE:~> sudo qemu-system-x86_64 -kernel /boot/vmlinuz-`uname -r`
> [sudo] password for root:
> Unable to init server: Could not connect: Connection refused
>
Hi Manuel,
This is because you're not supplying it with a root file system. The
article you linked goes on to describe this process, but I've found this
blog post[1] to be a bit more concise and easy to follow. It'll show you
how to use "mkinitramfs" to make a ramdisk to pass to QEMU alongside the
kernel you're trying to boot.
Good luck!
Connor
[1]
http://nickdesaulniers.github.io/blog/2018/10/24/booting-a-custom-linux-kernel-in-qemu-and-debugging-it-with-gdb/
>
>
>
> Thank you
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
[-- Attachment #1.2: Type: text/html, Size: 3639 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-06-19 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 17:47 QEMU end Kernel panic - not sysncing: VFS: Unable to mount toor fs on unknown Manuel Quintero Fonseca
2019-06-19 22:52 ` Connor Kuehl [this message]
2019-06-20 4:05 ` Manuel Quintero Fonseca
2019-06-20 6:43 ` Michal Rostecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAC_QXZTTKDd_bjU8wBeQiSF9f4Kc3RpXdX+ef2dtZYBmS8uyJw@mail.gmail.com \
--to=cipkuehl@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=manuel@uas.edu.mx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).