All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt-XAri/EZa3C4vJsYlp49lxw@public.gmane.org>
To: Amit Shah <amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: amd64: does it ever work? ;)
Date: Fri, 01 Feb 2008 11:31:39 +0300	[thread overview]
Message-ID: <47A2D8EB.5030403@msgid.tls.msk.ru> (raw)
In-Reply-To: <200802011351.28186.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Amit Shah wrote:

> On Friday 01 February 2008 13:30:03 Michael Tokarev wrote:

>> Some time ago I tried KVM for the first time, on an AMD X2-64 system
>> (BE-2400 processor, also tried with other similar processors, like
>> "plain" X2-64 4888+ etc), first with 2.6.23 vanilla kernel compiled
>> for 64 bits, SMP.  After it didn't work, I also tried KVM modules
>> from SVN (compiled against the same kernel sources), and when 2.6.24
>> was out, I tried that too.  Neither of which works.
> 
> KVM doesn't have an SVN tree; do you mean git?

Err...  It was totally screwed up.  I tried kvm-59 release from
sourceforge, not git (and definitely not svn :)

Right now I'm compiling kvm-60.

>> Userspace tools is from Debian unstable -- 58+dfsg-1.
>>
>> The effect is as follows.
>>
>> With 2.6.23 and vanilla kvm modules, while from X, it opens the
>> "virtual console" (an X window), but that console is entirely
>> empty (black), and nothing more happens.  I can Ctrl+C the original
>> process, but nothing more.
>>
>> With 2.6.23+modules-59, and with vanilla 2.6.24, it again opens
>> the window, and the HOST machine immediately reboots (goes into
>> BIOS Post screen).
>>
>> When not loading kvm modules, it works in all 3 cases.
>>
>> Where to look at to debug it further?
> 
> Can you check if you have any BIOS updates? This seems like BIOS support for 
> SVM might be half-baked.

Well..  I tried it on 2 different motherboards with 2 different
CPUs (in all 4 permutations):

Biostar TA690G-AM2 - AMD690G chipset, latest BIOS (dated 09-2007)
ASUS M2NPV-VM - Geforce6150/Nforce430(?) (MCP51), latest BIOS (dated 11-2007)

The effect on both is exactly the same.

So I don't think it's a BIOS problem after all.  Maybe some kernel
option(s) (like tickless (dynticks) for example - but 2.6.23 x86-64
didn't have that option).  But with so many options I'm afraid I can't
tell which to try to turn off... ;)

Thanks!

/mjt

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

  parent reply	other threads:[~2008-02-01  8:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  8:00 amd64: does it ever work? ;) Michael Tokarev
     [not found] ` <47A2D183.7080100-Gdu+ltImwkhes2APU0mLOQ@public.gmane.org>
2008-02-01  8:21   ` Amit Shah
     [not found]     ` <200802011351.28186.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-02-01  8:31       ` Michael Tokarev [this message]
     [not found]         ` <47A2D8EB.5030403-Gdu+ltImwkhes2APU0mLOQ@public.gmane.org>
2008-02-01 17:06           ` Michael Tokarev
2008-02-01 21:49           ` Michael Tokarev
2008-02-10 11:31             ` Avi Kivity
2008-02-11  6:57               ` Amit Shah
2008-02-11  7:28                 ` Avi Kivity
2008-02-11  8:36                   ` Michael Tokarev
2008-02-11 10:17                     ` Avi Kivity
2008-02-12  5:27                   ` Amit Shah

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=47A2D8EB.5030403@msgid.tls.msk.ru \
    --to=mjt-xari/eza3c4vjsylp49lxw@public.gmane.org \
    --cc=amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.