[Qemu-devel] Qemu and Longhorn

[Qemu-devel] Qemu and Longhorn

[Darryl Dixon]

[-- 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 --]

Re: [Qemu-devel] Qemu and Longhorn

[Doug Stanley]

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

I thought from what I read that longhorn required a 3d accelerator
card and relied heavily on directX. I thought it was something
crazy like you need atleast an geforce FX5200 just to run longhorn
at a decent speed...

Perhaps that's the problem? Maybe it's doing all the directX in software
and making it take twice as long...but I'm not really a windows or
longhorn expert, so I may just be talking out my a**.

Atleast it installs though right ? ;)

Doug

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

[-- Attachment #2: dstanley.vcf --]
[-- Type: text/x-vcard, Size: 304 bytes --]

begin:vcard
fn:Douglas Stanley
n:Stanley;Douglas
org:Integrated Marketing Technologies;IT
adr:;;2945 Carquest Dr.;Brunswick;Ohio;44212;US
email;internet:dstanley@imtco.com
title:Systems Administrator
tel;work:330-220-6715
x-mozilla-html:FALSE
url:http://www.imtco.com
version:2.1
end:vcard

Re: [Qemu-devel] Qemu and Longhorn

[Fabrice Bellard]

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

Re: [Qemu-devel] Qemu and Longhorn

[Natalia Portillo]

This performance problems exists even in real hardware if the video  
card isn't installed.

Contrary to Windows XP, if the video card hasn't a driver it goes to  
VGA (not to VESA as XP) and goes extremely slow.

Longhorn doesn't have enabled the Direct3D interface by default so this  
is not the problem.

El 16/02/2005, a las 18:51, Fabrice Bellard escribió:

> 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
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

Re: [Qemu-devel] Qemu and Longhorn

[Darryl Dixon]

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

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>

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

Re: [Qemu-devel] Qemu and Longhorn

[Darryl Dixon]

[-- 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 --]

Re: [Qemu-devel] Qemu and Longhorn

[Jernej Simončič]

On Thursday, February 17, 2005, 12:11:54, Darryl Dixon wrote:

> or whether Longhorn simply refuses to have any
> truck with such obsolete legacy devices as floppy drives I don't know ;)

I seriously doubt this - 64bit Windows XP/2003 still won't load additional
drivers needed during installation from anywhere but floppy disks.

-- 
< Jernej Simoncic ><><><><>< http://deepthought.ena.si/ >

Things get worse under pressure.
       -- Murphy's Law of Thermodynamics

Re: [Qemu-devel] Qemu and Longhorn

[Natalia Portillo]

Longhorn doesn't support any ISA device.
Never seen if it supports anything else that PS/2 controller (floppy, 
serial, parallel, etc).

If someone can test on real hardware.

Remember that the Longhorn source tree and the XP/2k3 are different 
ones, so no mather what does one and what does the another.

El 17/02/2005, a las 12:52, Jernej Simončič escribió:

> On Thursday, February 17, 2005, 12:11:54, Darryl Dixon wrote:
>
>> or whether Longhorn simply refuses to have any
>> truck with such obsolete legacy devices as floppy drives I don't know 
>> ;)
>
> I seriously doubt this - 64bit Windows XP/2003 still won't load 
> additional
> drivers needed during installation from anywhere but floppy disks.
>
> -- 
> < Jernej Simoncic ><><><><>< http://deepthought.ena.si/ >
>
> Things get worse under pressure.
>        -- Murphy's Law of Thermodynamics
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>