qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] What can qemu do that vmware/virtual pc can't...article idea
Date: Fri, 28 Jul 2006 18:15:46 +0200	[thread overview]
Message-ID: <fb249edb0607280915g1fde83deyda66d5a14ea3f257@mail.gmail.com> (raw)
In-Reply-To: <20060728135806.GB24108@muon.de>

> Soo, do you have any more ideas what qemu can what the (free) alternatives
> from M$/VMWare can't?

I must admit I haven't used Virtual PC and have no idea about what it
can do, but I tried VMWare.

In terms of using, apart from the source code, I think the biggest
advantage of QEMU is the amount of hardware it can emulate. There's a
number of input devices, graphics cards, NICs, storage devices and
above all CPUs. VMWare can do only a very little part of this, and it
doesn't emulate the CPU at all, it only virtualises it. It won't run
on a platform different than i386 or with a guest different than i386.

So, QEMU is a quite generic computer emulator and I don't know if the
word "alternatives" can be used because they don't have the
functionality that I personally exploit in QEMU.

Also, if I was forced to use VMWare for some reason, I would miss the
flexibility of -monitor, -serial, and the options related to the
graphics display, as well as the debug info I can get from QEMU.

Regards,
-- 
balrog 2oo6

Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258

  parent reply	other threads:[~2006-07-28 16:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28 13:58 [Qemu-devel] What can qemu do that vmware/virtual pc can't...article idea Udo 'Robos' Puetz
2006-07-28 14:49 ` Oliver Gerlich
2006-07-28 15:07   ` Linas Žvirblis
2006-07-28 15:01 ` Jan Marten Simons
2006-07-28 16:15 ` andrzej zaborowski [this message]
2006-07-28 16:19 ` Kevin F. Quinn
2006-07-28 22:07 ` Udo 'Robos' Puetz
2006-07-29  3:28 ` Bill C. Riemers

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=fb249edb0607280915g1fde83deyda66d5a14ea3f257@mail.gmail.com \
    --to=balrog@zabor.org \
    --cc=balrogg@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).