On Sun, Dec 02, 2012 at 04:26:41PM +0100, Nikola Ciprich wrote:
> > hmm, that should be OK, new kvm*.ko modules are part of kernel rpm package,
> > there's no old module there. (I checked by both inspecting kernel pkg and
> > using modinfo)... Could it be something else?
>
> hmm, I can reply to my
On Sun, Dec 02, 2012 at 04:10:10PM +0100, Nikola Ciprich wrote:
> > I think you need to copy them over old modules in /lib/modules.
>
> hmm, that should be OK, new kvm*.ko modules are part of kernel rpm package,
> there's no old module there. (I checked by both inspecting kernel pkg and
> using mo
> hmm, that should be OK, new kvm*.ko modules are part of kernel rpm package,
> there's no old module there. (I checked by both inspecting kernel pkg and
> using modinfo)... Could it be something else?
hmm, I can reply to myself this time - perf seems to get the symbols using
/proc/kallsyms and th
> I think you need to copy them over old modules in /lib/modules.
hmm, that should be OK, new kvm*.ko modules are part of kernel rpm package,
there's no old module there. (I checked by both inspecting kernel pkg and
using modinfo)... Could it be something else?
>
> --
> Gl
On Sun, Dec 02, 2012 at 03:51:53PM +0100, Nikola Ciprich wrote:
> > More like loaded modules/installed modules mismatch.
> I see, the problem is, that I've got kvm-kmod compiled separately!
> thus kvm*.ko symboles don't match!
> I see that kvm-kmod build produces System.map file, I guess I need to
> More like loaded modules/installed modules mismatch.
I see, the problem is, that I've got kvm-kmod compiled separately!
thus kvm*.ko symboles don't match!
I see that kvm-kmod build produces System.map file, I guess I need to
merge it with kernel's System.map?
--
On Sun, Dec 02, 2012 at 03:31:08PM +0100, Nikola Ciprich wrote:
> Hi Gleb,
>
> > Something wrong with your symbols. This function cannot take that much.
> > It is three and a half instruction long and should be called only once
> > during vm startup.
>
> well, it didn't make any sense to me, glad
Hi Gleb,
> Something wrong with your symbols. This function cannot take that much.
> It is three and a half instruction long and should be called only once
> during vm startup.
well, it didn't make any sense to me, glad I wasn't that wrong :)
how could that be? I guess it could be perf/kernel mis
On Sun, Dec 02, 2012 at 12:41:37PM +0100, Nikola Ciprich wrote:
> Hi,
>
> while trying to find source of KVM guest slowness, I noticed following in
> perf top:
>
> 326.00 19.6% vmx_set_supported_cpuid
> /lib/modules/3.0.53lb6.02/kernel/arch/x86/kvm/kvm-intel
Hi,
while trying to find source of KVM guest slowness, I noticed following in perf
top:
326.00 19.6% vmx_set_supported_cpuid
/lib/modules/3.0.53lb6.02/kernel/arch/x86/kvm/kvm-intel.ko
108.00 6.5% kvm_arch_dev_ioctl
10 matches
Mail list logo