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 1801139 - can't start two guests with passthrough of an iscsi lun with "shareable" element
Summary: can't start two guests with passthrough of an iscsi lun with "shareable" element
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.8
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Ján Tomko
QA Contact: gaojianan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-10 10:50 UTC by gaojianan
Modified: 2020-03-31 19:59 UTC (History)
8 users (show)

Fixed In Version: libvirt-4.5.0-33.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 19:59:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Libvirtd log (218.67 KB, text/plain)
2020-02-10 10:50 UTC, gaojianan 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1094 0 None None None 2020-03-31 19:59:44 UTC

Description gaojianan 2020-02-10 10:50:25 UTC 
Created attachment 1662115 [details]
Libvirtd log

Description of problem:
As subject

Version-Release number of selected component (if applicable):
libvirt-4.5.0-32.virtcov.el7.x86_64
qemu-kvm-rhev-2.12.0-44.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare an iscsi server and login the target in the host
# iscsiadm -m session
tcp: [1] 10.66.85.243:3260,1 iqn.2015-01.com.fred:444 (non-flash)
tcp: [2] 10.66.85.243:3260,1 iqn.2016-03.com.virttest:logical-pool.target6 (non-flash)

# lsscsi
...
[5:0:0:0]    disk    LIO-ORG  device.logical-  4.0   /dev/sdc 

2.Passthrough the disk to two guests
For the 1st :
# cat attach.xml 
<hostdev managed="no" mode="subsystem" type="scsi">
<source>
<adapter name="scsi_host5" />
<address bus="0" target="0" unit="0" />
</source>
<shareable/>             --------------with shareable
</hostdev>

# virsh attach-device vm2 attach.xml                                                                                                                                                                         
Device attached successfully

For the 2nd with the same xml:
# virsh attach-device avocado-vt-vm1 attach.xml
error: Failed to attach device from attach.xml
error: Failed to read file '/dev/sdc': Value too large for defined data type

3.In the 2nd guest,you can also hit the issue by:
# virsh attach-device avocado-vt-vm1 attach.xml --config
Device attached successfully

# virsh start avocado-vt-vm1
error: Failed to start domain avocado-vt-vm1
error: Failed to read file '/dev/sdc': Value too large for defined data type

Actual results:
As step 2 and 3

Expected results:
The 2nd guest should be started without error

Additional info:
Comment 9 gaojianan 2020-02-14 11:22:35 UTC 
Verified on:
libvirt-4.5.0-33.el7.x86_64
qemu-kvm-rhev-2.12.0-44.el7.x86_64

Sc1:hot-plug the device to two guests
1.Prepare an iscsi server and login the target in the host
# iscsiadm -m session
tcp: [1] 10.66.85.243:3260,1 iqn.2015-01.com.fred:444 (non-flash)
tcp: [2] 10.66.85.243:3260,1 iqn.2016-03.com.virttest:logical-pool.target6 (non-flash)

# lsscsi
...
[5:0:0:0]    disk    LIO-ORG  device.logical-  4.0   /dev/sdc 

2.Passthrough the disk to two guests
For the 1st :
# cat attach.xml 
<hostdev managed="no" mode="subsystem" type="scsi">
<source>
<adapter name="scsi_host5" />
<address bus="0" target="0" unit="0" />
</source>
<shareable/>             --------------with shareable
</hostdev>

# virsh attach-device vm2 attach.xml                                                                                                                                                                         
Device attached successfully

For the 2nd with the same xml:
# virsh attach-device avocado-vt-vm1 attach.xml
Device attached successfully

Login the guest ,the disk works well

Sc2:cold-plug the device to two guests:
# virsh attach-device avocado-vt-vm1 attach.xml --config 
Device attached successfully

# virsh attach-device vm2 attach.xml --config 
Device attached successfully

# virsh start vm2
Domain vm2 started

# virsh start avocado-vt-vm1 
Domain avocado-vt-vm1 started

and then detach the device and attach again,
# virsh detach-device vm2 attach.xml 
Device detached successfully

# virsh attach-device vm2 attach.xml 
Device attached successfully

Work as expected
Comment 12 errata-xmlrpc 2020-03-31 19:59:02 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1094
Note You need to log in before you can comment on or make changes to this bug.