public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alec Joseph Rivera <eijhei@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Alexander Graf <agraf@suse.de>,
	kvm@vger.kernel.org, Meric Mara <mmara@8layertech.com>,
	Renan Mara <rmara@8layertech.com>
Subject: Re: 2.6.16 Guest Hangs on Boot
Date: Thu, 16 Sep 2010 16:17:27 +0800	[thread overview]
Message-ID: <1284625047.7482.183.camel@nami.8liens.com> (raw)
In-Reply-To: <4C911284.4090308@msgid.tls.msk.ru>

On Wed, 2010-09-15 at 22:37 +0400, Michael Tokarev wrote:
> Alec Joseph Rivera wrote:
> []
> >> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> >> Memory: 1022272k/1048564k available (1671k kernel code, 25488k reserved, 890k data, 200k init, 131064k highmem)
> >> Checking if this processor honours the WP bit even in supervisor mode... Ok.
> > -- end
> 
> Hm.  There was some error with earlier kernels and
> kvm that resulted in exactly this behavour.  Maybe
> even a (guest) kernel bug.. no?  My memory is vague
> in this area, but it tells there was something...
> 

Hi Michael:

I suspect has something to do with loops (re: bogomips calibration) or
timers (re: calibration + pci probing). Will verify this when I get the
time to read the source.

Maybe someone more familiar with this kernel area can shed some light on
the topic too...? :-) only if I'm not stretching too much..

> /mjt


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera




  reply	other threads:[~2010-09-16  8:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 16:53 2.6.16 Guest Hangs on Boot Alec Joseph Rivera
2010-09-15 17:28 ` Alexander Graf
2010-09-15 17:48   ` Alec Joseph Rivera
2010-09-15 17:51     ` Alexander Graf
2010-09-15 18:07       ` Alec Joseph Rivera
2010-09-15 18:15         ` Alexander Graf
2010-09-15 18:26           ` Alec Joseph Rivera
2010-09-16  1:55           ` Alec Joseph Rivera
2010-09-16  6:39             ` Gleb Natapov
2010-09-16  7:52               ` Alec Joseph Rivera
2010-09-16  7:56                 ` Gleb Natapov
2010-09-16  8:03                   ` Alec Joseph Rivera
2010-09-16 10:11                     ` Alec Joseph Rivera
2010-09-16 10:14                       ` Gleb Natapov
2010-09-16 11:13                         ` Alec Joseph Rivera
2010-09-16 11:18                           ` Gleb Natapov
2010-09-16 10:27             ` Alexander Graf
2010-09-16 11:02               ` Joerg Roedel
2010-09-16 11:11                 ` Alec Joseph Rivera
2010-09-16 11:32                   ` Joerg Roedel
2010-09-16 11:35                     ` Michael Tokarev
2010-09-16 11:41                       ` Gleb Natapov
2010-09-16 11:43                       ` Joerg Roedel
2010-09-16 11:37                     ` Alec Joseph Rivera
2010-09-16 11:41                       ` Gleb Natapov
2010-09-16 11:51                         ` Alec Joseph Rivera
2010-09-15 18:37         ` Michael Tokarev
2010-09-16  8:17           ` Alec Joseph Rivera [this message]
2010-09-16  8:32             ` Dave Young
2010-09-16  9:56               ` Alec Joseph Rivera

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=1284625047.7482.183.camel@nami.8liens.com \
    --to=eijhei@gmail.com \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=mmara@8layertech.com \
    --cc=rmara@8layertech.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox