From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] International Virtualization Conference
Date: Tue, 10 Oct 2006 11:54:57 -0400 [thread overview]
Message-ID: <200610101154.57588.rob@landley.net> (raw)
In-Reply-To: <452B6730.4010207@root.id.au>
On Tuesday 10 October 2006 5:26 am, Joshua Root wrote:
> Part of the generally accepted definition of virtualization is that the
> majority of guest instructions execute directly on the real CPU with no
> intervention by the VMM. QEMU + qvm86 does count as virtualization if
> the system spends most of its time in user mode; QEMU on its own does
> not (you run code that is very different to the original binary).
So it stops being a virtual environment if you run Java or Python in it? (or
anything else that uses bytecode?)
Or if I get one of those old Rockwell Java processors (or a Dallas
semiconductor Java iButton, or an ARM processor with a J in it) and make a
coprocessor out of it (I dunno, plug it into the USB port and send code to
it), I now have a virtual Java environment because the bytecode is running on
real hardware?
Rob
--
"Perfection is reached, not when there is no longer anything to add, but when
there is no longer anything to take away." - Antoine de Saint-Exupery
next prev parent reply other threads:[~2006-10-10 15:55 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
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 [this message]
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=200610101154.57588.rob@landley.net \
--to=rob@landley.net \
--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).