From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46895) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TTI1C-0005Kj-Go for qemu-devel@nongnu.org; Tue, 30 Oct 2012 16:02:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TTI16-00020l-NY for qemu-devel@nongnu.org; Tue, 30 Oct 2012 16:02:34 -0400 Received: from 69.169.164.127.provo.static.broadweavenetworks.net ([69.169.164.127]:39466 helo=baldr.dev-zero.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TTI16-00020Y-IG for qemu-devel@nongnu.org; Tue, 30 Oct 2012 16:02:28 -0400 Received: from [10.1.8.6] (mail.adaptivecomputing.com [204.15.87.226]) by baldr.dev-zero.net (Postfix) with ESMTP id 42D77190469 for ; Tue, 30 Oct 2012 14:00:01 -0600 (MDT) Message-ID: <50903261.2070107@dev-zero.net> Date: Tue, 30 Oct 2012 14:02:41 -0600 From: Mike Lovell MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] centos 6.3 and nested kvm List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org i have been using kvm in an nested environment for a couple months now. things have appeared to be working fine. i have used both intel (westmere-ep) hosts and, when starting the first level guest, i have specified '-cpu qemu64,+vmx' to pass the kvm support through. when using a centos 6.2 guest, i am able to load the kvm and kvm_intel modules and use it. the problem is today i tried updating my centos 6.2 guest to 6.3 and now the kvm_intel module fails to load in this guest. there aren't any kernel messages that i can see. does anyone on the list have an idea of what might have changed. the 6.2 system had 2.6.32-220.el6.x86_64 as the kernel version and 6.3 has 2.6.32-279.11.1.el6. the exact error i get when trying to load the module is FATAL: Error inserting kvm_intel (/lib/modules/2.6.32-279.11.1.el6.x86_64/kernel/arch/x86/kvm/kvm-intel.ko): Input/output error anyone know of anything that might have changed in the kvm_intel module or elsewhere that would cause this to break? mike