[Pkg-libvirt-maintainers] Bug#797513: Bug#797513: Regression in support for custom CPU configuration

[Nikolaus Schulz]

On Tue, Sep 01, 2015 at 01:27:30PM +0200, Guido Günther wrote:
> On Tue, Sep 01, 2015 at 11:40:52AM +0100, Ben Hutchings wrote:
> > > I'd be keen to know what the <vendor> element says. I retried on a
> > > Westmere and the CPU type is detected correctly.
> 
> It's indeed lacking the vendor attribute. I have:
> 
>   $ virsh capabilities | xpath -q -e //host/cpu/vendor
>   <vendor>Intel</vendor>
> 
> while yours is empty which seems to be the regression.

Again, same here.  I've downgraded libvirt to 1.2.16 again, and here's
the delta for the capabilities host node:

--- virsh-cap-1.2.16.xml	2015-09-02 00:20:50.989297520 +0200
+++ virsh-cap-1.2.19.xml	2015-09-02 00:19:58.709038277 +0200
@@ -1,10 +1,20 @@
 <host>
-    <uuid>638c5e1e-b80b-4ae0-a519-73a90ca4c1ad</uuid>
+    <uuid>8c1ecff4-070d-4374-94f0-ce62022e53db</uuid>
     <cpu>
       <arch>i686</arch>
       <model>coreduo</model>
-      <vendor>Intel</vendor>
       <topology sockets="1" cores="2" threads="1" />
+      <feature name="avx512cd" />
+      <feature name="avx512pf" />
+      <feature name="adx" />
+      <feature name="rdseed" />
+      <feature name="avx512f" />
+      <feature name="invpcid" />
+      <feature name="bmi2" />
+      <feature name="smep" />
+      <feature name="avx2" />
+      <feature name="hle" />
+      <feature name="bmi1" />
       <feature name="pdcm" />
       <feature name="xtpr" />
       <feature name="tm2" />

The features avx512cd..bmi1 are actually *not* supported by my old Core
Duo T2400 CPU, and libvirt 1.2.16 rightly complains about that if I feed
it such a cpu definition on my box.

> Can you check
> syslog if there are any warnings or errors printed during libvirt
> startup? If not I'm a bit puzzled since nothing changed recently in
> this area.

I have no libvirt related errors in my log.

Regards,
Nikolaus.