From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] Don't expose hypervisor bit when running nested SVM Date: Mon, 22 Jun 2009 11:46:49 +0300 Message-ID: <4A3F44F9.4080608@redhat.com> References: <1245276660-11259-1-git-send-email-agraf@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Alexander Graf Return-path: Received: from mx2.redhat.com ([66.187.237.31]:59308 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751907AbZFVIqE (ORCPT ); Mon, 22 Jun 2009 04:46:04 -0400 In-Reply-To: <1245276660-11259-1-git-send-email-agraf@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On 06/18/2009 01:11 AM, Alexander Graf wrote: > Hyper-V refuses to run in hypervisor mode when it finds the hypervisor bit > set, because it assumes it's running as a guest. > > While the perfect way of not setting the hypervisor would be an option to the > -cpu parameter, this is reasonable sane for now. Let's deal with the -cpu > way when we get to -cpu host. > > There's infrastructure in helper.c to make -cpu blah,-hypervisor fairly trivial, no? -- error compiling committee.c: too many arguments to function