Bug 2152079

Summary:	qemuAgentGetDisks cannot parse response from a guest agent running in Windows VM [rhel-8.7.0.z]
Product:	Red Hat Enterprise Linux 8	Reporter:	RHEL Program Management Team <pgm-rhel-tools>
Component:	libvirt	Assignee:	Peter Krempa <pkrempa>
Status:	CLOSED ERRATA	QA Contact:	Lili Zhu <lizhu>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	chhu, jdenemar, lmen, pkrempa, virt-maint, yalzhang, ymankad
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libvirt-8.0.0-10.2.module+el8.7.0+17753+6a6ae27a	Doc Type:	Bug Fix
Doc Text:	Cause: The reply from the guest agent doesn't contain one of the fields when running on windows. The code reports a spurious log entry in such case. Consequence: A safe-to-ignore error log entry is produced, in many times repeatedly. Fix: The code was modified to avoid reporting the error.	Story Points:	---
Clone Of:	2149752	Environment:
Last Closed:	2023-02-21 09:30:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2149752
Bug Blocks:

Comment 7 Lili Zhu 2023-01-08 09:20:42 UTC

Verify this bug with:
libvirt-8.0.0-10.2.module+el8.7.0+17753+6a6ae27a.x86_64

1. prepare a win guest with guest agent device
# virsh domtime win2k19 
Time: 1669923955

2. config the libvirtd conf file
# grep -v ^# /etc/libvirt/libvirtd.conf 
log_outputs = "3:file:/var/log/libvirt/libvirtd.log"

3. restart libvirtd

4. Get guest disk info
# virsh guestinfo win2k19 --disk 
disk.count          : 1
disk.0.name         : \\.\PhysicalDrive0
disk.0.partition    : no
disk.0.serial       : QM00001

5. check the log
# cat /var/log/libvirt/libvirtd.log 
(no output)

As the testing result matches with the expected result. Mark the bug as verified.

Comment 12 errata-xmlrpc 2023-02-21 09:30:41 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 (virt:rhel and virt-devel:rhel bug fix and enhancement update), 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-2023:0845