From: Laurence Rochfort <laurence.rochfort@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Kernel development virtualization options
Date: Fri, 16 Nov 2018 10:41:43 +0000 [thread overview]
Message-ID: <CAMof6LAyNcugf3RyB7G4xD7PQ45kL=CvG6S+Pe=5mQVq1Y=-6A@mail.gmail.com> (raw)
Message-ID: <20181116104143.4gBc6q8lsyH-bgULGAbodokYBasUVIGI2w6mPWec_NA@z> (raw)
Hi all,
Thus far, I've been testing my kernel patches in a KVM vm with a full
distro installation, but it's pretty slow and cumbersome.
Valerie Aurora has a blog post on using User-mode Linux, and others
mention QEMU with an overlay filesystem and BusyBox.
What do people recommend for quick iterative development, with good
GDB integration?
Cheers,
Laurence.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2018-11-16 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 10:41 Laurence Rochfort [this message]
2018-11-16 10:41 ` Kernel development virtualization options Laurence Rochfort
2018-11-16 17:02 ` Mulyadi Santosa
2018-11-16 17:02 ` Mulyadi Santosa
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='CAMof6LAyNcugf3RyB7G4xD7PQ45kL=CvG6S+Pe=5mQVq1Y=-6A@mail.gmail.com' \
--to=laurence.rochfort@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
/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).