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 1715724 - The same iommu_group NICs can not be assigned to a Win2019 guest at the same time
Summary: The same iommu_group NICs can not be assigned to a Win2019 guest at the same ...
Keywords:
Status: CLOSED DUPLICATE of bug 1627499
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.0
Assignee: Alex Williamson
QA Contact: Pei Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-31 05:23 UTC by Lei Yang
Modified: 2019-05-31 15:37 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-31 15:37:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lei Yang 2019-05-31 05:23:02 UTC 
Description of problem:
The same iommu_group nic can not be assigned to same Win2019 guest at the same time. But each nic can be assigned individually to Win2019 guest.

Version-Release number of selected component (if applicable):
kernel-4.18.0-80.4.1.el8_0.x86_64
qemu-kvm-3.1.0-27.module+el8.0.1+3253+c5371cb3.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Unbond same iommu_group from host driver to vfio-pci.
# modprobe vfio-pci
# dpdk-devbind --bind=vfio-pci 0000:83:00.0
# dpdk-devbind --bind=vfio-pci 0000:83:00.1

2.Boot Win2019 guest with PFs assigned.
QEMU cli:
/usr/libexec/qemu-kvm -name win2019 \
-M q35,kernel-irqchip=split -m 4G \
-nodefaults \
-cpu Haswell-noTSX \
-device intel-iommu,intremap=true,caching-mode=true \
-smp 4,sockets=1,cores=4,threads=1 \
-device pcie-root-port,id=root.1,chassis=1 \
-device pcie-root-port,id=root.2,chassis=2 \
-device pcie-root-port,id=root.3,chassis=3 \
-device pcie-root-port,id=root.4,chassis=4 \
-device pcie-root-port,id=root.5,chassis=5 \
-blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/win2019_ovmf.qcow2,node-name=my_file \
-drive id=drive_cd1,if=none,snapshot=off,aio=native,cache=none,media=cdrom,file=/home/en_windows_server_2019_updated_march_2019_x64_dvd_2ae967ab.iso \
-blockdev driver=qcow2,node-name=my,file=my_file \
-device virtio-blk-pci,drive=my,id=virtio-blk0,bus=root.1 \
-device ide-cd,id=cd1,drive=drive_cd1,bus=ide.0,unit=0 \
-drive id=drive_winutils,if=none,snapshot=off,aio=native,cache=none,media=cdrom,file=/usr/share/virtio-win/virtio-win-1.9.8.iso \
-device ide-cd,id=winutils,drive=drive_winutils,bus=ide.1,unit=0 \
-vnc :1 \
-vga qxl \
-monitor stdio \
-qmp tcp:0:5555,server,nowait \
-usb -device usb-tablet \
-boot menu=on \
-device vfio-pci,id=pf2,host=83:00.1,bus=root.5,rombar=0 \
-device vfio-pci,id=pf1,host=83:00.0,bus=root.4,rombar=0 \

Actual results:
vfio 0000:83:00.0: group 42 used in multiple address spaces

Expected results:
Win2019 guest can works well.

Additional info:
1.Both OVMF and Seabios have same issue.

2.NIC info:

# lspci |grep Eth
83:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
83:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)

# ls /sys/bus/pci/devices/0000\:83\:00.0/iommu_group/devices/
0000:83:00.0  0000:83:00.1
Comment 2 Alex Williamson 2019-05-31 15:37:24 UTC 
The expectation is wrong here, when a VM is configured with intel-iommu each assigned devices is placed into a separate address space, which is in direct conflict with the vfio model where containers define an address space and the granularity with which we can attach devices to a container is a group.  QEMU does not currently provide DMA aliasing support, which would allow very specific configurations of multiple devices within the same IOMMU group to be attached to a VM configured with intel-iommu when those devices are aliased to the same address space, such as by a conventional PCI bus.

Cloning to relevant RFE, behavior described here matches current expectations.

*** This bug has been marked as a duplicate of bug 1627499 ***
Note You need to log in before you can comment on or make changes to this bug.