All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jorge Lucangeli Obes <jorgelo@chromium.org>
Cc: Alexander Graf <agraf@suse.de>, kvm@vger.kernel.org
Subject: Re: Running KVM inside a chroot
Date: Sun, 30 Oct 2011 16:36:09 +0200	[thread overview]
Message-ID: <4EAD60D9.4010808@redhat.com> (raw)
In-Reply-To: <CAKYuF5TXDx2T0QTR3_wE_ut2c4+vL=CX-_uMVqzQrzdFmwHNsg@mail.gmail.com>

On 10/20/2011 05:30 AM, Jorge Lucangeli Obes wrote:
> >>
> >> >> However, running trace-cmd gives:
> >> >>
> >> >> $ trace-cmd report trace_report
> >> >>   error reading header for trace_report
> >> >> jorgelo@tegan:~/local$ trace-cmd report trace.dat > trace_report2
> >> >>   cound not load plugin '/usr/local/share/trace-cmd/plugins/plugin_kvm.so'
> >> >> /usr/local/share/trace-cmd/plugins/plugin_kvm.so: undefined symbol:
> >> >> ud_translate_att
> >> >>
> >> >
> >> > Looks like udis86 isn't loaded correctly, is it installed in /usr/lib[64]?
> >>
> >> $ ls /usr/local/lib/libudis*
> >> /usr/local/lib/libudis86.a  /usr/local/lib/libudis86.la
> >>
> >> Does "/usr/local/lib" vs "/usr/lib" make a difference?
> >
> > Shoudn't.  I have a .so instead of .a, maybe trace-cmd's Makefile isn't
> > prepared for static libraries?
>
> 'configure' doesn't seem to enable building shared libs by default. I
> had to pass '--enable-shared'. Once the shared libs were installed, I
> ran 'ldconfig' and the problem was solved. 

Ok, great.

> I've uploaded a new version
> of the trace report, now generated without any errors. I see lots of:
>
> kvm_exit:             reason EPT_VIOLATION
>
> But maybe that's expected.

Yes, completely normal.

>
> https://docs.google.com/leaf?id=0B78o7gMWkuFeNmJlYzNiNWYtMGQ4MS00NzhiLWIyNTMtY2NlNWEzNzQ5NGYx&hl=en_US
>
> I'll get a trace of the VM outside the chroot to see if there are
> noticeable differences.
>
> Could ksmd have anything to do with this? The daemon is running on my host.
>

It shouldn't, but worth trying to disable it.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-10-30 14:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 18:49 Running KVM inside a chroot Jorge Lucangeli Obes
2011-10-12 19:55 ` Alexander Graf
     [not found]   ` <CAKYuF5TG4+5yaVZh9KX0wLOjjg2h01Maz-VOsr2u4BVHzE8i7g@mail.gmail.com>
2011-10-13  0:51     ` Jorge Lucangeli Obes
2011-10-16 16:23       ` Avi Kivity
2011-10-17  6:10         ` Jorge Lucangeli Obes
2011-10-17  9:56           ` Avi Kivity
2011-10-17 16:37             ` Jorge Lucangeli Obes
2011-10-18 10:29               ` Avi Kivity
2011-10-18 16:43                 ` Jorge Lucangeli Obes
2011-10-18 17:28                   ` Avi Kivity
2011-10-18 17:39                     ` Jorge Lucangeli Obes
2011-10-18 17:46                       ` Avi Kivity
2011-10-20  3:30                         ` Jorge Lucangeli Obes
2011-10-30 14:36                           ` Avi Kivity [this message]
2011-10-30 14:41                           ` Avi Kivity
2011-11-01 16:06                             ` Jorge Lucangeli Obes
2011-11-01 16:29                               ` Gerd Hoffmann
2011-11-01 18:10                                 ` Jorge Lucangeli Obes
2011-11-02  0:12                                   ` Jorge Lucangeli Obes
2011-11-02  8:36                                   ` Gerd Hoffmann
2011-10-19 15:38                 ` David Ahern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EAD60D9.4010808@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=jorgelo@chromium.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.