Re: [libvirt] [PATCH v3 00/52] qemu: Store default CPU in domain XML

2019-11-11 Thread Jiri Denemark
On Fri, Nov 08, 2019 at 12:25:06 +0100, Christian Borntraeger wrote: > As discussed, does it make sense to add the default change to host-model for > s390 > in this series or should that be a separate patch? Originally I wanted to do it as a separate patch, but since no review has apparently

Re: [libvirt] [PATCH v3 00/52] qemu: Store default CPU in domain XML

2019-11-08 Thread Christian Borntraeger
As discussed, does it make sense to add the default change to host-model for s390 in this series or should that be a separate patch? On 05.11.19 14:26, Jiri Denemark wrote: > When starting a domain without a CPU model specified in the domain XML, > QEMU will choose a default one. Which is fine

[libvirt] [PATCH v3 00/52] qemu: Store default CPU in domain XML

2019-11-05 Thread Jiri Denemark
When starting a domain without a CPU model specified in the domain XML, QEMU will choose a default one. Which is fine unless the domain gets migrated to another host because libvirt doesn't perform any CPU ABI checks and the virtual CPU provided by QEMU on the destination host can differ from the