Bug 626333

This issue does not exist on virtio-win-1.1.7-2. So it's a regression.
During the version virtio-win-1.1.8-0 ~ virtio-win-1.1.11-0, serial test is blocked by Bug 613949 and Bug 614722.

what is the qemu command line?
Thanks,
Vadim.

(In reply to comment #4)
> what is the qemu command line?
> Thanks,
> Vadim.
Sorry, forgot to paste it.

 /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu qemu64,+x2apic -usbdevice tablet -drive file=win2k8-r2-serial.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none   -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup0 -device e1000,netdev=hostnet0,mac=00:10:42:3F:76:1C,bus=pci.0,addr=0x4,id=net0 -boot c -uuid 37ebf1b7-7195-43d6-8404-1a2a6129e3fc  -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -name win2k8-r2-serial-176  -spice port=5930,disable-ticketing -vga qxl  -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=4,bus=pci.0 -chardev pty,id=channel0 -device virtserialport,chardev=channel0,name=org.linux-kvm.port.0,bus=virtio-serial0.0

Hi, Qunfang.
Could you please re-test two slightly different configurations:
1. the same command line, but "-smp 1"
2. the same command lime, but "-smp 2", and no qxl device?

Thanks,
Vadim.

(In reply to comment #6)
> Hi, Qunfang.
> Could you please re-test two slightly different configurations:
> 1. the same command line, but "-smp 1"
> 2. the same command lime, but "-smp 2", and no qxl device?
> 
> Thanks,
> Vadim.

Hi, Vadim
Tested the above 2 different configurations. Both got BSOD and the error code is still 0x9F.

BTW, tested win7-64, has the same problem.

Can you please try it on any 32-bit OS?
And, any chance of seeing DTM report file?

Thanks & best regards,
Vadim.

(In reply to comment #9)
> Can you please try it on any 32-bit OS?
> And, any chance of seeing DTM report file?
> 
> Thanks & best regards,
> Vadim.

OK, will update result after finish. But because it got BSOD so we can not get a DTM report file.

(In reply to comment #10)
> (In reply to comment #9)
> > Can you please try it on any 32-bit OS?
> > And, any chance of seeing DTM report file?
> > 
> > Thanks & best regards,
> > Vadim.
> 
> OK, will update result after finish. But because it got BSOD so we can not get
> a DTM report file.

OK, thanks.

(In reply to comment #10)
> (In reply to comment #9)
> > Can you please try it on any 32-bit OS?
> > And, any chance of seeing DTM report file?
> > 
> > Thanks & best regards,
> > Vadim.
> 
> OK, will update result after finish. But because it got BSOD so we can not get
> a DTM report file.

Could it be that you have spice agent installed on your system?

(In reply to comment #12)
> (In reply to comment #10)
> > (In reply to comment #9)
> > > Can you please try it on any 32-bit OS?
> > > And, any chance of seeing DTM report file?
> > > 
> > > Thanks & best regards,
> > > Vadim.
> > 
> > OK, will update result after finish. But because it got BSOD so we can not get
> > a DTM report file.
> 
> Could it be that you have spice agent installed on your system?

Qunfang,
could you please try running the tests without any virtserialport device, only virtio-serial-pci?

Thank you,
Vadim.

(In reply to comment #13)
> (In reply to comment #12)
> > (In reply to comment #10)
> > > (In reply to comment #9)
> > > > Can you please try it on any 32-bit OS?

Tested win7-32 with the same command line in Comment 5, got the same BSOD.

> > > > And, any chance of seeing DTM report file?
> > > > 
> > > > Thanks & best regards,
> > > > Vadim.
> > > 
> > > OK, will update result after finish. But because it got BSOD so we can not get
> > > a DTM report file.
> > 
> > Could it be that you have spice agent installed on your system?
Hi, Vadim, when we got BSOD, can only "system_reset" guest in the qemu monitor, and we can not get the DTM report log, whenever I use vnc or spice.

> 
> Qunfang,
> could you please try running the tests without any virtserialport device, only
> virtio-serial-pci?
> 

Tested without virtserialport device, only use virtio-serial-pci, still got BSOD.

> Thank you,
> Vadim.

please check with the latest drivers from 
http://download.lab.bos.redhat.com/devel/RHEV/virtio-win/mm21/

Please check two different scenarios: 
- vioserial device only, without any port device;
- vioserial device with one or two port devices.

Thanks,
Vadim.

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

(In reply to comment #18)
> please check with the latest drivers from 
> http://download.lab.bos.redhat.com/devel/RHEV/virtio-win/mm21/
> 
> Please check two different scenarios: 
> - vioserial device only, without any port device;
Test with the driver, and this bug does not exist in win2k8-R2.

> - vioserial device with one or two port devices.
The job will take many hours, so we continue to test without port devices for other jobs and guests. and try to get all guests' vioserial result for submission.

> Thanks,
> Vadim.

Created attachment 442567 [details]
dump  analysis file for 2k8r2 bsod in virtio-win-1.1.13-0

Please check with the latest drivers from
http://download.lab.bos.redhat.com/devel/RHEV/virtio-win/1.1.14-0/

The long-awaited RPM with these new drivers is now available:

https://brewweb.devel.redhat.com/buildinfo?buildID=144698

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.