From: Avi Kivity <avi@qumranet.com>
To: "Yang, Sheng" <sheng.yang@intel.com>
Cc: kvm-devel@lists.sourceforge.net, Alexander Graf <alex@csgraf.de>
Subject: Re: KVM Test result, kernel 81e4400.., userspace 08385e4.. , One new issue
Date: Mon, 25 Feb 2008 11:34:29 +0200 [thread overview]
Message-ID: <47C28BA5.1010706@qumranet.com> (raw)
In-Reply-To: <200802251731.57297.sheng.yang@intel.com>
Yang, Sheng wrote:
> On Monday 25 February 2008 16:41:25 Zhao, Yunfeng wrote:
>
>> Hi, all,
>>
>> This is today's KVM test result against kvm.git
>> 81e4400b4df4e597a81c19c1161aa03c73613710 and kvm-userspace.git
>> 08385e49dcff3585f597870af67301d7659a1ecb.
>>
>> One new issue has been found in today's testing:
>> 1. fc5/fc6/rhel5u1 no-acpi up guests can't boot on pae host
>> https://sourceforge.net/tracker/index.php?func=detail&aid=1901208&group_
>> id=180599&atid=893831
>>
>
> A quick bisect shows that the problem caused by "kvm: qemu: fix host_cpuid()
> on x86_64".
>
Yeah, I just found this out the hard way (by trying to debug this --
silly me). The effects were that the "GenuineIntel" in cpuid
identification was corrupted.
I'm reverting that patch.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-25 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 8:41 KVM Test result, kernel 81e4400.., userspace 08385e4.. , One new issue Zhao, Yunfeng
2008-02-25 9:31 ` Yang, Sheng
2008-02-25 9:34 ` Avi Kivity [this message]
2008-02-25 10:28 ` Alexander Graf
2008-02-25 10:45 ` Avi Kivity
2008-02-25 12:55 ` Alexander Graf
2008-02-25 17:40 ` Avi Kivity
2008-02-25 18:35 ` Alexander Graf
2008-02-25 19:26 ` Avi Kivity
2008-02-25 17:37 ` [PATCH] fix CPUID handling Alexander Graf
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=47C28BA5.1010706@qumranet.com \
--to=avi@qumranet.com \
--cc=alex@csgraf.de \
--cc=kvm-devel@lists.sourceforge.net \
--cc=sheng.yang@intel.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