Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-869

[virtio-win][viostor+vioscsi] Failed hotunplug in guest

Details

    • Major
    • CustomerScenariosInitiative
    • sst_virtualization_windows
    • ssg_virtualization
    • False
    • Hide

      None

      Show
      None
    • RN only
    • Yes
    • Known Issue
    • Hide
      .Hot-unplugging a storage device on Windows VMs might fail

      On virtual machines (VMs) that use a Windows guest operating system, removing a storage device when the VM is running (also known as a device hot-unplug) in some cases fails. As a consequence, the storage device remains attached to the VM and the disk manager service might become unresponsive.
      Show
      .Hot-unplugging a storage device on Windows VMs might fail On virtual machines (VMs) that use a Windows guest operating system, removing a storage device when the VM is running (also known as a device hot-unplug) in some cases fails. As a consequence, the storage device remains attached to the VM and the disk manager service might become unresponsive.
    • Done

    Description

      Description of problem:
      data disk still in disk manager after hotunplug.

      Version-Release number of selected component (if applicable):

      qemu-kvm-4.2.0-19.module+el8.2.0+6296+6b821950.x86_64
      kernel-4.18.0-193.el8.x86_64
      virtio-win-prewhql-181
      seabios-1.13.0-1.module+el8.2.0+5520+4e5817f3.x86_64

      How reproducible:
      1/5

      Steps to Reproduce:
      1. boot guest with below cmd lines.
      /usr/libexec/qemu-kvm \
      -name 'avocado-vt-vm1' \
      -sandbox on \
      -machine q35 \
      -device pcie-root-port,id=pcie-root-port-0,multifunction=on,bus=pcie.0,addr=0x1,chassis=1 \
      -device pcie-pci-bridge,id=pcie-pci-bridge-0,addr=0x0,bus=pcie-root-port-0 \
      -nodefaults \
      -device VGA,bus=pcie.0,addr=0x2 \
      -m 14336 \
      -smp 24,maxcpus=24,cores=12,threads=1,dies=1,sockets=2 \
      -cpu 'Skylake-Server',hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,+kvm_pv_unhalt \
      -object iothread,id=iothread0 \
      -object iothread,id=iothread1 \
      -blockdev node-name=file_image1,driver=file,aio=threads,filename=/home/kvm_autotest_root/images/win2016-64-virtio.qcow2,cache.direct=on,cache.no-flush=off \
      -blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
      -device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \
      -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,iothread=iothread0,bus=pcie-root-port-2,addr=0x0 \
      -device pcie-root-port,id=pcie-root-port-4,port=0x4,addr=0x1.0x4,bus=pcie.0,chassis=5 \
      -device virtio-net-pci,mac=9a:49:63:b8:8b:03,id=id4BeT93,netdev=id3m5Beo,bus=pcie-root-port-4,addr=0x0 \
      -netdev tap,id=id3m5Beo \
      -blockdev node-name=file_cd1,driver=file,read-only=on,aio=threads,filename=/home/kvm_autotest_root/iso/windows/winutils.iso,cache.direct=on,cache.no-flush=off \
      -blockdev node-name=drive_cd1,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_cd1 \
      -device ide-cd,id=cd1,drive=drive_cd1,bootindex=2,write-cache=on,bus=ide.0,unit=0 \
      -vnc :0 \
      -rtc base=localtime,clock=host,driftfix=slew \
      -boot menu=off,order=cdn,once=c,strict=off \
      -enable-kvm \
      -qmp tcp:0:1231,server,nowait \
      -device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \

      2. hotplug blk device
      {"execute": "blockdev-add", "arguments": {"node-name": "file_stg0", "driver": "file", "aio": "threads", "filename": "/home/kvm_autotest_root/images/storage0.raw", "cache": {"direct": true, "no-flush": false}}, "id": "ZODSKhzq"}
      {"execute": "blockdev-add", "arguments": {"node-name": "drive_stg0", "driver": "raw", "cache":

      {"direct": true, "no-flush": false}

      , "file": "file_stg0"}, "id": "PDBqM4ab"}
      {"execute": "device_add", "arguments":

      {"driver": "virtio-blk-pci", "id": "stg0", "drive": "drive_stg0", "write-cache": "on", "bus": "pcie-root-port-3", "addr": "0x0"}

      , "id": "AfUx0F55"}

      3.format disk in disk manager

      4.hotunplug blk device
      {'execute': 'device_del', 'arguments':

      {'id': 'stg0'}

      , 'id': 'w4Tj7zKN'}
      {'execute': 'blockdev-del', 'arguments':

      {'node-name': 'drive_stg0'}

      , 'id': 'inkmmsdp'}
      {'execute': 'blockdev-del', 'arguments':

      {'node-name': 'file_stg0'}

      , 'id': 'WqOdPb0n'}

      4.repeate step 2 and 4

      5.send command :'wmic logicaldisk get drivetype,name,description & wmic diskdrive list brief /format:list' to check disk info

      Actual results:
      After step5,disk still display in disk manager,but can not get its info.

      Expected results:
      data disk should not display in disk manager after hotunplug.

      Additional info:

      Attachments

        Activity

          People

            rhn-support-vrozenfe Vadim Rozenfeld
            rhn-support-menli Menghuan Li
            virt-maint virt-maint
            Menghuan Li Menghuan Li
            Jiří Herrmann Jiří Herrmann
            Votes:
            0 Vote for this issue
            Watchers:
            19 Start watching this issue

            Dates

              Created:
              Updated: