Re: [libvirt] [PATCH] qemu: Refresh caps cache after booting a different kernel

2018-01-30 Thread Peter Krempa
On Tue, Jan 30, 2018 at 13:26:49 +0300, Nikolay Shirokovskiy wrote: > > > On 22.01.2018 15:36, Daniel P. Berrange wrote: > > On Mon, Jan 22, 2018 at 01:31:21PM +0100, Jiri Denemark wrote: > >> On Mon, Jan 22, 2018 at 10:57:57 +, Daniel P. Berrange wrote: > >>> On Mon, Jan 22, 2018 at

Re: [libvirt] [PATCH] qemu: Refresh caps cache after booting a different kernel

2018-01-30 Thread Nikolay Shirokovskiy
On 22.01.2018 15:36, Daniel P. Berrange wrote: > On Mon, Jan 22, 2018 at 01:31:21PM +0100, Jiri Denemark wrote: >> On Mon, Jan 22, 2018 at 10:57:57 +, Daniel P. Berrange wrote: >>> On Mon, Jan 22, 2018 at 11:46:14AM +0100, Jiri Denemark wrote: Whenever a different kernel is booted, some

Re: [libvirt] [PATCH] qemu: Refresh caps cache after booting a different kernel

2018-01-22 Thread Daniel P. Berrange
On Mon, Jan 22, 2018 at 01:31:21PM +0100, Jiri Denemark wrote: > On Mon, Jan 22, 2018 at 10:57:57 +, Daniel P. Berrange wrote: > > On Mon, Jan 22, 2018 at 11:46:14AM +0100, Jiri Denemark wrote: > > > Whenever a different kernel is booted, some capabilities related to KVM > > > (such as CPUID

Re: [libvirt] [PATCH] qemu: Refresh caps cache after booting a different kernel

2018-01-22 Thread Jiri Denemark
On Mon, Jan 22, 2018 at 10:57:57 +, Daniel P. Berrange wrote: > On Mon, Jan 22, 2018 at 11:46:14AM +0100, Jiri Denemark wrote: > > Whenever a different kernel is booted, some capabilities related to KVM > > (such as CPUID bits) may change. We need to refresh the cache to see the > > changes. >

Re: [libvirt] [PATCH] qemu: Refresh caps cache after booting a different kernel

2018-01-22 Thread Daniel P. Berrange
On Mon, Jan 22, 2018 at 11:46:14AM +0100, Jiri Denemark wrote: > Whenever a different kernel is booted, some capabilities related to KVM > (such as CPUID bits) may change. We need to refresh the cache to see the > changes. > > Signed-off-by: Jiri Denemark > --- > > Notes: >

[libvirt] [PATCH] qemu: Refresh caps cache after booting a different kernel

2018-01-22 Thread Jiri Denemark
Whenever a different kernel is booted, some capabilities related to KVM (such as CPUID bits) may change. We need to refresh the cache to see the changes. Signed-off-by: Jiri Denemark --- Notes: The capabilities may also change if a parameter passed to a kvm module