Hi, I was doing integration testing on the current 4.3.0-pre repository which is planned to be released today as RC3 and i can't start a newly created VM: *Bug 1669102* <https://bugzilla.redhat.com/show_bug.cgi?id=1669102> - can't start VM qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NU MA mappings is obsoleted and will be removed in future can you please have a look? I've the system available for further investigations.

Milan Zamazal <mzamazal(a)redhat.com&gt; writes: > Sandro Bonazzola <sbonazzo(a)redhat.com&gt; writes: > >> Hi, >> I was doing integration testing on the current 4.3.0-pre repository which >> is planned to be released today as RC3 and i can't start a newly created VM: >> >> *Bug 1669102* <https://bugzilla.redhat.com/show_bug.cgi?id=1669102> - can't >> start VM qemu-kvm: warning: All CPU(s) up to maxcpus should be described in >> NUMA config, ability to start up with partial NU MA mappings is obsoleted >> and will be removed in future >> >> can you please have a look? I've the system available for further >> investigations. > > I can reproduce the error, see > https://bugzilla.redhat.com/show_bug.cgi?id=1669102#c3 > > The problem is: > > qemu-kvm: can't apply global SandyBridge-x86_64-cpu.hv-synic=on: Property '.hv-synic' not found > > It looks like some problem with hyperv settings. I guess it is https://bugzilla.redhat.com/show_bug.cgi?id=1644693#c4 and https://bugzilla.redhat.com/show_bug.cgi?id=1644693#c7 .