downgrade to

vgabios to vgabios-0.6b-3.4.el6.noarch  
seabios seabios-0.6.1.2-1.el6.x86_64
kernel kernel-2.6.32-94.el6.x86_64
the problem stills exsits.

but if shut the VM down in a qemu-kvm-144 environment.

and boot the VM again in qemu-kvm-132 environment.


kernel-2.6.32-113.el6.x86_64
qemu-kvm-0.12.1.2-2.144.el6.x86_64
seabios-0.6.1.2-3.el6.x86_64
vgabios-0.6b-3.5.el6.noarch


the driver will work .

the latest qxl-win driver with digital signature   qxl-win-0.1-1   is no work with 144


while the newer but no digital signature driver qxl-win-0.1-2 and qxl-win-0.1-3 works with qemu-kvm-144.

Does adding '-global qxl.revision=1' to the qemu command line (for 144) help (i.e. makes the signed drivers work) ?

(In reply to comment #4)
> Does adding '-global qxl.revision=1' to the qemu command line (for 144) help
> (i.e. makes the signed drivers work) ?



still dont work with 
'-global qxl.revision=1' to the qemu command line 



 'code 10' failed (this device cannot start )



Best Regards

Xiaoqing

Created attachment 478843 [details]
still failed to install with -global.......

Any effect with '-global qxl-vga.revision=1' ?

(In reply to comment #7)
> Any effect with '-global qxl-vga.revision=1' ?

yes,after install the no digital signed driver(with is newer).able to sleep,
and the sleep will cause to the qemu-kvm process die

it outputs:

(qemu) reds_handle_main_link: 
reds_show_new_channel: channel 1:0, connected successfully, over Non Secure link
handle_dev_input: mouse mode 2
reds_main_handle_message: net test: latency 9.938000 ms, bitrate 488782816 bps (466.139618 Mbps)
reds_show_new_channel: channel 4:0, connected successfully, over Non Secure link
red_dispatcher_set_cursor_peer: 
handle_dev_input: cursor connect
reds_show_new_channel: channel 2:0, connected successfully, over Non Secure link
red_dispatcher_set_peer: 
handle_dev_input: connect
handle_new_display_channel: jpeg disabled
handle_new_display_channel: zlib-over-glz disabled
reds_show_new_channel: channel 3:0, connected successfully, over Non Secure link
inputs_link: 
handle_dev_destroy_surfaces: 
qxl_phys2virt: PANIC !qxl->guest_slots[slot].active failed
[root@rhel6xwei staf-kvm]# 


and the guest no BSOD(the qemu-kvm process in host is already quit.)


but if dont install the newer but no digi-signed driver ,nothing diff.

"code 10 "in video driver . cant sleep...etc




Best Regards,
Xiaoqing

Can you please add '-global qxl-vga.debug=1' to get more debug output?

Hmm, the guest driver from
http://download.devel.redhat.com/brewroot/packages/qxl-win/0.1/1/
works just fine for me.  They are not signed though.

Where did you got the guest drivers from?

(In reply to comment #10)
> Hmm, the guest driver from
> http://download.devel.redhat.com/brewroot/packages/qxl-win/0.1/1/
> works just fine for me.  They are not signed though.
> 
> Where did you got the guest drivers from?



https://brewweb.devel.redhat.com/packageinfo?packageID=31174

I have try the 0.1-2   0.1-3 unsigned drivers,works fine.
.

Created attachment 479008 [details]
debug.1

(In reply to comment #9)
> Can you please add '-global qxl-vga.debug=1' to get more debug output?



pls see attachment qxl-win-debug.1.txt


generate this by :

boot the VM use   cmd in the head of the  qxl-win-debug.1.txt.

downgrade the driver from 0.1-3 (unsigned )to 0.1-1  (signed ).
restart the VM,and shutdown 


BTW,"code 10" error.

*** Bug 677907 has been marked as a duplicate of this bug. ***

Change the priority to urgent because whql test need it.

Something is really fishy here.

First, according to people working on windows drivers windows driver installation on windows is quite tricky.  For example Windows silently ignores attempts to install older driver versions.  I'd suggest to start testing another qxl driver version with a fresh guest image which has never ever seen a qxl driver before to make sure windows actually uses the driver you want it to use.

Second, all qxl-win drivers from brew are guest drivers for the new RHEL 6.1 qxl device.  Windows says they are *not* signed (all of them).  Also they don't work with 113 qemu-kvm for me (not surprising as they most likely want use the new features available in 6.1).

/me wonders which qxl driver is active+working in your guest image if you boot the old 113 qemu?

(In reply to comment #16)
> Something is really fishy here.
> 
> First, according to people working on windows drivers windows driver
> installation on windows is quite tricky.  For example Windows silently ignores
> attempts to install older driver versions.  I'd suggest to start testing
> another qxl driver version with a fresh guest image which has never ever seen a
> qxl driver before to make sure windows actually uses the driver you want it to
> use.
> 
hi,I have try use a fresh win installation .but the results are same.

> Second, all qxl-win drivers from brew are guest drivers for the new RHEL 6.1
> qxl device.  Windows says they are *not* signed (all of them).  Also they don't
> work with 113 qemu-kvm for me (not surprising as they most likely want use the
> new features available in 6.1).
> 
> /me wonders which qxl driver is active+working in your guest image if you boot
> the old 113 qemu?

please see the attachment.

(In reply to comment #16)
> Something is really fishy here.
> 
> First, according to people working on windows drivers windows driver
> installation on windows is quite tricky.  For example Windows silently ignores
> attempts to install older driver versions.  I'd suggest to start testing
> another qxl driver version with a fresh guest image which has never ever seen a
> qxl driver before to make sure windows actually uses the driver you want it to
> use.
> 
> Second, all qxl-win drivers from brew are guest drivers for the new RHEL 6.1
> qxl device.  Windows says they are *not* signed (all of them).  Also they don't
> work with 113 qemu-kvm for me (not surprising as they most likely want use the
> new features available in 6.1).
> 
> /me wonders which qxl driver is active+working in your guest image if you boot
> the old 113 qemu?

hi,I am using kernel 113 in the testing.no qemu-kvm-113.
btw,the attached driver is work with qemu-132,kernel-113

Created attachment 480031 [details]
work with qemu-132,kernel-113

Set it as a TestBlocker as whql need spice+qxl.
CC Vadim as well.
Could you guys have a look asap?

Thanks a lot!

Install qxl driver from:
https://brewweb.devel.redhat.com/packageinfo?packageID=31174
Host kernel: 2.6.32-117.el6.x86_64
qemu-kvm: qemu-kvm-0.12.1.2-2.147.el6.x86_64

I boot a win2k3-32 guest, install the qxl driver. Sometimes it can not install
successfully, there's yellow "!" in device manager for QXL driver.
Sometimes it can install successfully. and #powercfg -a tells me the system
supports Standby (S3) and Hibernate.
But after I do Standby from Start menu. The guest quit from qemu and prompt:

qxl_phys2virt: PANIC !qxl->guest_slots[slot].active failed

After I boot the guest again, it does not resume from the point when I do
standby.

Tried with win7 guest, can not install QXL driver successful as well.

Hi Qunfang Zhang,

 Could you try build 133? Looking at the logs Gerd introduced the new spice in 133, so 132 is the old spice. This would just confirm that point.

Thanks,
Alon

Few points:

1. Note you are the first users of the *brew windows build* of the qxl drivers, which I have just recently added & test build for the first time. I didn't know it's already used, but it's really nice having qa so early :)

2. Ignore versions  0.1-1 & 0.1-2 which were just for testing.

3. Regarding 0.1-3 it is still not signed (will not work on Win7) & also versioned incorrectly (old & irrelevant version), which I guess causes lots of headache. I will fix it soon in 0.1-4.

Feel free to contact me for any windows brew build issue by mail/irc as well.
Thanks,
Arnon

(In reply to comment #23)
> Hi Qunfang Zhang,
> 
>  Could you try build 133? Looking at the logs Gerd introduced the new spice in
> 133, so 132 is the old spice. This would just confirm that point.
> 
> Thanks,
> Alon

Hi, Alon 
I installed 133 build and boot a win2k8-64 guest with -spice port=5930,disable-ticketing -vga qxl.
Then install qxl driver qxl-win-0.1-3. After installation, restart guest system as required. But there's a yellow "!" in the device manager for the QXL driver. The driver can not be installed successfully.

(In reply to comment #24)
> Few points:
> 
> 1. Note you are the first users of the *brew windows build* of the qxl drivers,
> which I have just recently added & test build for the first time. I didn't know
> it's already used, but it's really nice having qa so early :)
> 
> 2. Ignore versions  0.1-1 & 0.1-2 which were just for testing.
> 
> 3. Regarding 0.1-3 it is still not signed (will not work on Win7) & also
> versioned incorrectly (old & irrelevant version), which I guess causes lots of
> headache. I will fix it soon in 0.1-4.
> 
> Feel free to contact me for any windows brew build issue by mail/irc as well.
> Thanks,
> Arnon

OK, Thanks~

It seems there are two different issue here:
1. When using brew built windows qxl drivers, there is a problem
   updating the driver.
   But installing the driver on a just-installed VM should work.
2. There is a problem with sleep/suspend mode.
   I think we should disable that in the bios so no VM is allowed to get into
   sleep mode.

Hi, guys
Any new about this issue? Actually we are eager for a new driver to continue whql testing. We need to pass all whql test and submit to MS to ask for the signatures. If we can not get a fixed qxl driver before the end of Mar, it will be hard for us to finish whql submission before deadline.

Thanks
qzhang

Just installed qxl-win-0.1-4 on win2k8-64 guest. The driver can be installed successfully viewed from device manager. But after I do sleep, guest aborted.

(qemu) handle_dev_destroy_surfaces: 
id 0, group 0, virt start 0, virt end ffffffffffffffff, generation 0, delta 0
validate_virt: panic: virtual address out of range
    virt=0x0+0x1d4c00 slot_id=1 group_id=1
    slot=0x0-0x0 delta=0x0

Program received signal SIGABRT, Aborted.

Seems it is the same issue with Bug 688883 - qemu-kvm process quits when windows guest doing S3.

I tried the scratch build https://brewweb.devel.redhat.com/taskinfo?taskID=3197745
and tested both qxl-win-0.1-3 and 0.1-4, all failed with the same error.