I'm just beginning to look into why my KVM VM won't start, but I thought I should post what I think I know thus far.
Yesterday (6 JUL) five of the libvirt 3.0.0-4 packages were updated to 3.5.0-1. Today I'm seeing the attached error when I try to start my Win 10 VM.
But my CPU does have those flags:
don@Hibiscus:~$ cat /proc/cpuinfo | grep flags
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm xsaveopt dtherm ida arat pln pts
My initial googling suggests this is a regression of
this bug. But I'm far from a code analyst.
Rather than attempting the configuration workaround, I'm going to wait a bit and see if the developers fix it.
EDIT: I removed the updated packages from 6 JUL (which pulled out virt-manager and virt-viewer), stopped the libvirtd service, reinstalled the 3.0.0-4 versions from the stable repo, set them on hold, reinstalled virt-manager and virt-viewer, restarted libvirtd, and my VM is up and running again.