From: "Roger Lathrop" <ratchetr@sprynet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] What can qemu do that vmware/virtual pc
Date: Fri, 28 Jul 2006 21:53:43 -0400 [thread overview]
Message-ID: <00a601c6b2b1$d2c13230$7145fea9@DELL3G> (raw)
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
> Soo, do you have any more ideas what qemu can what the (free) alternatives
> from M$/VMWare can't?
I use both QEMU and VMWare (commercial version), but for very different reasons. Both are excellent tools that make my job easier.
I'm primarily a Windows developer, but I do have some Linux tools I support. VMWare works well when I need to switch to Linux to write code. It virtualizes a generic PC, which is all I need. It's time tested, reliable and predictable.
But I work for a company that sells HW/SW. Our HW is your basic PC, but with some additional non-standard devices. Our SW won't run without these devices (no way, no matter how clever you are with the preprocessor, you won't make it run). So it won't run under VMWare, or VPC. They aren't extensible. QEMU is. Just grab the source code.
Fabrice et.el. did an amazing thing with QEMU. Adding emulation for our hardware wasn't tough to do. Moving from the edit...compile...download...reboot...debug...repeat cycle to edit...compile...debug...repeat cycle is a BIG advantage for us. You just can't do that with the commercial products.
And QEMU is so light weight...I can throw the whole thing on a pen drive, plug into any managers/sales/marketing/tech writers/etc. machine, and just run it. Installing VMWare player is a bit more heavy handed. Not sure, but I suspect you need admin priv. to do it? I live in corp. America. Our tech writers don't HAVE admin privileges.
[-- Attachment #2: Type: text/html, Size: 2299 bytes --]
reply other threads:[~2006-07-29 1:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='00a601c6b2b1$d2c13230$7145fea9@DELL3G' \
--to=ratchetr@sprynet.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).