From: Gilles PIETRI <contact+dev@gilouweb.com>
To: kvm@vger.kernel.org
Subject: KVM-86 not exposing 64 bits CPU anymore, NICE
Date: Thu, 04 Jun 2009 09:20:38 +0200 [thread overview]
Message-ID: <4A2775C6.9030503@gilouweb.com> (raw)
Hi,
I'm quite pissed off. I just upgraded to kvm-86 on a host that has
worked nicely on kvm-78 for quite some time. But since I was fearing the
qcow2 corruption issues, I wanted to upgrade kvm-86. After testing the
performance, I decided to switch. How stupid that was. That was really
putting too much trust in KVM.
Now I can't have 64 bits CPUs on my guests.
My host is running a 2.6.27.7 kernel, and is x86_64 enabled.
Until the upgrade, guests were running x86_64 fine.
Now, it says long mode can't be used or something like that, and I can
only have 32 bits guests.
Looks really like the bug explained here:
http://www.mail-archive.com/kvm@vger.kernel.org/msg09431.html
If I use -no-kvm, it works, but obviously, I want to be able to have kvm
support enabled.
Now, I really am happy about this upgrade, and I'm gonna have to roll it
back. I really would appreciate some help on this..
Gilles
next reply other threads:[~2009-06-04 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 7:20 Gilles PIETRI [this message]
2009-06-04 7:46 ` KVM-86 not exposing 64 bits CPU anymore, NICE Jim Paris
2009-06-04 8:02 ` Gilles PIETRI
2009-06-04 8:00 ` Alexey Eromenko
2009-06-04 9:27 ` Mark McLoughlin
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=4A2775C6.9030503@gilouweb.com \
--to=contact+dev@gilouweb.com \
--cc=kvm@vger.kernel.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