From: Stefan Hajnoczi <stefanha@gmail.com>
To: Joey Carlini <moocow1452@gmail.com>
Cc: alex.bennee@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ChrEMU - Virtualization in the Browser
Date: Mon, 23 Sep 2013 15:39:30 +0200 [thread overview]
Message-ID: <20130923133930.GA10376@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CADkvBsqWjUF7btUS3o1VDQoFMhD7NgfpA-smeNDrH3=EdP7NWQ@mail.gmail.com>
On Tue, Sep 10, 2013 at 08:08:22PM -0400, Joey Carlini wrote:
> I managed to get QEMU running on a Crouton install, virtual box not being
> possible with the Chrome OS kermel with the KVM mods required, and even a
> couple distros running. Since I enjoy pain and/or haven't done enough cool
> things to be called a badass dev, I figured, why not try building QEMU into
> a Chrome app, now that packaged apps are a thing, and native client allows
> for C code to run within the browser, letting an entire VM run on a stock
> Chromebook.
QEMU isn't pure C code and effort would be required to make it run under
Native Client.
I've never used Native Client but I think its machine code verifier
checks the application to ensure that control flow is safe. In other
words, low-level things that QEMU does like code generation or stack
switching are probably not allowed under Native Client since they are
unsafe!
Maybe I'm wrong and it's possible, but the first thing to check is the
constraints that Native Client puts on the application code.
Stefan
next prev parent reply other threads:[~2013-09-23 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 0:08 [Qemu-devel] ChrEMU - Virtualization in the Browser Joey Carlini
2013-09-23 13:39 ` Stefan Hajnoczi [this message]
2013-09-23 16:24 ` Alex Bennée
2013-09-23 18:48 ` Anthony Liguori
2013-09-25 8:59 ` Stefan Hajnoczi
2013-09-25 13:10 ` Peter Maydell
2013-09-25 14:02 ` Stefan Hajnoczi
2013-10-07 14:49 ` Paolo Bonzini
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=20130923133930.GA10376@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=moocow1452@gmail.com \
--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).