public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Riepe <michael-0QoEqw4nQxo@public.gmane.org>
To: Carsten Emde <Carsten.Emde-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [ANNOUNCE] kvm-17 release
Date: Sat, 24 Mar 2007 12:58:09 +0100	[thread overview]
Message-ID: <46051251.1020401@mr511.de> (raw)
In-Reply-To: <46048C34.4080300-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>

Hi!

Carsten Emde wrote:
> Avi Kivity wrote:
> 
>>Michael Riepe wrote:
>>
>>>With respect to the Core Duo, this is the best release I've seen so far:
> 
> Unfortunately, kvm-17 was less successful here. FC6 did not boot any 
> longer after I upgraded from kvm-16 to kvm-17, so I was rather surprised 
> when I read the above message.

Probably the same problem that killed Knoppix in -17 (-16 worked fine).
But it was the first release that worked with both Net- and FreeBSD as
well as Solaris.

Oh by the way: Knoppix 5.2 behaves the same way as 5.1.1. With -17, it
hangs before the penguin logo appears on the framebuffer.

> This is the test system:
> CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz, Chipset: Intel 975X

There's quite a difference between Core Duo and Core 2 Duo.

Did the host and/or guest run in 64-bit mode, by the way?

-- 
Michael "Tired" Riepe <michael-0QoEqw4nQxo@public.gmane.org>
X-Tired: Each morning I get up I die a little

-------------------------------------------------------------------------
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-24 11:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 13:27 [ANNOUNCE] kvm-17 release Avi Kivity
     [not found] ` <45FFE14F.6020808-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-22 19:32   ` Michael Riepe
     [not found]     ` <4602D9D5.7060806-0QoEqw4nQxo@public.gmane.org>
2007-03-23  9:33       ` Avi Kivity
     [not found]         ` <46039EEA.4070504-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-24  2:25           ` Carsten Emde
     [not found]             ` <46048C34.4080300-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
2007-03-24  3:29               ` Carsten Emde
     [not found]                 ` <46049B0C.40501-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
2007-03-24 12:29                   ` Michael Riepe
     [not found]                     ` <460519A6.1020005-0QoEqw4nQxo@public.gmane.org>
2007-03-24 13:25                       ` Carsten Emde
2007-03-25  8:53                       ` Avi Kivity
2007-03-25  8:47                   ` Avi Kivity
2007-03-24 11:58               ` Michael Riepe [this message]
     [not found]                 ` <46051251.1020401-0QoEqw4nQxo@public.gmane.org>
2007-03-24 13:06                   ` Carsten Emde
2007-03-25  8:49                   ` Avi Kivity
2007-03-25  8:46               ` Avi Kivity
2007-03-23  9:43       ` Avi Kivity

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=46051251.1020401@mr511.de \
    --to=michael-0qoeqw4nqxo@public.gmane.org \
    --cc=Carsten.Emde-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox