On Wed, Dec 31, 2025 at 08:30:59PM -0800, Paul B. Henson wrote:
> I guess I'll compile a custom kernel with the viocon driver enabled and
> see what happens.
Hmm, with the driver enabled it finds the port:
virtio5 at pci0 dev 12 function 0 "Qumranet Virtio Console" rev 0x00
viocon0 at virtio5
and the device file is active:
# stty -a -f /dev/ttyVI00
speed 1000000 baud; 0 rows; 0 columns;
qemu-ga starts successfully connecting to that port:
# qemu-ga -v -m virtio-serial -p /dev/ttyVI00
1767479353.529997: debug: Guest agent version 10.0.2 started
but libvirt says it's not connected:
# virsh qemu-agent-command obsd '{"execute":"guest-ping"}'
error: Guest agent is not responding: QEMU guest agent is not connected
Something's off though; in my libvirt config I have a virtio-serial
controller defined:
<controller type='virtio-serial' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/>
</controller>
and a qemu agent channel:
<channel type='unix'>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
If I remove the channel definition, the kernel still finds the
controller and /dev/ttyVI00 is still active. So that device doesn't seem
to be connected to the channel libvirt expects the agent to be on?
/dev/ttyVI01 isn't active. Dunno, maybe the driver is disabled because
it's not fully baked yet <sigh>.
