RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1449118 - [Q35] scsi controller unplug failed after migration
Summary: [Q35] scsi controller unplug failed after migration
Keywords:
Status: CLOSED DUPLICATE of bug 1455150
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Fam Zheng
QA Contact: jingzhao
URL:
Whiteboard:
Depends On: 1455150
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-09 09:18 UTC by jingzhao
Modified: 2017-06-28 02:29 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-20 07:44:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
dmesg log of dst (44.30 KB, text/plain)
2017-05-09 09:18 UTC, jingzhao 		no flags Details
View All

Description jingzhao 2017-05-09 09:18:02 UTC 
Created attachment 1277339 [details]
dmesg log of dst

Description of problem:
scsi controller unplug failed after migration

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.9.0-3.el7.x86_64
kernel-3.10.0-663.el7.x86_64

How reproducible:
3/3

Steps to Reproduce:
1.Boot guest with qemu cli in src [1]
2.Hot-plug virtio scsi disk through qmp
{"execute":"__com.redhat_drive_add", "arguments": {"file":"/home/test/rhel/block1.qcow2","format":"qcow2","id":"drive_datadisk0"}}
{"return": {}}
{"execute":"device_add","arguments":{"driver":"virtio-scsi-pci","id":"scsi1","bus":"root2"}}
{"return": {}}
{"execute":"device_add","arguments":{"driver":"scsi-hd","drive":"drive_datadisk0","id":"device_datadisk0","bus":"scsi1.0"}}
{"return": {}}
{"execute":"__com.redhat_drive_add", "arguments": {"file":"/home/test/rhel/block2.qcow2","format":"qcow2","id":"drive_datadisk1"}}
{"return": {}}
{"execute":"device_add","arguments":{"driver":"virtio-scsi-pci","id":"scsi2","bus":"root1"}}
{"return": {}}
{"execute":"device_add","arguments":{"driver":"scsi-hd","drive":"drive_datadisk1","id":"device_datadisk1","bus":"scsi2.0"}}
{"return": {}}

3.Boot guest with qemu cli in dst [2]

4.Migration from src to dst
(qemu) migrate -d tcp:10.66.6.246:5800
      
(qemu) migrate_set_downtime 1
  
(qemu) migrate_set_speed 1G

5.After migrate finished, unplug scsi disk and scsi controller in dst

6.Check the scsi controller in guest
[root@localhost ~]# lspci -vvv -t
-[0000:00]-+-00.0  Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller
           +-01.0  Red Hat, Inc. QXL paravirtual graphic card
           +-02.0-[01]----00.0  Red Hat, Inc Virtio block device
           +-03.0-[02]----00.0  Red Hat, Inc Virtio SCSI
           +-04.0  Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode]
           +-0a.0-[03]----00.0  Red Hat, Inc Virtio network device
           +-0a.1-[04]----00.0  Red Hat, Inc Virtio SCSI
           +-1f.0  Intel Corporation 82801IB (ICH9) LPC Interface Controller
           +-1f.2  Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode]
           \-1f.3  Intel Corporation 82801I (ICH9 Family) SMBus Controller


Actual results:
Disk unplug successfully , but scsi controller unplug failed

dmesg log, please check the attachment

Expected results:
Disk and scsi controller unplug successfully 

Additional info:
scsi controller can be unplug successfully without migration
Comment 2 jingzhao 2017-05-09 09:19:28 UTC 
src cli [1]
/usr/libexec/qemu-kvm \
-machine q35,smm=on,accel=kvm \
-cpu Haswell-noTSX \
-nodefaults -rtc base=utc \
-m 2G \
-smp 2,sockets=2,cores=1,threads=1 \
-enable-kvm \
-uuid 990ea161-6b67-47b2-b803-19fb01d30d12 \
-k en-us \
-nodefaults \
-serial unix:/tmp/console,server,nowait \
-boot menu=on \
-qmp tcp:0:6666,server,nowait \
-vga qxl \
-chardev file,path=/home/seabios.log,id=seabios -device isa-debugcon,chardev=seabios,iobase=0x402 \
-device pcie-root-port,bus=pcie.0,id=root3 \
-drive file=/home/test/rhel/rhel74.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop \
-device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio-disk0,bus=root3,bootindex=0 \
-device pcie-root-port,bus=pcie.0,id=root0,multifunction=on,chassis=1,addr=0xa.0 \
-device virtio-net-pci,netdev=tap10,mac=9a:6a:6b:6c:6d:6e,bus=root0 -netdev tap,id=tap10 \
-device pcie-root-port,bus=pcie.0,id=root1,multifunction=on,chassis=2,addr=0xa.1 \
-device pcie-root-port,bus=pcie.0,id=root2,slot=2 \
-cdrom /home/test/win/win7/en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso \
-device ahci,id=ahci0 \
-drive file=/usr/share/virtio-win/virtio-win-1.9.0.iso,if=none,id=drive-virtio-disk1,format=raw \
-device ide-cd,drive=drive-virtio-disk1,id=virtio-disk1,bus=ahci0.0 \
-monitor stdio \
-vnc :0 \


dst cli [2]
/usr/libexec/qemu-kvm \
-machine q35,smm=on,accel=kvm \
-cpu Haswell-noTSX \
-nodefaults -rtc base=utc \
-m 2G \
-smp 2,sockets=2,cores=1,threads=1 \
-enable-kvm \
-uuid 990ea161-6b67-47b2-b803-19fb01d30d12 \
-k en-us \
-nodefaults \
-serial unix:/tmp/console,server,nowait \
-boot menu=on \
-qmp tcp:0:6667,server,nowait \
-vga qxl \
-chardev file,path=/home/seabios.log,id=seabios -device isa-debugcon,chardev=seabios,iobase=0x402 \
-device pcie-root-port,bus=pcie.0,id=root3 \
-drive file=/home/test/rhel/rhel74.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop \
-device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio-disk0,bus=root3,bootindex=0 \
-device pcie-root-port,bus=pcie.0,id=root0,multifunction=on,chassis=1,addr=0xa.0 \
-device virtio-net-pci,netdev=tap10,mac=9a:6a:6b:6c:6d:6e,bus=root0 -netdev tap,id=tap10 \
-device pcie-root-port,bus=pcie.0,id=root1,multifunction=on,chassis=2,addr=0xa.1 \
-device pcie-root-port,bus=pcie.0,id=root2,slot=2 \
-device virtio-scsi-pci,id=scsi1,bus=root2 \
-drive file=/home/test/rhel/block1.qcow2,if=none,id=drive_datadisk0,format=qcow2,cache=none,werror=stop,rerror=stop \
-device scsi-hd,drive=drive_datadisk0,id=device_datadisk0,bus=scsi1.0 \
-device virtio-scsi-pci,id=scsi2,bus=root1 \
-drive file=/home/test/rhel/block2.qcow2,if=none,id=drive_datadisk1,format=qcow2,cache=none,werror=stop,rerror=stop \
-device scsi-hd,drive=drive_datadisk1,id=device_datadisk1,bus=scsi2.0 \
-cdrom /home/test/win/win7/en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso \
-device ahci,id=ahci0 \
-drive file=/usr/share/virtio-win/virtio-win-1.9.0.iso,if=none,id=drive-virtio-disk1,format=raw \
-device ide-cd,drive=drive-virtio-disk1,id=virtio-disk1,bus=ahci0.0 \
-monitor stdio \
-vnc :1 \
-incoming tcp:0:5800 \

Thanks
Jing
Comment 4 Fam Zheng 2017-06-14 11:33:48 UTC 
Can this be reproduced with libvirt commands?
Comment 5 Fam Zheng 2017-06-14 13:14:05 UTC 
To answer myself: looks like yes. Seems the same issue with bug 1455150. Marking TestOnly and keeping the flags back in sync. Sorry for the noise.
Note You need to log in before you can comment on or make changes to this bug.