linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zachary Amsden <zamsden@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: Avi Kivity <avi@redhat.com>,
	Nikola Ciprich <nikola.ciprich@linuxbox.cz>,
	KVM list <kvm@vger.kernel.org>,
	Linux kernel list <linux-kernel@vger.kernel.org>,
	Glauber Costa <glommer@redhat.com>
Subject: Re: regression - 2.6.36 -> 2.6.37 - kvm - 32bit SMP guests don't boot
Date: Fri, 04 Mar 2011 10:13:51 -0500	[thread overview]
Message-ID: <4D7101AF.6060009@redhat.com> (raw)
In-Reply-To: <20110303220155.GB27691@nik-comp.lan>

On 03/03/2011 05:01 PM, Nikola Ciprich wrote:
>> That sounds like a kernel which will be vulnerable to broken KVM clock
>> on 32-bit.  There's a kernel side fix that is needed, but why the server
>> side change triggers the problem needs more investigation.
>>      
> OK, it's important for me that I can fix this by kernel parameter,
> but if I can help somehow with debugging, please let me know.
> thanks for Your time!
> nik
>    

You don't see any messages about TSC being unstable or switching 
clocksource after loading the KVM module?  And you are not suspending 
the host or anything?

Can you try using "processor.max_cstate=1" on the host as a kernel 
parameter and see if it makes a difference?

  reply	other threads:[~2011-03-04 15:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 23:42 regression - 2.6.36 -> 2.6.37 - kvm - 32bit SMP guests don't boot Nikola Ciprich
2011-02-24 10:17 ` Avi Kivity
2011-02-24 10:48   ` Nikola Ciprich
2011-02-24 10:52     ` Avi Kivity
2011-02-24 11:27       ` Nikola Ciprich
2011-02-24 12:26         ` Avi Kivity
2011-02-24 12:41           ` Nikola Ciprich
2011-02-24 12:51             ` Avi Kivity
2011-02-24 12:57               ` Nikola Ciprich
2011-02-25 10:48                 ` Nikola Ciprich
2011-02-25 14:45                   ` Zachary Amsden
2011-02-27 17:20                     ` Nikola Ciprich
2011-02-28 13:51                       ` Zachary Amsden
2011-02-28 14:32                         ` Nikola Ciprich
2011-02-28 15:17                           ` Zachary Amsden
2011-02-28 15:28                             ` Nikola Ciprich
2011-02-28 15:56                               ` Zachary Amsden
2011-02-28 17:13                                 ` Nikola Ciprich
2011-02-28 17:15                                 ` Nikola Ciprich
2011-03-03  1:56                                   ` Zachary Amsden
2011-03-03  7:06                                     ` Nikola Ciprich
2011-03-03 20:47                                       ` Zachary Amsden
2011-03-03 21:06                                         ` Nikola Ciprich
2011-03-03 21:58                                           ` Zachary Amsden
2011-03-03 22:01                                             ` Nikola Ciprich
2011-03-04 15:13                                               ` Zachary Amsden [this message]
2011-03-04 18:27                                                 ` Nikola Ciprich
2011-03-04 19:09                                                   ` Glauber Costa
2011-03-04 20:55                                                     ` Nikola Ciprich
2011-03-04 21:41                                                       ` Glauber Costa
2011-03-04 22:36                                                         ` Nikola Ciprich
2011-03-04 22:59                                                           ` Zachary Amsden
2011-03-05  1:17                                                           ` Zachary Amsden
2011-03-05  7:21                                                             ` Nikola Ciprich
2011-03-06 14:53                                                               ` Zachary Amsden
2011-03-06 16:03                                                                 ` Nikola Ciprich
2011-03-04 22:57                                                     ` Zachary Amsden

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=4D7101AF.6060009@redhat.com \
    --to=zamsden@redhat.com \
    --cc=avi@redhat.com \
    --cc=extmaillist@linuxbox.cz \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    /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;
as well as URLs for NNTP newsgroup(s).