📖 ~1 min read
Table of contents
Symptom & Impact
`virsh start` aborts with unsupported CPU model after a hypervisor migration.
Environment & Reproduction
Observed when moving VMs between SLES 15 hypervisors with different CPU generations.
Root Cause Analysis
Guest XML pins a CPU model not present on the destination host.
Quick Triage
Inspect host CPU capabilities with `virsh capabilities` and compare to guest XML.
Step-by-Step Diagnosis
Open the guest definition with `virsh edit` and review “ settings.

Solution – Primary Fix
Switch CPU mode to `host-model` or `host-passthrough` for portability, then start guest.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Pin guests to compatible hypervisors via Salt grain or labels.
Verification & Acceptance Criteria
Guest starts cleanly and `virsh list –all` reports it running.
Rollback Plan
Restore the prior XML if the new mode triggers application-level CPU feature errors.
Prevention & Hardening
Standardise CPU model strategy across the cluster and document migrations.
Related Errors & Cross-Refs
Pairs with libvirt `qemu unsupported configuration` errors.
Related tutorial: View the step-by-step tutorial for sles-15.
View all sles-15 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SUSE Virtualization Guide and libvirt CPU model documentation.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.