From: Jesper Juhl <jesper.juhl@gmail.com>
To: jerome lacoste <jerome.lacoste@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] make it easy to test new kernels
Date: Thu, 26 Jan 2006 00:02:56 +0100 [thread overview]
Message-ID: <9a8748490601251502q7d0ed605xb2b6477ffe5ea87f@mail.gmail.com> (raw)
In-Reply-To: <5a2cf1f60601251430k5823e7dald12c9b5f8bc297be@mail.gmail.com>
On 1/25/06, jerome lacoste <jerome.lacoste@gmail.com> wrote:
[...]
>
> Now, will all these talks about virtualization, I wonder if it will be
> possible one day to just download a new virtualized test OS and test
> it without rebooting the main one. I could always allocate 10 G to a
> test system on my disk. As long as I don't have to reboot.
>
[...]
Sure, you can test some aspects of the kernel in a virtualized environment.
Setup Xen [1] or UML [2] (or some other virtual machine software like
Bochs [3] or Qemu [4]) and use those virtual environments for testing
your new kernels - no reboots required.
Not the best way to test all aspects of new kernels, but if reboots
are out of the question then they are certainly options and better
than no testing at all :)
1. http://www.cl.cam.ac.uk/Research/SRG/netos/xen/
2. http://user-mode-linux.sourceforge.net/
3. http://bochs.sourceforge.net/
4. http://fabrice.bellard.free.fr/qemu/
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-01-25 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 22:30 jerome lacoste
2006-01-25 22:50 ` Christopher Friesen
2006-01-25 23:02 ` Jesper Juhl [this message]
2006-01-30 14:52 ` Tejun
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=9a8748490601251502q7d0ed605xb2b6477ffe5ea87f@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=jerome.lacoste@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®