From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] International Virtualization Conference
Date: Sun, 8 Oct 2006 17:58:51 +0100 [thread overview]
Message-ID: <20061008165851.GA3009@mail.shareable.org> (raw)
In-Reply-To: <20061008143646.GA27314@jbrown.mylinuxbox.org>
Jim C. Brown wrote:
> On Sun, Oct 08, 2006 at 05:30:19AM -0700, Ottavio Caruso wrote:
> > http://www.linuxworldexpo.de/linux_messe.php?ID=124&STEP=&lang=en
> >
> > I don't see Qemu mentioned at all. I wonder if any of the
> > developers have been contacted at all. I thing it is a pity that once
> > againg Qemu is ignored.
> >
> > Ottavio
>
> qemu is primarily a dynamic translator not a virtualizer.
VMware is also a dynamic translator for some code. "Full"
virtualisation (i.e. not like Xen) requires that.
> I suppose that qemu could get in by virtue of kqemu.
qemu+kqemu is a useful, powerful, versatile x86 virtualisation
package. It really should be mentioned at a conference on the
subject. But maybe the conference is only for commercially-backed
parties?
> That [kqemu] is closed source but being closed source hasn't stopped
> VMware.
Don't forget qvm86, which is intended as an open source drop-in
replacement for kqemu.
-- Jamie
next prev parent reply other threads:[~2006-10-08 18:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 12:30 [Qemu-devel] International Virtualization Conference Ottavio Caruso
2006-10-08 14:36 ` Jim C. Brown
2006-10-08 15:35 ` Joshua Root
2006-10-08 16:58 ` Jamie Lokier [this message]
2006-10-08 23:35 ` Jim C. Brown
2006-10-09 4:05 ` Rob Landley
2006-10-09 12:08 ` Jim C. Brown
2006-10-10 15:48 ` Rob Landley
2006-10-10 17:18 ` Jim C. Brown
2006-10-11 2:03 ` Rob Landley
2006-10-11 2:54 ` Jim C. Brown
2006-10-10 9:26 ` Joshua Root
2006-10-10 15:54 ` Rob Landley
2006-10-10 17:23 ` Jim C. Brown
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=20061008165851.GA3009@mail.shareable.org \
--to=jamie@shareable.org \
--cc=qemu-devel@nongnu.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).