Michael Tokarev
unread,Dec 25, 2023, 4:50:04 PM12/25/23You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to
Control: tag -1 + moreinfo unreproducible
11.12.2023 14:51, Y :
> Package: qemu-guest-agent
> Version: 1:8.1.2+ds-1~bpo12+1
> Severity: serious
> Justification: 6
>
> Dear Maintainer,
>
> The problem arose after upgrading from bullseye to bookworm.
What did you upgrade, host or guest system?
> All was OK on bullseye, but on bookworm qemu-ga refuse to start with
> following messages :
>
> 1702295113.963828: debug: disabling command: guest-get-devices
> 1702295113.963868: critical: error opening channel '/dev/virtio-ports/org.qemu.guest_agent.0': No such file or directory
> 1702295113.963873: critical: failed to create guest agent channel
> 1702295113.963875: critical: failed to initialize guest agent channel
>
> The systemd command looks like :
> [Unit]
> Description=QEMU Guest Agent
> BindsTo=dev-virtio\x2dports-org.qemu.guest_agent.0.device
> After=dev-virtio\x2dports-org.qemu.guest_agent.0.device
This is the standard qga systemd unit file.
This unit file tells systemd to start qemu-ga *only* if
/dev/virtio-ports/org.qemu.guest_agent.0 device is present.
So it is either present and qga will start okay, or it is
not present, and systemd wont start it. But not both.
I can't reproduce this issue, everything looks and works
like it is supposed to look and work.
Also, there are *lots* of bullseye VMs and hosts has been
upgraded to bookworm, and qemu-ga continues to work just
fine.
I've no idea what to get out of all this.
/mjt