From: "Richard W.M. Jones" <rjones@redhat.com>
To: Mike Rapoport <mike.rapoport@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [QUERY] lguest64
Date: Thu, 8 Aug 2013 20:15:22 +0100 [thread overview]
Message-ID: <20130808191522.GA1857@redhat.com> (raw)
In-Reply-To: <CABpLfohrweJd0=0eFJDO7dv2HHxx_mbP0uySMDrsZZZXExdXug@mail.gmail.com>
On Wed, Jul 31, 2013 at 12:39:23PM +0300, Mike Rapoport wrote:
> On Tue, Jul 23, 2013 at 4:28 AM, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > Yes, the subset of x86-64 machines for which there isn't hardware
> > virtualization support is pretty uninteresting.
>
> There are plenty virtual machines in EC2, Rackspace, HP and other
> clouds that do not have hardware virtualization. I believe that
> running a hypervisor on them may be pretty interesting.
[Jumping in rather late]
The problem with basing this on lguest is that you would need to
implement a whole lot of stuff from qemu to make lguest really useful
as a modern hypervisor. eg. qcow2 and a variety of other block
devices, kvmclock, virtio{-scsi,-net}. Probably more, but just
implementing those will keep you going for a while. It might also be
feasible to add lguest support to qemu.
However I think it's best to do nothing and use TCG mode in qemu. TCG
is a bit slower than lguest or UML, but definitely not unusable. It's
a drop-in replacement for qemu/KVM with all the same features, and it
works today.
We use and support TCG to make libguestfs work on EC2.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
prev parent reply other threads:[~2013-08-08 19:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 9:06 [QUERY] lguest64 Ramkumar Ramachandra
2013-07-19 17:29 ` H. Peter Anvin
2013-07-19 17:42 ` Ramkumar Ramachandra
2013-07-19 18:46 ` H. Peter Anvin
2013-07-19 20:36 ` richard -rw- weinberger
2013-08-01 17:22 ` Ramkumar Ramachandra
2013-08-01 13:04 ` Alex Elsayed
2013-07-23 1:28 ` Rusty Russell
2013-07-31 9:39 ` Mike Rapoport
2013-07-31 12:17 ` H. Peter Anvin
2013-07-31 13:07 ` Mike Rapoport
2013-07-31 13:19 ` H. Peter Anvin
2013-07-31 14:32 ` Mike Rapoport
2013-08-01 2:12 ` Rusty Russell
2013-08-02 14:27 ` H. Peter Anvin
2013-07-31 13:17 ` Konrad Rzeszutek Wilk
2013-07-31 13:25 ` H. Peter Anvin
2013-08-02 19:09 ` Konrad Rzeszutek Wilk
2013-08-04 12:37 ` Gleb Natapov
2013-08-05 16:50 ` Konrad Rzeszutek Wilk
2013-08-05 16:59 ` H. Peter Anvin
2013-08-05 17:16 ` Konrad Rzeszutek Wilk
2013-07-31 15:31 ` Borislav Petkov
2013-08-01 7:18 ` Mike Rapoport
2013-08-08 19:15 ` Richard W.M. Jones [this message]
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=20130808191522.GA1857@redhat.com \
--to=rjones@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.rapoport@gmail.com \
/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