You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That is the same shape QD2 expects when it inspects clipboard support.
124
+
125
+
For libvirt or `virt-manager`, the equivalent XML is a `qemu-vdagent` channel. If the UI does not expose it directly, open the XML editor and add:
126
+
127
+
```xml
128
+
<channeltype='qemu-vdagent'>
129
+
<source>
130
+
<clipboardcopypaste='yes'/>
131
+
</source>
132
+
<targettype='virtio'name='com.redhat.spice.0'/>
133
+
</channel>
134
+
```
135
+
136
+
Inside the guest:
137
+
138
+
- X11 desktops usually need the regular `spice-vdagent` session agent running.
139
+
- Wayland guests, especially Hyprland or wlroots-based sessions, may need a Wayland-native guest agent instead of the traditional X11-focused `spice-vdagent`.
140
+
141
+
For Wayland guests, see [`paprika-vdagent`](https://github.com/thelicato/paprika-vdagent), a standalone Wayland SPICE guest agent that was built specifically for clipboard support without relying on X11 clipboard mirroring.
142
+
143
+
When clipboard still does not work, `qd2 inspect` and `qd2 doctor` are the quickest way to confirm whether QEMU is exporting both the D-Bus clipboard object and the guest-agent channel.
144
+
112
145
## 🌍 Platform Notes
113
146
114
147
- Release artifacts are produced for Linux on both `x86_64` and `arm64`.
0 commit comments