qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu and Longhorn
Date: Fri, 18 Feb 2005 00:11:54 +1300	[thread overview]
Message-ID: <1108638715.5587.16.camel@localhost.localdomain> (raw)
In-Reply-To: <1108592421.8439.20.camel@csrn99fxw86.chhnet.net>

[-- Attachment #1: Type: text/plain, Size: 4652 bytes --]

Well.

    I managed to get a video driver for the Cirrus 5446 installed.  I
shamelessly cribbed three files: cirrus.dll, cirrus.sys, and display.inf
from the Windows XP SP2 install, and managed to put up with the pain
involved in getting them installed/shoehorned into Longhorn.  They work
perfectly.  Which leads me to another observation: Longhorn doesn't
detect Qemu's floppy drive (I mkisofs'ed the above files and inserted
the pretend cd to get them onto the virtual machine).  Whether this is
because there is some sort of bug that Longhorn has revealed in the
floppy emulation code, or whether Longhorn simply refuses to have any
truck with such obsolete legacy devices as floppy drives I don't know ;)

    The thing that I discovered that made persevering with it possible
is that the stupid clock that Longhorn slaps onto the right-hand taskbar
by default chews CPU cycles like they're going out of style -- it has an
animated seconds hand.  I just removed that entire toolbar and suddenly
everything was a *lot* quicker.  With the clock gone and the Cirrus
driver installed it is now roughly 3-4x as slow as the WinXP SP2 install
with the same setup.  So it's usable, just ;)  (That and it has a *lot*
of bugs, which makes things worse).

    I imagine that the driver for the RTL8029 that I have posted to this
list previously also works correctly in Longhorn (if one has enough
patience).  Perhaps I'll try it out tomorrow...

Regards,
D

On Thu, 2005-02-17 at 11:20 +1300, Darryl Dixon wrote:

>Hi Fabrice,
>
>    If possible, it is even slower without kqemu, and is in fact almost
>impossible to use.  There are some errors too, like no taskbar coming
>up, etc - presumably they simply take so long that the operation ends
>up going to the bit bucket... :)
>
>
>D
>
>
>On Wed, 2005-02-16 at 19:51 +0100, Fabrice Bellard wrote: 
>
>>Do you have the same performance problems without kqemu ?
>>
>>Fabrice.
>>
>>Darryl Dixon wrote:
>>>   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 
>>> <mailto:esrever_otua@pythonhacker.is-a-geek.net>>
>>> 
>>> 
>>> ------------------------------------------------------------------------
>>> 
>>> _______________________________________________
>>> Qemu-devel mailing list
>>> Qemu-devel@nongnu.org
>>> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>>
>
>>-- 
>>Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
>
>_______________________________________________
>Qemu-devel mailing list
>Qemu-devel@nongnu.org
>http://lists.nongnu.org/mailman/listinfo/qemu-devel

-- 
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>

[-- Attachment #2: Type: text/html, Size: 7464 bytes --]

  reply	other threads:[~2005-02-17 11:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  8:22 [Qemu-devel] Qemu and Longhorn Darryl Dixon
2005-02-16 16:12 ` 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 [this message]
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=1108638715.5587.16.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).