From: David Lishchyshen <david@daika.dev>
To: Siddh Raman Pant <sanganaka@siddh.me>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Kernel test
Date: Sat, 28 Feb 2026 20:19:32 +0200 [thread overview]
Message-ID: <db57a15d-9806-4bc9-9729-9ccbc20c773c@daika.dev> (raw)
In-Reply-To: <19ca3aac7cd.248e3142240.8191304919364704072@siddh.me>
Thanks, but I found issue in your guide :)
We need mount drive as VirtIO, so we need to specify `root=/dev/vda` and
`-drive file=$HOME/linux/qemu/image/bookworm.img,format=raw,if=virtio`
without it I had kernel panic
Thanks,
David
On 2/28/26 11:53, Siddh Raman Pant wrote:
> On Sat, 28 Feb 2026 12:42:25 +0530, David Lishchyshen wrote:
>> How you recommend to test kernel? I use Arch and found 3 ways:
>> * Native run, replace existing kernel
>> * Qemu with full Linux distribution, install Ubuntu in qemu and
>> replace kernel in it
>> * Minimal Qemu, need to create initramfs with busybox and connect to
>> Qemu with your kernel, but I even couldn't see printk log from e1000e
>> in this way
> Option 3 is the best way since you can't keep rebooting your machine
> when you reproduce crashes.
>
> I did a writeup about it, it might help you. Take a look here:
> https://bodha.siddh.me/posts/2023/10/14/kernel_qemu_setup/
>
> Thanks,
> Siddh
>
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2026-02-28 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 7:12 Kernel test David Lishchyshen
2026-02-28 9:53 ` Siddh Raman Pant
2026-02-28 18:19 ` David Lishchyshen [this message]
2026-02-28 18:38 ` Siddh Raman Pant
2026-02-28 19:29 ` David Lishchyshen
2026-02-28 19:56 ` Siddh Raman Pant
2026-03-01 18:44 ` David Lishchyshen
2026-02-28 20:45 ` Ozgur Kara
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=db57a15d-9806-4bc9-9729-9ccbc20c773c@daika.dev \
--to=david@daika.dev \
--cc=kernelnewbies@kernelnewbies.org \
--cc=sanganaka@siddh.me \
/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