-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
None
-
libvirt-10.0.0-3.el9
-
None
-
None
-
ZStream
-
rhel-sst-virtualization
-
ssg_virtualization
-
26
-
None
-
Dev ack
-
False
-
-
None
-
Red Hat OpenStack Services on OpenShift (formerly Red Hat OpenStack Platform)
-
None
-
Approved Blocker
-
Pass
-
RegressionOnly
-
None
(This issue is based on an OSP 17.0 bug report by Alex Stupnikov:
"Nova errors out due to libvirt failing to parse PCI device VPD (virtual private data" — https://bugzilla.redhat.com/show_bug.cgi?id=2259641)
Description
---------------
This is a hardware-specific bug; libvirt failing to parse PCI device VPD (virtual private data) for some hardware:
<vendor_field index='Z'>6<1</vendor_field>
Which results in:
lxml.etree.XMLSyntaxError: StartTag: invalid element name
Root cause
---------------
Daniel Berrangé and Peter Krempa from libvirt confirmed that it's a libvirt bug.
Dan writes: "we (libvirt) are using virBufferAsprintf instead of virBufferEscapeString"
So the issue here to be libvirt not escaping a string.
Version details
--------------------
Affected versions (from the OSP container running the libvirt daemon and the guests):
$ podman exec -it nova_virtqemud virsh version Compiled against library: libvirt 9.0.0 Using library: libvirt 9.0.0 Using API: QEMU 9.0.0 Running hypervisor: QEMU 7.2.0}}
- is cloned by
-
RHEL-22396 libvirt failing to parse PCI device VPD (virtual private data) for some hardware
- Closed
- is duplicated by
-
RHEL-22396 libvirt failing to parse PCI device VPD (virtual private data) for some hardware
- Closed
- links to
-
RHBA-2023:125049 libvirt bug fix and enhancement update
- mentioned on