mait.sh1.69.2

Private beta: features and content may change. No warranty; use at your own risk.

Docs / MCP tool

MCP Libvirt problems and fixes

Tell a wrong working set from a host or guest failure, and recover without a second failure.

Record the connection, the VM identity and the returned result before acting again.

Creation and deletion have several stages, so a failure can leave part of the work done.

Help
All troubleshooting

Start with identity and the exact result

Record the selected connection, the VM or resource identity, the operation and the result. For a snapshot or checkpoint, also record its VM. This separates an operation on the wrong working set from a host or guest failure.

Common outcomes

SymptomNext step
A new session lists no VMsInspect the intended VM and adopt it when authorized
A snapshot name is ambiguousSelect the intended domain_id; names are unique per VM
An inactive-only operation fails after shutdownLet the guest reach Shutoff first
A marked base refuses to startWork in a clone, or review whether starting the source is right
Provisioning failed but the disk existsInspect the partial artifacts before retrying
Snapshot delete kept filesRead the retained paths; preserve backing files
Domain deletion reports a disk errorInspect the remaining volume; the definition can already be gone
A checkpoint has no restore pointDirty tracking is not a backup; find a matching backup
Passthrough returned a non-zero exitRead its diagnostics and the current state
A request timed outObserve the resource before another change
Symptom
A new session lists no VMs
Next step
Inspect the intended VM and adopt it when authorized
Symptom
A snapshot name is ambiguous
Next step
Select the intended domain_id; names are unique per VM
Symptom
An inactive-only operation fails after shutdown
Next step
Let the guest reach Shutoff first
Symptom
A marked base refuses to start
Next step
Work in a clone, or review whether starting the source is right
Symptom
Provisioning failed but the disk exists
Next step
Inspect the partial artifacts before retrying
Symptom
Snapshot delete kept files
Next step
Read the retained paths; preserve backing files
Symptom
Domain deletion reports a disk error
Next step
Inspect the remaining volume; the definition can already be gone
Symptom
A checkpoint has no restore point
Next step
Dirty tracking is not a backup; find a matching backup
Symptom
Passthrough returned a non-zero exit
Next step
Read its diagnostics and the current state
Symptom
A request timed out
Next step
Observe the resource before another change

The console works but a guest service does not

A running VM, a console and a reachable guest service are separate outcomes. Confirm the guest booted, then that SSH, RDP or Screen Sharing is enabled in the guest and that the network provides a route. A listener address can describe a host binding rather than an address a remote client can use.

Avoid turning recovery into a second failure

Do not delete a retained disk because it is no longer the top image: another disk can depend on it. Do not repeat a failed create blindly: the first attempt may have created storage. Use the detailed report to see what changed and what remains.

What you getThe VM, disk or snapshot you meant, in a known state, with backing files preserved.