retitle 574988 kvm: cirrus video slower than snapshots close 574988 thanks On Mon, Mar 22, 2010 at 09:06:47PM +0300, Michael Tokarev wrote: > I just tried it with 0.12.3+dfsg-4 (the one that entered -testing today). > I see almost instant scrolling in winXP and w2k3 cmd window. `dir' in > C:\Windows directory takes a few fractions of a second to scroll. I even
> > processor : 0 > > vendor_id : AuthenticAMD > > cpu family : 15 > > model : 75 > > model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ > > One thing I notice is that my CPU is quite a bit faster than this: > mine is running at 2.5GHz. So that may explain the difference between > your 1-2s/page with my less than 0.5s/page, in case of bad matching of > color depth, but the difference is still larger than I'd expect based > solely on cpu speed (mine is of the same generation, Athlon x2 64). It's still a reasonably fast processor ;) It runs at 2GHz but slows down to 1000MHz and 1800MHz depending on load. My Windows installs under qemu-kvm date back to early 2007. This makes them over 3 years old. In this time qemu-kvm has changed its "hardware signature" to the OS a few times and it was always using the default cirrus emulation. Now, I've tried the "new" -vga std and amazingly video speed is back to normal. I have tested at 1400x1050 and have seen no difference between color depths (16, 24 or 32 bit). All function perfectly and almost instant scrolling. So I think the culprit may be using cirrus video at max resolution (1280x1024 16-bit). Heck, I can't even use same bit depth as desktop with cirus - native would be 1920x1080 32-bit. Do you happen to know if there is any particular reason why `-vga std` is not the new default options for qemu-kvm? - Adam PS. I'm retitling this bug to something that is more descriptive. Closing it as well as I don't think there will be lots of work done in cirrus emulation code anyway considering there is the std video driver that works so much better. -- Adam Majer [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
