All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Michael Riepe <michael-0QoEqw4nQxo@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [ANNOUNCE] kvm-18 release
Date: Mon, 26 Mar 2007 09:17:33 +0200	[thread overview]
Message-ID: <4607738D.30001@qumranet.com> (raw)
In-Reply-To: <4606DE0F.5010009-0QoEqw4nQxo@public.gmane.org>

Michael Riepe wrote:
> Avi Kivity wrote:
>   
>> This is mostly to fix the 32-bit Linux guest breakage in kvm-17.
>>     
>
> Well, almost. Knoppix 5.0 and 5.2 work now, but 5.1.1 still hangs with a
> black framebuffer (no penguin logo) and a load of 100%.
>   

Do you have msr complaints in dmesg? Can you try booting the guest with 
nmi_watchdog=0?


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2007-03-26  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 12:15 [ANNOUNCE] kvm-18 release Avi Kivity
     [not found] ` <460667F6.20107-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-25 20:39   ` Michael Riepe
     [not found]     ` <4606DE0F.5010009-0QoEqw4nQxo@public.gmane.org>
2007-03-26  7:17       ` Avi Kivity [this message]
     [not found]         ` <4607738D.30001-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-26 14:50           ` Michael Riepe

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=4607738D.30001@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=michael-0QoEqw4nQxo@public.gmane.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.