On 01/23/2012 05:03 PM, Daniel P. Berrange wrote:
> > The qemu32/qemu64 models are weird in that the exact combination of
> > CPUID flags does not match any actual processor. kvm32 and kvm64 are
> > a better match when not using TCG. Use them when -cpu is only needed
> > to hardcode a 32-bit guest arch or for kvmclock.
>
> I don't think we can do this as it means the guest CPU may change
unexpectedly
> for existing domains. A 32b domain started on current libvirt would see
qemu32,
> while the same domain started after this patch would see kvm32.
Also, IIUC, kvm32 is a fairly newly introduced CPU type for KVM - ie most
deployments of KVM won't support it.
Ok, I'll redo this patch with just kvm64. As the wrong subject in 0/3
show, it was an afterthought.
As soon as I get the review of 3/4, I'll see whether I need to resubmit
the whole series or just this patch.
Paolo
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
