Bug 1783214 - BSOD when click refresh button in device manager in windows guest (blockdev)
Summary: BSOD when click refresh button in device manager in windows guest (blockdev)
Keywords:
Status: CLOSED DUPLICATE of bug 1711167
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: 8.2
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: 8.2
Assignee: Amnon Ilan
QA Contact: qing.wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-13 10:33 UTC by menli@redhat.com
Modified: 2020-04-16 11:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-23 08:39:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
bsod (23.74 KB, image/png)
2019-12-13 10:33 UTC, menli@redhat.com
no flags Details

Description menli@redhat.com 2019-12-13 10:33:41 UTC
Created attachment 1644753 [details]
bsod

Description of problem:
Hit BSOD when refresh on device manage in win2019 guest with virtio-scsi-pci device and backend is blockdev.

Version-Release number of selected component (if applicable):
kernel-core-4.18.0-165.el8.x86_64
qemu-kvm-4.2.0-2.module+el8.2.0+5135+ed3b2489.x86_64
seabios-1.12.0-5.module+el8.2.0+4793+b09dd2fb.x86_64
virtio-win-prewhql-0.1-174.iso


How reproducible:
100%


Steps to Reproduce:
1. Booted windows guest  with virtio-scsi-pci and backend is blockdev.
 /usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm3' \
    -machine q35 \
    -nodefaults \
    -vga std  \
    -device pcie-root-port,id=pcie.0-root-port-3,slot=3,chassis=3,addr=0x3,bus=pcie.0 \
    -device pcie-root-port,id=pcie-root-port-5,slot=5,chassis=5,bus=pcie.0  \
    -device pcie-root-port,id=pcie-root-port-6,slot=6,chassis=6,bus=pcie.0  \
    -device pcie-root-port,id=pcie-root-port-7,slot=7,chassis=7,bus=pcie.0  \
    -device pcie-root-port,id=pcie-root-port-8,slot=8,chassis=8,bus=pcie.0  \
    -device pcie-root-port,id=pcie-root-port-9,slot=9,chassis=9,bus=pcie.0  \
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie-root-port-5,addr=0x0 \
    -blockdev node-name=file_image1,driver=file,cache.direct=on,cache.no-flush=off,filename=win2019.qcow2,aio=threads \
    -blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
    -device scsi-hd,id=image1,drive=drive_image1  \
    -device virtio-net-pci,mac=9a:36:83:b6:3d:05,id=idJVpmsF,netdev=id23ZUK6,bus=pcie-root-port-7,addr=0x0  \
    -netdev tap,id=id23ZUK6,vhost=on \
    -m 14336  \
    -smp 2,maxcpus=4 \
    -cpu 'Skylake-Server' \
    -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/ISO/Win2019/en_windows_server_2019_x64_dvd_4cb967d8.iso \
    -device ide-cd,id=cd2,drive=drive_cd1,bus=ide.0,unit=0 \
    -cdrom /home/kvm_autotest_root/iso/windows/virtio-win-prewhql-0.1-172.iso \
    -device piix3-usb-uhci,id=usb -device usb-tablet,id=input0 \
    -vnc :11  \
    -rtc base=localtime,clock=host,driftfix=slew  \                                                       
    -boot order=cdn,once=c,menu=off,strict=off \
    -enable-kvm \
    -qmp tcp:0:1231,server,nowait \
    -monitor stdio \

2. open device manager in guest and refresh 


Actual results:
BSOD

Expected results:
no BSOD

Additional info:
1.no issue with -drive
2.no issue with virtio-blk device
3.hit it on win2012
4.windbg log

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffff9d0f9cbd1080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  10.0.17763.107 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  Red Hat

SYSTEM_PRODUCT_NAME:  KVM

SYSTEM_VERSION:  RHEL-8.1.0 PC (Q35 + ICH9, 2009)

BIOS_VENDOR:  SeaBIOS

BIOS_VERSION:  1.12.0-5.module+el8.2.0+4793+b09dd2fb

BIOS_DATE:  04/01/2014

DUMP_TYPE:  1

BUGCHECK_P1: ffff9d0f9cbd1080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  services.exe

CRITICAL_PROCESS:  services.exe

EXCEPTION_RECORD:  ffff9d0f9cbd1640 -- (.exr 0xffff9d0f9cbd1640)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 0

EXCEPTION_CODE: (NTSTATUS) 0x9cda7540 - <Unable to get error code text>

ERROR_CODE: (NTSTATUS) 0x9cda7540 - <Unable to get error code text>

CPU_COUNT: 2

CPU_MHZ: 82f

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R)  SIG: 1'00000000 (cache) 1'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xEF

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  WIN-3IORRL4PE1F

ANALYSIS_SESSION_TIME:  12-13-2019 17:18:12.0333

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8070f81b1dd to fffff8070f1be040

THREAD_SHA1_HASH_MOD_FUNC:  970c66ec931231a073d40cce1e396d0220e62660

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e96ec51cb4cfe02226ad3c699af4be2e553842eb

THREAD_SHA1_HASH_MOD:  93f3cda62d6816517e161ec85731e575b0d3c716

FOLLOWUP_IP: 
ntdll!RtlLookupFunctionEntry+118
00007ff8`75146968 448b1c86        mov     r11d,dword ptr [rsi+rax*4]

FAULT_INSTR_CODE:  861c8b44

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  ntdll!RtlLookupFunctionEntry+118

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ntdll

IMAGE_NAME:  ntdll.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  118

FAILURE_BUCKET_ID:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_9cda7540_ntdll!RtlLookupFunctionEntry

BUCKET_ID:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_9cda7540_ntdll!RtlLookupFunctionEntry

PRIMARY_PROBLEM_CLASS:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_9cda7540_ntdll!RtlLookupFunctionEntry

TARGET_TIME:  2019-12-14T02:03:45.000Z

OSBUILD:  17763

OSSERVICEPACK:  107

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  400

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 Server TerminalServer DataCenter SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.17763.107

ANALYSIS_SESSION_ELAPSED_TIME:  c15

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xef_services.exe_bugcheck_critical_process_9cda7540_ntdll!rtllookupfunctionentry

FAILURE_ID_HASH:  {92b45b80-7771-4508-4d2a-6b41b3c881f9}

Followup:     MachineOwner

Comment 2 menli@redhat.com 2019-12-16 03:30:52 UTC
hit this issue in virtio-win-1.9.9-3.el8.iso(8.1.0 release version)

Comment 6 qing.wang 2019-12-23 08:39:29 UTC

*** This bug has been marked as a duplicate of bug 1711167 ***


Note You need to log in before you can comment on or make changes to this bug.