From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50795)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1Wwktu-0000Yv-8a
	for qemu-devel@nongnu.org; Tue, 17 Jun 2014 00:21:47 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1Wwktl-0002Rl-7f
	for qemu-devel@nongnu.org; Tue, 17 Jun 2014 00:21:38 -0400
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <539FC243.2070906@redhat.com>
Date: Tue, 17 Jun 2014 06:21:23 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <6DBD3DBB-24B1-4564-B524-E8E73508BBC5@jnielsen.net>	<42870B81-CA29-4161-9BCE-F6D6020C3D2C@jnielsen.net>	<539F1DC0.4020604@redhat.com>
	<4F14D859-D641-4AB5-B749-83D9D82F1DEA@jnielsen.net>
In-Reply-To: <4F14D859-D641-4AB5-B749-83D9D82F1DEA@jnielsen.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Hang on reboot in FreeBSD guest on Linux KVM host
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: John Nielsen <lists@jnielsen.net>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>

Il 16/06/2014 18:47, John Nielsen ha scritto:
> On Jun 16, 2014, at 10:39 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>> Il 16/06/2014 18:09, John Nielsen ha scritto:
>>>>> The only substantial difference on the hardware side is the CPU.
>>>>> The hosts where the problem occurs use "Intel(R) Xeon(R) CPU
>>>>> E5-2650 v2 @ 2.60GHz", while the hosts that don't show the
>>>>> problem use the prior revision, "Intel(R) Xeon(R) CPU E5-2650 0 @
>>>>> 2.00GHz".
>>
>> Can you do "grep . /sys/module/kvm_intel/parameters/*" on both hosts please?
>
> No differences that I can see. Output below.

Not really:

> Working host:
> Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
> # grep . /sys/module/kvm_intel/parameters/*
> /sys/module/kvm_intel/parameters/enable_apicv:N
>
> Problem host:
> Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
> # grep . /sys/module/kvm_intel/parameters/*
> /sys/module/kvm_intel/parameters/enable_apicv:Y

So we have a clue.  Let me study the code more, I'll try to get back 
with a suggestion.

In the meanwhile, I'm CCing the KVM list and BCCing QEMU, so that 
follow-ups come to the KVM list.

Paolo