public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Mike Lampard <mike-/+b+wjvSUqIxsqv6Oivclw@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] Expose host cpuid to guest
Date: Thu, 22 Nov 2007 15:30:00 +0200	[thread overview]
Message-ID: <47458458.3030104@qumranet.com> (raw)
In-Reply-To: <200711221012.05384.mike-/+b+wjvSUqIxsqv6Oivclw@public.gmane.org>

Mike Lampard wrote:
> With current kvm-git (commit 51727a110220681f6f43b005d069e28c58f5d151) 
> (userspace is current to commit 6a385c9539f9746d7ff51ef34c064c3eba86448b) and 
> the userspace portion of this patch I cannot boot a 64 bit guest (Mandriva 
> 2008 x64) on my AMD x2 without -cpu host.  The guest kernel says "Your CPU 
> does not support long mode.  Use a 32bit distribution.".  Works fine without 
> the userspace portion of the patch.  
>
> With -cpu host, the 64bit kernel starts to boot then panics almost 
> immediately:
> Code: 0f 30 e9 ed fc ff ff b8 66 00 00 00 f0 0f ab 45 08 e9 e2 fa
> RIP [<ffffffff8020ff99> identify_cpu+0x609/0x700
>  RSP <ffffffff8057df58>
> Kernel panic - not syncing: Attempted to kill the idle task!
>
> In the host log I see: cpu0 unhandled wrmsr: 0xc0010015, which might not have 
> anything to do with this patch of course :)
>   

A listing/disassembly of the function will help show where the problem is.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-11-22 13:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 11:06 [RFC] Expose host cpuid to guest Dan Kenigsberg
     [not found] ` <20071121110631.GA14292-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
2007-11-21 11:21   ` Amit Shah
2007-11-21 11:52   ` Avi Kivity
     [not found]     ` <47441BEF.4070207-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-21 14:41       ` Dan Kenigsberg
     [not found]         ` <20071121144128.GA26036-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
2007-11-21 15:11           ` Avi Kivity
2007-11-21 23:42   ` Mike Lampard
     [not found]     ` <200711221012.05384.mike-/+b+wjvSUqIxsqv6Oivclw@public.gmane.org>
2007-11-22 13:01       ` Dan Kenigsberg
     [not found]         ` <20071122130118.GA14295-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
2007-11-22 13:20           ` Mike Lampard
     [not found]             ` <200711222350.14746.mike-/+b+wjvSUqIxsqv6Oivclw@public.gmane.org>
2007-11-22 13:36               ` Dan Kenigsberg
2007-11-22 13:30       ` Avi Kivity [this message]
     [not found]         ` <47458458.3030104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-22 13:50           ` Mike Lampard
2007-12-25 15:56   ` [RFC] Expose host cpuid to guest: userspace patch Dan Kenigsberg

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=47458458.3030104@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mike-/+b+wjvSUqIxsqv6Oivclw@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox