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: Tue, 18 Oct 2011 12:29:35 +0200 [thread overview]
Message-ID: <4E9D550F.9030400@redhat.com> (raw)
In-Reply-To: <CAKYuF5SxQNk_G0--me4dUXoHW0iSec89P1MzHsrwkepnQCcnrg@mail.gmail.com>
On 10/17/2011 06:37 PM, Jorge Lucangeli Obes wrote:
> On Mon, Oct 17, 2011 at 2:56 AM, Avi Kivity <avi@redhat.com> wrote:
> > On 10/17/2011 08:10 AM, Jorge Lucangeli Obes wrote:
> >> > What do top/vmstat/kvm_stat say?
> >>
> >> I'm attaching the output of the three commands during a test run
> >> launched form inside the chroot, which was slow as usual. I didn't see
> >> anything too weird on top/vmstat, though I found it odd that once the
> >> VM had booted Chromium OS, QEMU still ate 100% of one core. vmstat
> >> didn't show anything strange, QEMU taking up the memory it's supposed
> >> to. What I don't quite know how to interpret is the output of
> >> kvm_stat, hence the attachment.
> >>
> >>
> >
> > kvm_stat shows insane instruction emulation counts. Please post a trace
> > as described in http://www.linux-kvm.org/page/Tracing.
>
> I've uploaded a bzip'd trace here:
>
> https://docs.google.com/leaf?id=0B78o7gMWkuFeMzM3MWM5NmUtYTY3My00ZDkxLTljZmUtYjRhMWRhOWVjZTZh&hl=en_US
>
> Almost all the exits show "[FAILED TO PARSE]", would this be a problem?
>
Did you 'make install' trace-cmd? run it from outside the chroot.
You're showing be a trace of the boot process, please start the trace
after the guest is idle (but consuming lots of cpu).
What host kernel version are you running?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-10-18 10:29 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 [this message]
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
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=4E9D550F.9030400@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.