Differences

This shows you the differences between two versions of the page.

--- computing:virtmanagerhell [2026/03/29 16:25] – oemb1905
+++ computing:virtmanagerhell [2026/08/15 10:01] (current) – oemb1905
@@ Line 317: / Line 317: @@
   sudo systemctl start serial-getty@ttyS0.service
-Next topic ...
+Migrating an existing VDD and virsh instance ... just dump or copy paste the .xml with ''virsh dump'' or ''virsh edit'', then create a new xml file, typically in ''/var/lib/libvirtd/qemu'', then run:
- --- //[[alerts@haacksnetworking.org|oemb1905]] 2026/03/29 16:18//
+  virsh define host.com.xml
+  virsh start host.com
+You should for sure check the network interface and MAC address, the storage location directory, and obviously run through anything else that might be different on the target migration host. Sometimes, virsh fails to shutdown using the agent method because the agent crashes. Instead of restarting, the agent stays crashed because virsh binds it to a specific socket. To change that, keep ''Bind To='' blank and change the systemd unit as follows:
+<code>
+cat > /usr/lib/systemd/system/qemu-guest-agent.service << 'EOF'
+[Unit]
+Description=QEMU Guest Agent
+BindsTo=
+Wants=dev-virtio\x2dports-org.qemu.guest_agent.0.device
+After=dev-virtio\x2dports-org.qemu.guest_agent.0.device
+Conflicts=shutdown.target
+Before=shutdown.target
+[Service]
+ExecStart=/usr/sbin/qemu-ga
+Restart=always
+RestartSec=3s
+[Install]
+WantedBy=multi-user.target
+EOF
+systemctl daemon-reload
+systemctl restart qemu-guest-agent
+</code>
+I am testing this still but it takes time. The agents only crash after extended use, so letting everything run while this is in production, then checking back up logs later and seeing if there was improvement on the few problem instances.
+ --- //[[alerts@haacksnetworking.org|oemb1905]] 2026/08/15 09:59//

Haack's Wiki

User Tools

Site Tools

Differences

Page Tools