All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: jieryn@gmail.com
Cc: kvm-devel@lists.sourceforge.net, Ryan Harper <ryanh@us.ibm.com>
Subject: Re: KVM and WinPE failure
Date: Fri, 7 Mar 2008 08:49:04 -0600	[thread overview]
Message-ID: <20080307144903.GB11057@us.ibm.com> (raw)
In-Reply-To: <eab08af20803061602j1e8f3924q6a2afcad124a8a1@mail.gmail.com>

* jieryn@gmail.com <jieryn@gmail.com> [2008-03-06 18:03]:
> On Thu, Mar 6, 2008 at 6:19 PM, Ryan Harper <ryanh@us.ibm.com> wrote:
> 
> >
> > (dethklok) kvm-63 % ./kvm_stat
> > Please mount debugfs ('mount -t debugfs debugfs /sys/kernel/debug')
> > and ensure the kvm modules are loaded
> > (dethklok) kvm-61 % sudo mount -t debugfs debugfs /sys/kernel/debug
> >
> > then run ./kvm_stat again
> >
> >
> jesse@indigo ~ $ lsmod | fgrep kvm
> kvm_intel              34272  1
> kvm                   138120  1 kvm_intel
> jesse@indigo ~ $ mount | fgrep debug
> debugfs on /sys/kernel/debug type debugfs (rw)
> jesse@indigo ~ $ kvm_stat
> Please mount debugfs ('mount -t debugfs debugfs /sys/kernel/debug')
> and ensure the kvm modules are loaded
> 
> No joy. Suggestions?

What's the error then?  You should see the stats with all zeros until
you start your guest.  Somethink like:

kvm statistics

 efer_reload                  0       0
 exits                        0       0
 fpu_reload                   0       0
 halt_exits                   0       0
 halt_wakeup                  0       0
 host_state_reload            0       0
 insn_emulation               0       0
 insn_emulation_fail          0       0
 invlpg                       0       0
 io_exits                     0       0
 irq_exits                    0       0
 irq_window                   0       0
 mmio_exits                   0       0
 mmu_cache_miss               0       0
 mmu_flooded                  0       0
 mmu_pde_zapped               0       0
 mmu_pte_updated              0       0
 mmu_pte_write                0       0
 mmu_recycled                 0       0
 mmu_shadow_zapped            0       0
 pf_fixed                     0       0
 pf_guest                     0       0
 remote_tlb_flush             0       0
 request_irq                  0       0
 signal_exits                 0       0
 tlb_flush                    0       0

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      reply	other threads:[~2008-03-07 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 19:17 KVM and WinPE failure jieryn
2008-03-06 21:43 ` Dor Laor
2008-03-06 22:04   ` jieryn
2008-03-06 22:52     ` jieryn
2008-03-06 23:19       ` Ryan Harper
2008-03-07  0:02         ` jieryn
2008-03-07 14:49           ` Ryan Harper [this message]

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=20080307144903.GB11057@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=jieryn@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /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.