Hi all,
Quick FYI. If you ever get the above panic on a KVM VM, you should
probably fix your hypervisor configuration.
Today I upgraded two VMs to the latest snapshot. They hadn't been
upgraded for some time, and they didn't come up after reboot. Turns
out, the CPU configuration on the hypervisor presented a weird
combination of cpuid levels and feature flags, the thing you get with
the "Limit CPUID" thing in BIOSes. Moving to host passthrough fixed
things.
This snippet worked (at least, for my two VMs, which run under
libvirt):
<cpu mode='host-passthrough' check='none' migratable='on'/>
Hope this helps someone running into the same :)
Cheers,
Paul 'WEiRD' de Weerd
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
