From: Joe Lee <joelee724@gmail.com>
To: Natalia Portillo <claunia@claunia.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Support Questions
Date: Tue, 13 Jun 2006 10:37:17 -0400 [thread overview]
Message-ID: <448ECD9D.3010102@gmail.com> (raw)
In-Reply-To: <F4B870B0-694C-4518-8B81-742A5B8567F5@claunia.com>
I came across a product called Iemulator and think it based on QEMU. If
so, I wanted to know how possible is it to re-brand qemu to something
similar to Iemulator.
Also, I am quite new to QEMU and virtualization in general and wanted to
know the difference between QEMU and product like OpenVZ. Based on my
reading on them I think they are quite different. I suppose QEMU is more
like VMware aimed at end users and OpenVZ would be more for Enterprise
servers.
Joe
Natalia Portillo wrote:
> Well,
>
> Fabrice Bellard is main developer, and KQEMU whole developer.
> Paul Brook maintains ARM system, and QVM86 whole developer.
> Jocelyn Mayer (away) maintains PPC system.
> Blue Swirl maintains Sparc system.
> A couple of collaborators do development taks.
> I maintain the OS compatibility list and do extensive operating system
> compatibility testing.
>
> Just, for what you want that information?
>
> El 12/06/2006, a las 20:32, Joe Lee escribió:
>
>> Wanted to know about individuals that provides support and custom
>> development for QEUM.
>>
>>
>>
>> _______________________________________________
>> Qemu-devel mailing list
>> Qemu-devel@nongnu.org
>> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>>
>
>
next prev parent reply other threads:[~2006-06-13 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 19:32 [Qemu-devel] Support Questions Joe Lee
2006-06-12 19:41 ` Natalia Portillo
2006-06-12 22:36 ` Johannes Schindelin
2006-06-13 14:37 ` Joe Lee [this message]
2006-06-13 15:39 ` Johannes Schindelin
2006-06-13 19:34 ` Mike Kronenberg
2006-06-13 20:56 ` Joe Lee
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=448ECD9D.3010102@gmail.com \
--to=joelee724@gmail.com \
--cc=claunia@claunia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.