> In your case, you should be able to use
>
>
> qemu64
>
>
>
> to get the same CPU model you'd get by default (if not, you may need to
> also add ).
>
> Alternatively
>
>
> qemu64
>
>
>
> should work too (and it would be better in case you use i
On 05/26/2016 04:41 AM, Jiri Denemark wrote:
The qemu64 CPU model contains svm and thus libvirt will always consider
it incompatible with any Intel CPUs (which have vmx instead of svm). On
the other hand, QEMU by default ignores features that are missing in the
host CPU and has no problem using
On Wed, May 25, 2016 at 23:13:24 -0600, Chris Friesen wrote:
> Hi,
>
> If I don't specify a virtual CPU model, it appears to give me a "qemu64" CPU,
> and /proc/cpuinfo in the guest instance looks something like this:
>
> processor 0
> vendor_id GenuineIntel
> cpu family 6
> model 6
> model name
On Wed, May 25, 2016 at 11:13:24PM -0600, Chris Friesen wrote:
[...]
> However, if I explicitly specify a custom CPU model of "qemu64" the
> instance refuses to boot and I get a log saying:
[Not a direct answer to the exact issue you're facing, but a related
issue that is being investigated pres
