From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 4/6] Implement Hyper-V MSRs Date: Sun, 17 May 2009 23:00:13 +0300 Message-ID: <4A106CCD.10903@redhat.com> References: <1242375740-31222-1-git-send-email-agraf@suse.de> <1242375740-31222-2-git-send-email-agraf@suse.de> <1242375740-31222-3-git-send-email-agraf@suse.de> <1242375740-31222-4-git-send-email-agraf@suse.de> <1242375740-31222-5-git-send-email-agraf@suse.de> <4A0FDEED.9020906@redhat.com> <59A0ED05-7A6B-4932-BA04-836D1E65350C@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" , "joerg.roedel@amd.com" To: Alexander Graf Return-path: Received: from mx2.redhat.com ([66.187.237.31]:45765 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752160AbZEQUAS (ORCPT ); Sun, 17 May 2009 16:00:18 -0400 In-Reply-To: <59A0ED05-7A6B-4932-BA04-836D1E65350C@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: Alexander Graf wrote: >>> case MSR_VM_CR: >>> + case 0x40000081: >>> *data = 0; >>> break; >>> >> >> This probably is a Hyper-V MSR, but I don't see how it expects it to >> be present in real hardware. Are you sure this is really needed? > > Well hyper-v just crashes/reboots if it get a #gp on that msr, so I > suppose yes. This is suspicious. It won't get this MSR on real hardware. Maybe this was with cpuid.hypervisor enabled? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.