I'll provide the dump file later.

Meet this issue when installing serial driver on win2k3-64 guest, and running "Common scenario stree with io" (and actually also when running for some other jobs) for other guests.

(In reply to comment #1)
> I'll provide the dump file later.

Analyze the dump file:

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself.  The first argument describes the nature of the
problem, the second argument is the address of the PDO.  The other arguments
vary depending on argument 1.
Arguments:
Arg1: 00000002, Invalid PDO
	An API which requires a PDO has been called with either an FDO,
	a PDO which hasn't been initialized yet (returned to PnP in a
	QueryDeviceRelation/BusRelations), or some random piece of
	memory.
Arg2: 8a9c2e80, Purported PDO.
Arg3: 00000000, Driver object.
Arg4: 00000000

Debugging Details:
------------------

*** ERROR: Module load completed but symbols could not be loaded for vioser.sys

OVERLAPPED_MODULE: Address regions for 'watchdog' and 'cdrom.sys' overlap

BUGCHECK_STR:  0xCA_2

DEVICE_OBJECT: 8a9c2e80

DRIVER_OBJECT: 8a853a30

IMAGE_NAME:  vioser.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d273fe1

MODULE_NAME: vioser

FAULTING_MODULE: 8bb17000 vioser

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 826349eb to 826fbd10

STACK_TEXT:  
807e1e7c 826349eb 000000ca 00000002 8a9c2e80 nt!KeBugCheckEx+0x1e
807e1ea8 8bb19e57 8a9c2e80 8a90a2f8 00000000 nt!IoReportTargetDeviceChangeAsynchronous+0x22a
WARNING: Stack unwind information not available. Following frames may be wrong.
807e1ed8 8bb19f88 00000027 00000100 8a852768 vioser+0x2e57
807e1ef4 8bb1856e 757ada58 8a860950 7579f6a8 vioser+0x2f88
807e1f1c 84888dad 7579f6a8 757ada58 8a86099c vioser+0x156e
807e1f38 84888df6 8a860950 00000000 807e1fa4 Wdf01000!FxInterrupt::DpcHandler+0x60
807e1f48 826873b5 8a86099c 8a860950 8a860950 Wdf01000!FxInterrupt::_InterruptDpcThunk+0x13
807e1fa4 82687218 807c1120 845c8798 00000000 nt!KiExecuteAllDpcs+0xf9
807e1ff4 826869dc 86e53594 00000000 00000000 nt!KiRetireDpcList+0xd5
807e1ff8 86e53594 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
826869dc 00000000 0000001a 00d6850f bb830000 0x86e53594


STACK_COMMAND:  kb

FOLLOWUP_IP: 
vioser+2e57
8bb19e57 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  vioser+2e57

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0xCA_2_VRF_vioser+2e57

BUCKET_ID:  0xCA_2_VRF_vioser+2e57

Followup: MachineOwner
---------

Please refer to http://10.66.65.33/dump-file/MEMORY-bug670713.DMP for details.

is it reproducible on 32-bit platform?
Thanks,
Vadim.

Hi Vadim.

Yes, it also reproducible on 32-bit platform, such as win7-32.

Best Regards,
Dawn

Could you please retest it with the latest driver from
http://download.lab.bos.redhat.com/devel/RHEV/virtio-win/1.1.20
Thanks,
Vadim

(In reply to comment #9)
> Could you please retest it with the latest driver from
> http://download.lab.bos.redhat.com/devel/RHEV/virtio-win/1.1.20
> Thanks,
> Vadim

Re-test with win2k8-32 guest, the problem still exists.

Guest got the same BSOD during a reboot.

Attachment will be provided.

Created attachment 480384 [details]
/analysis_for_bz670713.txt

(In reply to comment #11)
> Created attachment 480384 [details]
> /analysis_for_bz670713.txt

(In reply to comment #11)
> Created attachment 480384 [details]
> /analysis_for_bz670713.txt

Hi Qunfang,
I think, I need to see the entire crash dump file.
Best regards,
Vadim.

(In reply to comment #12)
> (In reply to comment #11)
> > Created attachment 480384 [details]
> > /analysis_for_bz670713.txt
> 
> (In reply to comment #11)
> > Created attachment 480384 [details]
> > /analysis_for_bz670713.txt
> 
> Hi Qunfang,
> I think, I need to see the entire crash dump file.
> Best regards,
> Vadim.

Sorry, forgot attach it.
http://10.66.65.120/mem-dump/MEMORY_670713.DMP.gz

Hi Qunfang,

According to https://bugzilla.redhat.com/show_bug.cgi?id=670713#c0 the command
line looks like this:

1.Start guest with following command:
/usr/libexec/qemu-kvm -m 2G -smp 2 -cpu cpu64-rhel6,+x2apic -usbdevice tablet
-drive
file=win2k8-64-virtio-upgrade.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-ifup -device
e1000,netdev=hostnet0,mac=00:10:20:3F:21:13,bus=pci.0,addr=0x4,id=net0 -boot c
-uuid 1212a123-ea30-4ccf-9ea2-eee6719ea2eb -rtc-td-hack -no-kvm-pit-reinjection
-monitor stdio -name win2k8-32-serial -vnc :1 -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

Do you have any application connected to the other side of the relevant pty
device?
Thank you,
Vadim.

(In reply to comment #14)
> Hi Qunfang,
> 
> According to https://bugzilla.redhat.com/show_bug.cgi?id=670713#c0 the command
> line looks like this:
> 
> 1.Start guest with following command:
> /usr/libexec/qemu-kvm -m 2G -smp 2 -cpu cpu64-rhel6,+x2apic -usbdevice tablet
> -drive
> file=win2k8-64-virtio-upgrade.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-ifup -device
> e1000,netdev=hostnet0,mac=00:10:20:3F:21:13,bus=pci.0,addr=0x4,id=net0 -boot c
> -uuid 1212a123-ea30-4ccf-9ea2-eee6719ea2eb -rtc-td-hack -no-kvm-pit-reinjection
> -monitor stdio -name win2k8-32-serial -vnc :1 -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
> 
> Do you have any application connected to the other side of the relevant pty
> device?
> Thank you,
> Vadim.

Hi, Vadim
No any application connected to it.

Please try the new drivers from:
http://download.devel.redhat.com/brewroot/packages/virtio-win-prewhql/0.1/6/win/virtio-win-prewhql-0.1.zip

According to comment 16,verified this issue with latest build virtio-win-prewhql-0.1-6, this issue does not reproduce on all platforms, following is the details:

virtio-win-prewhql-0.1-6
qemu-kvm-0.12.1.2-2.150.el6
kernel-2.6.32-120.el6

/usr/libexec/qemu-kvm -m 2G -smp 2 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=win7-64-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-ifup -device e1000,netdev=hostnet0,mac=00:10:20:3F:35:02,bus=pci.0,addr=0x4,id=net0 -boot c -uuid cd3dd58b-bf31-4b34-81c8-b00b865b0eb2 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win7-64-serial,server,nowait -mon chardev=111a,mode=readline -name win7-64-serial -vnc :1 -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

so change this bug to verified.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0782.html