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

[Guido Günther]

Hi Jiri,
On Fri, Sep 18, 2015 at 03:53:02PM +0200, Jiri Denemark wrote:
> On Fri, Sep 18, 2015 at 00:38:31 +0200, Nikolaus Schulz wrote:
> > On Tue, Sep 08, 2015 at 04:28:10PM +0200, Jiri Denemark wrote:
> > > Interesting, so it seems syscall feature is missing in both cases, which
> > > is why libvirt detects the CPU as n270 or coreduo (all new CPU models
> > > require syscall feature). Would you mind attaching the output of the
> > > "cpuid -1r" command?
> > 
> > Attached.
> 
> Thanks, the attached file confirms the CPU does not support syscall.
> Which means libvirt is correct in this part, I will play more with the
> data to look into the vendor issue.
> 
> > 
> > > Could you also set log_filters="1:cpu 1:qemu 1:daemon" in
> > > /etc/libvirt/libvirtd.conf, restart libvirtd and attach libvirtd.log?
> > 
> > Ditto.  Note that I temporarily upgraded to libvirt 1.2.19 for this, the
> > larger part of the log before that is still with 1.2.16.
> 
> Hmm, the log doesn't contain any debug messages. Did you change
> log_filters settings as suggested? And if so, does log_outputs look
> similar to
> 
>     log_outputs="1:file:/var/log/libvirt/libvirtd.log"
> 
> (note the "1" at the beginning)?

Debian does not build with --enable-debug at the moment so the
VIR_DEBUG_INT is stubbed out. Looking at the spec file it seems
Fedora doesn't enable it either.

I already wondered ad debconf if it wouldn't be better if distros
would build with debugging enabled?

Cheers
 -- Guido