From: Anthony Liguori <anthony@codemonkey.ws>
To: Pekka Enberg <penberg@kernel.org>
Cc: linux-kernel@vger.kernel.org, aarcange@redhat.com,
avi@redhat.com, mtosatti@redhat.com, kvm@vger.kernel.org,
joro@8bytes.org, penberg@cs.helsinki.fi, asias.hejun@gmail.com,
gorcunov@gmail.com, mingo@elte.hu
Subject: Re: [ANNOUNCE] Native Linux KVM tool
Date: Sat, 02 Apr 2011 15:38:08 -0500 [thread overview]
Message-ID: <4D978930.1000909@codemonkey.ws> (raw)
In-Reply-To: <1301592656.586.15.camel@jaguar>
On 03/31/2011 12:30 PM, Pekka Enberg wrote:
> Hi all,
>
> We’re proud to announce the native Linux KVM tool!
Neat!
As something of a lesson of history, I'd suggest picking a more unique
name while it's still a prototype :-)
> The goal of this tool is to provide a clean, from-scratch, lightweight
> KVM host tool implementation that can boot Linux guest images (just a
> hobby, won't be big and professional like QEMU) with no BIOS
> dependencies and with only the minimal amount of legacy device
> emulation.
I see you do provide 16-bit entry points for Linux. Are you planning on
paravirtualizing this within Linux to truly eliminate the BIOS dependency?
Regards,
Anthony Liguori
> Note that this is a development prototype for the time being: there's no
> networking support and no graphics support, amongst other missing
> essentials.
>
> It's great as a learning tool if you want to get your feet wet in
> virtualization land: it's only 5 KLOC of clean C code that can already
> boot a guest Linux image.
>
> Right now it can boot a Linux image and provide you output via a serial
> console, over the host terminal, i.e. you can use it to boot a guest
> Linux image in a terminal or over ssh and log into the guest without
> much guest or host side setup work needed.
>
> 1. To try out the tool, clone the git repository:
>
> git clone git://github.com/penberg/linux-kvm.git
>
> or alternatively, if you already have a kernel source tree:
>
> git checkout -b kvm/tool
> git pull git://github.com/penberg/linux-kvm.git
>
> 2. Compile the tool:
>
> cd tools/kvm&& make
>
> 3. Download a raw userspace image:
>
> wget http://wiki.qemu.org/download/linux-0.2.img.bz2&& bunzip2
> linux-0.2.img.bz2
>
> 4. Build a kernel with CONFIG_VIRTIO_BLK=y and
> CONFIG_SERIAL_8250_CONSOLE=y configuration options. Note: also make sure
> you have CONFIG_EXT2_FS or CONFIG_EXT4_FS if you use the above image.
>
> 5. And finally, launch the hypervisor:
>
> ./kvm --image=linux-0.2.img --kernel=../../arch/x86/boot/bzImage
>
> The tool has been written by Pekka Enberg, Cyrill Gorcunov, and Asias
> He. Special thanks to Avi Kivity for his help on KVM internals and Ingo
> Molnar for all-around support and encouragement!
>
> See the following thread for original discussion for motivation of this
> project:
>
> http://thread.gmane.org/gmane.linux.kernel/962051/focus=962620
>
> Pekka
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-02 20:38 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 17:30 [ANNOUNCE] Native Linux KVM tool Pekka Enberg
[not found] ` <1B1AE097-4524-4026-85EC-F9A0E274FFF2@suse.de>
2011-04-01 7:07 ` Carsten Otte
2011-04-01 7:37 ` Cyrill Gorcunov
2011-04-01 14:26 ` Steven Rostedt
2011-04-02 20:38 ` Anthony Liguori [this message]
2011-04-03 6:21 ` Ingo Molnar
2011-04-03 8:24 ` Avi Kivity
2011-04-03 8:53 ` Pekka Enberg
2011-04-03 9:06 ` Cyrill Gorcunov
2011-04-03 9:37 ` CaT
2011-04-04 10:31 ` Ingo Molnar
2011-04-03 8:51 ` Pekka Enberg
2011-04-03 9:17 ` Avi Kivity
2011-04-03 8:23 ` Avi Kivity
2011-04-03 9:59 ` Pekka Enberg
2011-04-03 10:11 ` Avi Kivity
2011-04-03 10:17 ` Pekka Enberg
2011-04-03 10:22 ` Avi Kivity
2011-04-03 10:32 ` Pekka Enberg
2011-04-03 13:09 ` Anthony Liguori
2011-04-03 13:19 ` Avi Kivity
2011-04-06 9:33 ` Ingo Molnar
2011-04-06 9:36 ` Gleb Natapov
2011-04-06 9:46 ` Ingo Molnar
2011-04-06 9:49 ` Avi Kivity
2011-04-06 9:51 ` Gleb Natapov
2011-04-06 10:14 ` Olivier Galibert
2011-04-06 10:55 ` Ingo Molnar
2011-04-08 2:04 ` Anthony Liguori
2011-04-08 2:14 ` Anthony Liguori
2011-04-08 5:14 ` Pekka Enberg
2011-04-08 6:19 ` Cyrill Gorcunov
2011-04-08 6:47 ` Takuya Yoshikawa
2011-04-08 6:51 ` Pekka Enberg
2011-04-08 7:10 ` Takuya Yoshikawa
2011-04-08 7:39 ` Jan Kiszka
2011-04-08 8:27 ` Pekka Enberg
2011-04-08 9:11 ` Jan Kiszka
2011-04-08 9:32 ` Cyrill Gorcunov
2011-04-08 10:42 ` Jan Kiszka
2011-04-08 12:27 ` Alexander Graf
2011-04-08 12:33 ` Cyrill Gorcunov
2011-04-08 14:39 ` Ted Ts'o
2011-04-08 14:00 ` Anthony Liguori
2011-04-08 19:20 ` Andrea Arcangeli
2011-04-08 22:59 ` Anthony Liguori
2011-04-10 8:05 ` Avi Kivity
2011-04-09 7:40 ` Ingo Molnar
2011-04-12 0:58 ` Andrea Arcangeli
2011-04-09 18:23 ` Olivier Galibert
2011-04-10 2:54 ` Anthony Liguori
2011-04-08 15:59 ` Scott Wood
2011-04-08 19:41 ` gene heskett
2011-04-08 22:58 ` Anthony Liguori
2011-04-06 8:59 ` Markus Armbruster
2011-04-06 9:29 ` Gleb Natapov
2011-04-03 9:01 ` Alon Levy
2011-04-03 10:01 ` Pekka Enberg
2011-04-03 10:15 ` Alon Levy
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=4D978930.1000909@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aarcange@redhat.com \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=penberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.