From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Nakajima, Jun" <jun.nakajima-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Is the latest tree broken for 64-bit guests?
Date: Thu, 26 Apr 2007 10:50:43 +0300 [thread overview]
Message-ID: <463059D3.1020602@qumranet.com> (raw)
In-Reply-To: <8FFF7E42E93CC646B632AB40643802A8027FC229-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Nakajima, Jun wrote:
> Avi, Hi
>
> I just tried the latest git tree, and I'm getting like (from
> arch/x86_64/boot/setup.S):
> Your CPU does not support long mode. Use a 32bit distribution.
>
> I don't see the problem with kvm-20. I tried that quickly, so I can be
> wrong. But can you please check that?
>
The tree was broken for a short while, maybe you picked it up at the
wrong moment. Commit 5d39e516c307ee54666ec63f8722b1d0f5fbca0a (in
kvm-userspace.git) is the fix.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-04-26 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 5:02 Is the latest tree broken for 64-bit guests? Nakajima, Jun
[not found] ` <8FFF7E42E93CC646B632AB40643802A8027FC229-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-04-26 7:50 ` Avi Kivity [this message]
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=463059D3.1020602@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=jun.nakajima-ral2JQCrhuEAvxtiuMwx3w@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.