From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu and Longhorn
Date: Wed, 16 Feb 2005 21:22:57 +1300 [thread overview]
Message-ID: <1108542177.16634.13.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]
Hi All,
Just for giggles I ran an install of Longhorn build 4074 on CVS Qemu
today with kqemu. The install seemed to go well; the first stage didn't
recognise any mouse (probably more a Windows error than a Qemu one), but
was otherwise perfectly rendered (with what appeared to be a vesa video
mode) and usable with the keyboard. It proceeded reasonably quickly.
After the first reboot, the mouse was detected and worked, and it once
again proceed reasonably quickly (vesa video mode again), up until it
started detecting the hardware, at which point it stuck for around an
hour (it was actually doing work and processing the whole time). During
this all seemed well, and I even watched it detect the video OK and flip
from 640x480 to 800x600. Once it made it past the hardware detect and
booted into the actual Windows GUI, things got painful. Apparently even
though the installer knows how to use vesa video, Windows itself and the
standard VGA display driver it installed *don't* and so I was left with
a 640x480 16 colour display that ran *agonisingly* slowly, presumably as
all of the video calls were being emulated through calls to the Bochs
BIOS. It was glacial. Anyhow, I managed to soldier through a few
windows to the Device Manager, and from what I could see everything
except the network card had been detected OK (except of course that the
video was 'Standard VGA'). Presumably the network card just needs the
Win2000 RTL8029 driver like Server 2003 did. I tried to fix the video
so I'd be able to give Qemu + Longhorn a proper test, but after
(literally) hours to get through the driver update wizard and find that
my only choice was the standard VGA or something called a 'BARCO', I
gave up and wrote this short summary instead :) Presumably a more
patient man would be able to install the Cirrus Win2000 driver and
Longhorn on Qemu would be usable...
Many regards,
--
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
[-- Attachment #2: Type: text/html, Size: 2459 bytes --]
next reply other threads:[~2005-02-16 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 8:22 Darryl Dixon [this message]
2005-02-16 16:12 ` [Qemu-devel] Qemu and Longhorn Doug Stanley
2005-02-16 18:51 ` Fabrice Bellard
2005-02-16 21:56 ` Natalia Portillo
2005-02-16 22:20 ` Darryl Dixon
2005-02-17 11:11 ` Darryl Dixon
2005-02-17 12:52 ` Jernej Simončič
2005-02-18 0:19 ` Natalia Portillo
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=1108542177.16634.13.camel@localhost.localdomain \
--to=esrever_otua@pythonhacker.is-a-geek.net \
--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).