Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
libvirt release the RNG device address on successful RNG attach
Version-Release number of selected component (if applicable):
libvirt-1.2.15-2.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. attach a RNG device:
# cat rng.xml
<rng model='virtio'>
<backend model='random'>/dev/random</backend>
</rng>
# virsh attach-device test3 rng.xml
Device attached successfully
2. attach some device use pci address until meet this error:
# while :; do virsh attach-device test3 rng.xml; done
...
error: Failed to attach device from rng.xml
error: internal error: unable to execute QEMU command 'device_add': PCI: slot 8 function 0 not available for virtio-rng-pci, in use by virtio-rng-pci
3.
Actual results:
libvirt will try to use a address already used by other RNG device, this is because we release the address on successful attach, then this address can be used again (but qemu will forbid this, so we got the error).
Expected results:
do not release the RNG device address on successful RNG attach
Additional info:
This commit could fix this issue:
commit 0ed3b3353593792da2104dd3b8a27a2b6a240300
Author: Luyao Huang <lhuang>
Date: Sun May 31 19:29:46 2015 +0800
qemu: Do not release device address on successful RNG attach
Commit id '980b265d' neglected to check for a successful status when
deciding whether to release the device address for the RNG attach thus
the address would be released even though the device was added.
Signed-off-by: Luyao Huang <lhuang>
v1.2.16-29-g0ed3b33
I can produce this bug with build libvirt-1.2.15-2.el7.x86_64
Verify this bug with build libvirt-1.2.17-1.el7.x86_64
1. prepare a guest without rng device
2. # cat rng.xml
<rng model='virtio'>
<backend model='random'>/dev/random</backend>
</rng>
3. attach rng device to guest on line
# while true; do virsh attach-device r7 rng.xml; done
Device attached successfully
Device attached successfully
...
...
error: Failed to attach device from rng.xml
error: internal error: No more available PCI slots
error: Failed to attach device from rng.xml
error: internal error: No more available PCI slots
...
4. check guest with rng device have been attached successful
move to verified
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://rhn.redhat.com/errata/RHBA-2015-2202.html
Description of problem: libvirt release the RNG device address on successful RNG attach Version-Release number of selected component (if applicable): libvirt-1.2.15-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. attach a RNG device: # cat rng.xml <rng model='virtio'> <backend model='random'>/dev/random</backend> </rng> # virsh attach-device test3 rng.xml Device attached successfully 2. attach some device use pci address until meet this error: # while :; do virsh attach-device test3 rng.xml; done ... error: Failed to attach device from rng.xml error: internal error: unable to execute QEMU command 'device_add': PCI: slot 8 function 0 not available for virtio-rng-pci, in use by virtio-rng-pci 3. Actual results: libvirt will try to use a address already used by other RNG device, this is because we release the address on successful attach, then this address can be used again (but qemu will forbid this, so we got the error). Expected results: do not release the RNG device address on successful RNG attach Additional info: This commit could fix this issue: commit 0ed3b3353593792da2104dd3b8a27a2b6a240300 Author: Luyao Huang <lhuang> Date: Sun May 31 19:29:46 2015 +0800 qemu: Do not release device address on successful RNG attach Commit id '980b265d' neglected to check for a successful status when deciding whether to release the device address for the RNG attach thus the address would be released even though the device was added. Signed-off-by: Luyao Huang <lhuang> v1.2.16-29-g0ed3b33