From: Avi Kivity <avi@redhat.com>
To: Sebastian Hetze <s.hetze@linux-ag.com>
Cc: kvm@vger.kernel.org
Subject: Re: syscall rmdir hangs with autofs
Date: Mon, 19 Jul 2010 18:28:32 +0300 [thread overview]
Message-ID: <4C446F20.4060106@redhat.com> (raw)
In-Reply-To: <20100719152518.641BAB001A@mail.linux-ag.de>
On 07/19/2010 06:23 PM, Sebastian Hetze wrote:
>
>> What's your hardware platform? EPT/NPT capable? Host kernel version?
>>
> Intel S5520HC Board with 2 Xeon CPU E5520, HT enabled
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good
> xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2
> ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow
> vnmi flexpriority ept vpid
>
> (so yes, EPT is available)
>
> host kernel is vanilla 2.6.34
>
>
Well, EPT makes it unlikely that there's an mmu bug involved.
Is the guest smp? Can you try UP?
Can you try 2.6.32.latest in the guest?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-07-19 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 8:39 syscall rmdir hangs with autofs Sebastian Hetze
2010-07-19 11:12 ` Avi Kivity
2010-07-19 11:40 ` Sebastian Hetze
[not found] ` <20100719114034.62BDD30303F5@mail.linux-ag.de>
2010-07-19 12:21 ` Avi Kivity
2010-07-19 12:48 ` Sebastian Hetze
2010-07-19 13:09 ` Avi Kivity
2010-07-19 13:45 ` Sebastian Hetze
[not found] ` <20100719134558.A0CD2A005F@mail.linux-ag.de>
2010-07-19 14:00 ` Avi Kivity
2010-07-19 14:47 ` Sebastian Hetze
[not found] ` <20100719144750.334F2303001B@mail.linux-ag.de>
2010-07-19 15:03 ` Avi Kivity
2010-07-19 15:23 ` Sebastian Hetze
[not found] ` <20100719152518.641BAB001A@mail.linux-ag.de>
2010-07-19 15:28 ` Avi Kivity [this message]
2010-07-19 15:38 ` Sebastian Hetze
[not found] ` <20100719153816.1E33FB0016@mail.linux-ag.de>
2010-07-19 17:55 ` 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=4C446F20.4060106@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=s.hetze@linux-ag.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 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.