-
Bug
-
Resolution: Not a Bug
-
Undefined
-
rhel-9.3.0
-
None
-
None
-
rhel-sst-virtualization-windows
-
ssg_virtualization
-
20
-
22
-
5
-
False
-
-
Yes
-
Red Hat Enterprise Linux
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
None
Version-Release number of selected component (if applicable):
libvirt-10.0.0-1.el9.x86_64
qemu-kvm-8.2.0-2.el9.x86_64
virtio-win-1.9.35-0.el9.noarch
How reproducible:
100%
Steps to Reproduce:
1. prepare a windows guest with guest agent device
# virsh dumpxml win2k19 --xpath //channel <channel type="unix"> <source mode="bind" path="/run/libvirt/qemu/channel/4-win2k19/org.qemu.guest_agent.0"/> <target type="virtio" name="org.qemu.guest_agent.0" state="connected"/> <alias name="channel0"/> <address type="virtio-serial" controller="0" bus="0" port="1"/> </channel>
2. check guest agent function
# virsh domtime win2k19 --pretty Time: 2024-01-14 14:27:59
3. Detach the guest agent device
# cat agent1.xml <channel type="unix"> <source mode="bind" path="/run/libvirt/qemu/channel/4-win2k19/org.qemu.guest_agent.0"/> <target type="virtio" name="org.qemu.guest_agent.0" state="connected"/> <alias name="channel0"/> <address type="virtio-serial" controller="0" bus="0" port="1"/> </channel> # virsh detach-device win2k19 agent1.xml Device detached successfully # virsh dumpxml win2k19 --xpath //channel (No output)
4. Attach the following guest agent device to guest
# cat agent.xml <channel type='unix'> <source mode='bind' /> <target type='virtio' name='org.qemu.guest_agent.0'/> </channel> # virsh attach-device win2k19 agent.xml Device attached successfully # virsh dumpxml win2k19 --xpath //channel <channel type="unix"> <source mode="bind" path="/run/libvirt/qemu/channel/4-win2k19/org.qemu.guest_agent.0"/> <target type="virtio" name="org.qemu.guest_agent.0"/> <alias name="channel0"/> <address type="virtio-serial" controller="0" bus="0" port="1"/> </channel> (No state element) # virsh domtime win2k19 error: Guest agent is not responding: QEMU guest agent is not connected
5. check the log
# grep -rni VSERPORT_CHANGE /var/log/libvirt/libvirtd.log
(no output)
{no output like:
# grep -rni VSERPORT_CHANGE /var/log/libvirt/libvirtd.log
4471:2024-01-18 03:19:30.906+0000: 20646: debug : qemuMonitorJSONIOProcessLine:191 : Line [{"timestamp": {"seconds": 1705547970, "microseconds": 906055}, "event": "VSERPORT_CHANGE", "data": {"open": true, "id": "channel0"}}]
4472:2024-01-18 03:19:30.906+0000: 20646: debug : virJSONValueFromString:1666 : string={"timestamp": {"seconds": 1705547970, "microseconds": 906055}, "event": "VSERPORT_CHANGE", "data": {"open": true, "id": "channel0"}}
4492:2024-01-18 03:19:30.906+0000: 20646: info : qemuMonitorJSONIOProcessLine:205 : QEMU_MONITOR_RECV_EVENT: mon=0x7f44e4044010 event={"timestamp": {"seconds": 1705547970, "microseconds": 906055}, "event": "VSERPORT_CHANGE", "data": {"open": true, "id": "channel0"}}
}
Actual result:
Guest agent device can not be connected
Expected result:
Guest agent device can be connected
Additional info:
1. Hotplug guest agent device to Windows guest without agent device before works normal
2. Hotplug guest agent device to Linux guest after detach guest agent device works normal
