how to use qxl driver in windows 7 . win7 also choose zhe standar vga driver itself .
and say that is zhe best and newest. 2011/6/16 <spice-devel-requ...@lists.freedesktop.org> > Send Spice-devel mailing list submissions to > spice-devel@lists.freedesktop.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freedesktop.org/mailman/listinfo/spice-devel > or, via email, send a message with subject or body 'help' to > spice-devel-requ...@lists.freedesktop.org > > You can reach the person managing the list at > spice-devel-ow...@lists.freedesktop.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Spice-devel digest..." > > > Today's Topics: > > 1. Re: [RFC] qxl: set mm_time in vga update (Gerd Hoffmann) > 2. Re: Windows QXL driver - low pixel depth, low resolution, > laggard mouse (John A. Sullivan III) > 3. Re: Windows QXL driver - low pixel depth, low resolution, > laggard mouse (John A. Sullivan III) > 4. Re: [RFC] qxl: set mm_time in vga update (Alon Levy) > 5. Re: Windows QXL driver - low pixel depth, low resolution, > laggard mouse (Alon Levy) > 6. Re: Windows QXL driver - low pixel depth, low resolution, > laggard mouse (--[ UxBoD ]--) > 7. Re: Windows QXL driver - low pixel depth, low resolution, > laggard mouse (Damien Churchill) > 8. Re: Windows QXL driver - low pixel depth, low resolution, > laggard mouse (John A. Sullivan III) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 16 Jun 2011 15:34:52 +0200 > From: Gerd Hoffmann <kra...@redhat.com> > Subject: Re: [Spice-devel] [RFC] qxl: set mm_time in vga update > To: Alon Levy <al...@redhat.com> > Cc: spice-devel@lists.freedesktop.org, qemu-de...@nongnu.org > Message-ID: <4dfa067c.1000...@redhat.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 06/15/11 20:44, Alon Levy wrote: > > This fixes a problem where on windows 7 startup phase, before the qxl > driver > > is loaded, the drawables are sufficiently large and video like to trigger > a > > stream, but the lack of a filled mm time field triggers a warning in > spice-gtk. > > Looks good to me. Why this is tagged RFC? > > cheers, > Gerd > > > > ------------------------------ > > Message: 2 > Date: Thu, 16 Jun 2011 09:41:01 -0400 > From: "John A. Sullivan III" <jsulli...@opensourcedevel.com> > Subject: Re: [Spice-devel] Windows QXL driver - low pixel depth, low > resolution, laggard mouse > To: Alon Levy <al...@redhat.com> > Cc: spice-devel@lists.freedesktop.org > Message-ID: <1308231661.11030.0.ca...@denise.theartistscloset.com> > Content-Type: text/plain; charset="UTF-8" > > 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 ]-- <ux...@splatnix.net> 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? > > > > <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 > ) > > > Thanks, we did that and there is no ! next to the device. We did notice > that before we signed the driver and that's when it was defaulting to > VGA - JOhn > > > > ------------------------------ > > Message: 3 > Date: Thu, 16 Jun 2011 09:44:45 -0400 > From: "John A. Sullivan III" <jsulli...@opensourcedevel.com> > Subject: Re: [Spice-devel] Windows QXL driver - low pixel depth, low > resolution, laggard mouse > To: Alon Levy <al...@redhat.com> > Cc: spice-devel@lists.freedesktop.org > Message-ID: <1308231885.11030.3.ca...@denise.theartistscloset.com> > Content-Type: text/plain; charset="UTF-8" > > On Thu, 2011-06-16 at 15:50 +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 ]-- <ux...@splatnix.net> 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? > > > > <snip> > > I've installed yesterday on windows 2008 R2 successfully, the only real > difference from win7/winxp is that the drivers have to be signed, and either > cross signed by microsoft or you need to set the vm to accept self signed > drivers. > > > > You can easily tell the driver is not really loaded by looking at > devmgmt.msc (device manager), the driver will have an exclamation mark > overlayed on the icon. > > > > I'm not sure if the self signed drivers are on the site, but I'm > attaching self signed drivers (these are development only - based on > unpushed patches). > > > Strange, I wonder what is different between your environment and mine. > I replaced the rpms on the Fedora host. Was I supposed to do anything > with the Windows drivers? The patched seemed only for qemu. I'll give > these a try and see if it changes anything. > > I should mentioned that, before Windows presented its "Press Ctl Alt Del > to login" screen, the color was brilliant for the Windows logo. It > changed when it got to the login screen. Thanks - John > > > > > ------------------------------ > > Message: 4 > Date: Thu, 16 Jun 2011 17:52:00 +0200 > From: Alon Levy <al...@redhat.com> > Subject: Re: [Spice-devel] [RFC] qxl: set mm_time in vga update > To: Gerd Hoffmann <kra...@redhat.com> > Cc: spice-devel@lists.freedesktop.org, qemu-de...@nongnu.org > Message-ID: <20110616155200.gx19...@bow.redhat.com> > Content-Type: text/plain; charset=us-ascii > > On Thu, Jun 16, 2011 at 03:34:52PM +0200, Gerd Hoffmann wrote: > > On 06/15/11 20:44, Alon Levy wrote: > > >This fixes a problem where on windows 7 startup phase, before the qxl > driver > > >is loaded, the drawables are sufficiently large and video like to > trigger a > > >stream, but the lack of a filled mm time field triggers a warning in > spice-gtk. > > > > Looks good to me. Why this is tagged RFC? > > I wasn't sure if the right thing is to set the mm_time or just not warn if > it is missing. > This can be committed as is if you think it's good. > > > > > cheers, > > Gerd > > > > > ------------------------------ > > Message: 5 > Date: Thu, 16 Jun 2011 17:53:40 +0200 > From: Alon Levy <al...@redhat.com> > Subject: Re: [Spice-devel] Windows QXL driver - low pixel depth, low > resolution, laggard mouse > To: "John A. Sullivan III" <jsulli...@opensourcedevel.com> > Cc: spice-devel@lists.freedesktop.org > Message-ID: <20110616155340.gy19...@bow.redhat.com> > Content-Type: text/plain; charset=us-ascii > > On Thu, Jun 16, 2011 at 09:44:45AM -0400, John A. Sullivan III wrote: > > On Thu, 2011-06-16 at 15:50 +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 ]-- <ux...@splatnix.net> 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? > > > > > > <snip> > > > I've installed yesterday on windows 2008 R2 successfully, the only real > difference from win7/winxp is that the drivers have to be signed, and either > cross signed by microsoft or you need to set the vm to accept self signed > drivers. > > > > > > You can easily tell the driver is not really loaded by looking at > devmgmt.msc (device manager), the driver will have an exclamation mark > overlayed on the icon. > > > > > > I'm not sure if the self signed drivers are on the site, but I'm > attaching self signed drivers (these are development only - based on > unpushed patches). > > > > > Strange, I wonder what is different between your environment and mine. > > The only difference that should bother anything is the creation and signing > of qxl.cat, signing of qxl.sys and signing of qxldd.dll. The > easiest route I thought was just to send you prebuilt and signed drivers, > but you can do that yourself, the information is on the wiki (WinQXL page). > > > I replaced the rpms on the Fedora host. Was I supposed to do anything > > with the Windows drivers? The patched seemed only for qemu. I'll give > > these a try and see if it changes anything. > > > > I should mentioned that, before Windows presented its "Press Ctl Alt Del > > to login" screen, the color was brilliant for the Windows logo. It > > changed when it got to the login screen. Thanks - John > > Yes, that's when the driver is loaded. > > > > > > > > ------------------------------ > > Message: 6 > Date: Thu, 16 Jun 2011 15:01:25 +0100 (BST) > From: "--[ UxBoD ]--" <ux...@splatnix.net> > Subject: Re: [Spice-devel] Windows QXL driver - low pixel depth, low > resolution, laggard mouse > To: "John A. Sullivan III" <jsulli...@opensourcedevel.com> > Cc: spice-devel@lists.freedesktop.org > Message-ID: <ebb6dca4-012f-4a3f-9235-77a32f022...@office.splatnix.net> > Content-Type: text/plain; charset=utf-8 > > ----- Original Message ----- > > On Thu, 2011-06-16 at 15:50 +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 ]-- <ux...@splatnix.net> > > > > > > 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? > > > > > > <snip> > > > I've installed yesterday on windows 2008 R2 successfully, the only > > > real difference from win7/winxp is that the drivers have to be > > > signed, and either cross signed by microsoft or you need to set > > > the vm to accept self signed drivers. > > > > > > You can easily tell the driver is not really loaded by looking at > > > devmgmt.msc (device manager), the driver will have an exclamation > > > mark overlayed on the icon. > > > > > > I'm not sure if the self signed drivers are on the site, but I'm > > > attaching self signed drivers (these are development only - based > > > on unpushed patches). > > > > > Strange, I wonder what is different between your environment and > > mine. > > I replaced the rpms on the Fedora host. Was I supposed to do > > anything > > with the Windows drivers? The patched seemed only for qemu. I'll > > give > > these a try and see if it changes anything. > > > > I should mentioned that, before Windows presented its "Press Ctl Alt > > Del > > to login" screen, the color was brilliant for the Windows logo. It > > changed when it got to the login screen. Thanks - John > > > > > > I believe the Windows logo you see within the boot process is low > resolution anyway. > -- > Thanks, Phil > > > ------------------------------ > > Message: 7 > Date: Thu, 16 Jun 2011 15:20:46 +0100 > From: Damien Churchill <dam...@gmail.com> > Subject: Re: [Spice-devel] Windows QXL driver - low pixel depth, low > resolution, laggard mouse > To: "John A. Sullivan III" <jsulli...@opensourcedevel.com>, Damien > Churchill <dam...@gmail.com>, spice-devel@lists.freedesktop.org > Message-ID: <banlktim3fp1o_08eehce+z0wckfqwey...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 16 June 2011 16:53, Alon Levy <al...@redhat.com> wrote: > > > > The only difference that should bother anything is the creation and > signing of qxl.cat, signing of qxl.sys and signing of qxldd.dll. The > > easiest route I thought was just to send you prebuilt and signed drivers, > but you can do that yourself, the information is on the wiki (WinQXL page). > > > > Are you able to provide the driver patches as well? > > > ------------------------------ > > Message: 8 > Date: Thu, 16 Jun 2011 10:22:32 -0400 > From: "John A. Sullivan III" <jsulli...@opensourcedevel.com> > Subject: Re: [Spice-devel] Windows QXL driver - low pixel depth, low > resolution, laggard mouse > To: Alon Levy <al...@redhat.com> > Cc: spice-devel@lists.freedesktop.org > Message-ID: <1308234152.11030.6.ca...@denise.theartistscloset.com> > Content-Type: text/plain; charset="UTF-8" > > 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 ]-- <ux...@splatnix.net> 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 > Spice-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/spice-devel > > > End of Spice-devel Digest, Vol 17, Issue 22 > ******************************************* >
_______________________________________________ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
