From: Charles Duffy <Charles_Duffy@messageone.com>
To: kvm@vger.kernel.org
Subject: Re: [ANNOUNCE] kvm-79 release
Date: Fri, 14 Nov 2008 16:15:48 -0600 [thread overview]
Message-ID: <gfktal$m2l$1@ger.gmane.org> (raw)
In-Reply-To: <491DC76A.9000202@web.de>
Jan Kiszka wrote:
> Farkas Levente wrote:
>> - guest fedora-9 latest kernel-2.6.26.6-79.fc9.i686 still not boot,
>> - guest centos-5 x86_64's kernel-2.6.18-92.1.17.el5 still gives the same
>> crash as kvm-78 (screenshot attached),
>
> Those two should be fine with this patch [1]. You are welcome to test it
> and be the first (mmmh...) to provide feedback on it.
I've been able to reproduce the issue on CentOS 5 x86_64 guests quite
reliably; after applying the patch to kvm-79 (with the necessary
filename munging), this issue does indeed appear to be resolved.
next prev parent reply other threads:[~2008-11-14 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 12:41 [ANNOUNCE] kvm-79 release Avi Kivity
2008-11-14 13:44 ` Farkas Levente
2008-11-14 18:46 ` Jan Kiszka
2008-11-14 22:15 ` Charles Duffy [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-12 14:53 Martin Vogt
2008-11-12 14:55 ` Avi Kivity
[not found] ` <491AF497.7020700@itwm.fraunhofer.de>
2008-11-12 15:27 ` 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='gfktal$m2l$1@ger.gmane.org' \
--to=charles_duffy@messageone.com \
--cc=kvm@vger.kernel.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