qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: daniel.carrera@zmsl.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] No useful documentation.
Date: Wed, 5 Jul 2006 22:25:24 +0100	[thread overview]
Message-ID: <20060705212524.GA27733@mail.shareable.org> (raw)
In-Reply-To: <1152133046.8295.85.camel@Agape-desktop>

Daniel Carrera wrote:
> I've looked at qemu several times over the past several years. Every
> time I get excited at the prospect of migrating people to GNU/Linux by
> letting them run the one windows app they need... and every time I hit a
> brick wall, as qemu fails to actually do anything useful.
> 
> Try to take this approach: You are writing to a technically competent
> user (perhaps a sysadmin) who wants to run Windows under Linux with qemu
> (perhaps to migrate some of the company computers). He has a Windows
> install CD, he has qemu installed, and is ready to go. Please write
> something that this person can use to get Windows running under qemu.

Personally I found Qemu astonishingly easy to use, and simply not
needing a lot of documentation to get an OS installed from CD into it.

A couple of hours after installing Qemu, having never used it before,
I had a working virtual machine running CentOS, installed from a set
of virtual CDs.  An hour later, kqemu (the accelerator) was installed
and working.

I was most impressed by how easy it was and how little I had to tweak.

But then I wasn't trying to run Windows inside it.

Is Windows harder to install in it than some random Linux distro?

-- Jamie

  parent reply	other threads:[~2006-07-05 21:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05 20:57 [Qemu-devel] No useful documentation Daniel Carrera
2006-07-05 21:07 ` Rick Vernam
2006-07-05 21:12 ` Nathaniel McCallum
2006-07-05 21:19   ` Daniel Carrera
2006-07-05 21:25     ` Rick Vernam
2006-07-05 21:40       ` Daniel Carrera
2006-07-05 22:48         ` Flavio Visentin
2006-07-05 22:52           ` Daniel Carrera
2006-07-05 23:11             ` benb
2006-07-05 23:02               ` WaxDragon
2006-07-05 23:06           ` benb
2006-07-05 23:36             ` Flavio Visentin
2006-07-06  0:19               ` benb
2006-07-05 21:29     ` Nathaniel McCallum
2006-07-05 21:31     ` Larry Brigman
2006-07-05 21:25 ` Jamie Lokier [this message]
2006-07-05 21:38   ` Daniel Carrera
2006-07-05 22:25     ` Jamie Lokier
2006-07-05 22:45       ` benb
2006-07-05 22:41     ` NyOS
2006-07-05 21:34 ` benb
2006-07-05 21:22   ` Daniel Carrera
2006-07-05 21:46     ` Udo 'Robos' Puetz
2006-07-05 22:01       ` Daniel Carrera
2006-07-06  0:00         ` Mike Swanson
2006-07-06  8:16           ` Daniel Carrera
2006-07-06 11:03             ` denis.scheidt
2006-07-05 22:30       ` Jamie Lokier
2006-07-05 22:34 ` Ronnie Misra
2006-07-05 22:38   ` Daniel Carrera
2006-07-05 22:56     ` benb
2006-07-09  9:26 ` [Qemu-devel] " Emmanuel Charpentier
  -- strict thread matches above, loose matches on Subject: below --
2006-07-05 21:05 [Qemu-devel] " Dugger, Donald D

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=20060705212524.GA27733@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=daniel.carrera@zmsl.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).