From: Yunfeng Zhao <yunfeng.zhao@intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: john cooper <john.cooper@redhat.com>,
Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, Avi Kivity <avi@qumranet.com>
Subject: Re: KVM Test result, kernel ff5bdac.., userspace eb2fd67.. -- OneNew Issue
Date: Thu, 12 Jun 2008 17:25:33 +0800 [thread overview]
Message-ID: <4850EB8D.7050301@intel.com> (raw)
In-Reply-To: <20080609212310.GA6324@dmt.cnet>
Marcelo Tosatti wrote:
> On Fri, Jun 06, 2008 at 11:11:12AM +0800, Yunfeng Zhao wrote:
>
>> Hi All,
>>
>> This is today's KVM test result against kvm.git
>> ff5bdac4be0230e0bb33e4208ac0a91343c72929 and kvm-userspace.git
>> eb2fd67cbecdb573f908697ed41b81ee312372bd.
>>
>> One New Issue:
>> ================================================
>> 1. Guests crash while rebooting
>> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1976075&group_id=180599
>>
>>
>> Five Old Issues:
>> ================================================
>> 2. Fail to save restore and live migrate
>> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1976075&group_id=180599
>> 3. netperf causes linux guest with virtnet kernel panic
>> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1972449&group_id=180599
>> 4. XP crashes while rebooting
>> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1959452&group_id=180599
>> 5.Cannot boot guests with hugetlbfs
>> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1941302&group_id=180599
>>
>
> This is a get_user_pages() with hugetlb-vma's bug, not KVM's problem,
> fixed by:
>
> commit 5b23dbe8173c212d6a326e35347b038705603d39
> Author: Adam Litke <agl@us.ibm.com>
> Date: Wed Nov 14 16:59:33 2007 -0800
>
> hugetlb: follow_hugetlb_page() for write access
>
> When calling get_user_pages(), a write flag is passed in by the caller to
> indicate if write access is required on the faulted-in pages.
>
> Currently, follow_hugetlb_page() ignores this flag and always faults pages for
> read-only access. This can cause data corruption because a device driver
> that calls get_user_pages() with write set will not expect COW faults to
> occur on the returned pages.
>
> This patch passes the write flag down to follow_hugetlb_page() and makes
> sure hugetlb_fault() is called with the right write_access parameter.
>
> Can you please upgrade your test hosts to 2.6.25 or newer?
>
I tried to test it against 2.6.25-rc5.
The host hanged while booting a xp guest.
Thanks
Yunfeng
> Perhaps kvm-userspace should check for kernel version and disable
> hugetlb backed memory. Nasty.
>
> Thanks John for help in tracking this down.
>
>
next prev parent reply other threads:[~2008-06-12 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 3:11 KVM Test result, kernel ff5bdac.., userspace eb2fd67.. -- One New Issue Yunfeng Zhao
2008-06-09 21:23 ` Marcelo Tosatti
2008-06-10 19:54 ` john cooper
2008-06-12 9:25 ` Yunfeng Zhao [this message]
2008-06-14 19:27 ` KVM Test result, kernel ff5bdac.., userspace eb2fd67.. -- OneNew Issue Marcelo Tosatti
2008-06-16 3:35 ` KVM Test result, kernel ff5bdac.., userspace eb2fd67.. --OneNew Issue Yunfeng Zhao
2008-06-12 13:21 ` KVM Test result, kernel ff5bdac.., userspace eb2fd67.. -- One New Issue Avi Kivity
2008-06-13 21:20 ` Marcelo Tosatti
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=4850EB8D.7050301@intel.com \
--to=yunfeng.zhao@intel.com \
--cc=avi@qumranet.com \
--cc=chrisw@redhat.com \
--cc=john.cooper@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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