On Thu, 2011-06-16 at 15:54 +0200, Alon Levy wrote: > On Thu, Jun 16, 2011 at 01:42:07AM -0400, John A. Sullivan III wrote: > > On Thu, 2011-06-16 at 01:34 +0200, Alon Levy wrote: > > > On Wed, Jun 15, 2011 at 09:35:57PM +0100, Damien Churchill wrote: > > > > On 15 June 2011 21:11, --[ UxBoD ]-- <[email protected]> wrote: > > > > > ----- Original Message ----- > > > > >> Hello, all. We have recently jumped into SPICE with both hands and > > > > >> feet > > > > >> as we are intrigued with the possibilities. But, we've hit a few > > > > >> rocks > > > > >> along the way! > > > > >> > > > > >> The immediate problems with our two test Windows installations > > > > >> (Windows7 > > > > >> and Windows Server 2008 running as KVM guests in Fedora 15) using the > > > > >> QXL driver is that the pixel depth appears to be 4-bits, the only > > > > >> available resolutions are 640x480 and 800x600, and the mouse is > > > > >> unusably > > > > >> lagged. > > > <snip>> > > > > > > Alon (Redhat Dev) has a patch for QEMU which should hopefully fix the > > > > > 4bpp issue but the binary and necessary libraries he sent me would > > > > > not run successfully on our server. It was execute and then hang and > > > > > eventually time out. Perhaps, as discussed, we could build from > > > > > source though I wonder why that patch has not been fully committed > > > > > yet? > > > > > -- > > > > > > > > Is the patch available to try anywhere? I'd like to give it a test and > > > > see what happens. > > > > > > attached. > > <snip> > > > > Argh!!! I recompiled the rpms from the srpms after applying the patch > > and thought for sure our woes would be ended! Alas, perhaps we have 8 > > bit color now and we still have a maximum resolution of 800x600 :( > > > > What next? > > > > I double checked the BUILD directory to confirm the patch was applied. > > > <snip>> > > Forgot to mention: to let the vm accept self signed certificates you need to: > bcdedit.exe -set TESTSIGNING ON > > (see http://spice-space.org/page/WinQXL, and the source is > http://stackoverflow.com/questions/5698617/signing-x64-driver-with-test-certificate) > Strange, after doing this with the new drivers, there is an ! mark next to the driver and I'm falling back to the VGA drivers. I wonder if we mangled something in our original signing. I'm going to resign the drivers we compiled and try again - John
_______________________________________________ Spice-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/spice-devel
