qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu speed vs vmplayer?
Date: Fri, 15 Dec 2006 22:47:08 +0000	[thread overview]
Message-ID: <200612152247.10133.paul@codesourcery.com> (raw)
In-Reply-To: <46d6db660612151434k502de652m91658b2e3b451fab@mail.gmail.com>

> Is qvm86 still active ? if yes, great. if no, what do you need to restart
> it ? (else than dedicated developpers, of course). As far as I can see, no
> qvm86 check-in for 15 months now...

Not really. I haven't had chance to do anything with it for a while, and 
probably won't in the forseeable future. It probably wouldn't take more than 
a couple of weeks work for an experienced coder to get it working properly.

If someone else shows serious interest in qvm86 I've no real objection to 
handing over management of the project to them.

As Anthony mentioned, efforts might be best spent integrating this 
functionality into Xen or KVM. You're more than welcome to use qvm86 code for 
this.

Paul

  reply	other threads:[~2006-12-15 22:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13  8:09 [Qemu-devel] About performance of qemu-system-arm PianoPan
2006-12-13 10:32 ` [Qemu-devel] " Ross Burton
2006-12-13 11:22 ` [Qemu-devel] " Màrius Montón
2006-12-13 14:17   ` PianoPan
2006-12-13 15:23     ` Màrius Montón
2006-12-13 13:26 ` Martin Guy
2006-12-13 14:40   ` [Qemu-devel] qemu-system-* using mmap? Tim Olson
2006-12-13 15:32     ` Paul Brook
2006-12-13 16:04     ` Joseph Miller
2006-12-14 14:50       ` Tim Olson
2006-12-14 17:01         ` [Qemu-devel] " Joseph Miller
2006-12-14 16:45           ` Paul Brook
2006-12-15 16:21             ` [Qemu-devel] Qemu speed vs vmplayer? Joseph Miller
2006-12-15 16:13               ` Paul Brook
2006-12-15 22:20                 ` Joseph Miller
2006-12-15 21:33                   ` Lonnie Mendez
2006-12-15 21:38                   ` Paul Brook
2006-12-15 21:48                     ` Christian MICHON
2006-12-15 21:57                       ` Lonnie Mendez
2006-12-15 22:18                       ` Paul Brook
2006-12-15 22:34                         ` Christian MICHON
2006-12-15 22:47                           ` Paul Brook [this message]
     [not found]                   ` <Pine.LNX.4.64.0612160028590.758@home.oyster.ru>
     [not found]                     ` <25199.71.51.225.120.1166272989.squirrel@secure.emarketingnc.com>
     [not found]                       ` <Pine.LNX.4.64.0612161732560.630@home.oyster.ru>
2006-12-17  4:37                         ` it
2006-12-17  5:18                           ` Lonnie Mendez
2006-12-19 16:00                             ` [Qemu-devel] Qemu speed w/ USB tablet emulation Joseph Miller
2006-12-16  5:27                 ` [Qemu-devel] Qemu speed vs vmplayer? Jamie Lokier
2006-12-15 16:32             ` [Qemu-devel] using mmap? Mark Williamson
2006-12-15 21:22               ` [Qemu-devel] " Anthony Liguori
2006-12-13 15:10   ` [Qemu-devel] About performance of qemu-system-arm Martin Guy

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=200612152247.10133.paul@codesourcery.com \
    --to=paul@codesourcery.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).