From: Jun Koi <junkoi2004@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: SVM support in 0.12?
Date: Sat, 19 Dec 2009 01:52:01 +0900 [thread overview]
Message-ID: <fdaac4d50912180852u679d6774o265cd4c324e720ba@mail.gmail.com> (raw)
In-Reply-To: <F780F0C5-3C21-4D85-820D-80BB4C4B7C62@suse.de>
On Fri, Dec 18, 2009 at 8:35 PM, Alexander Graf <agraf@suse.de> wrote:
>
> Am 18.12.2009 um 03:39 schrieb Jun Koi <junkoi2004@gmail.com>
>
>> On Fri, Dec 18, 2009 at 11:37 AM, Jun Koi <junkoi2004@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> I am running latest Qemu 0.12-rc. My guest VM runs Linux kernel 2.6.31.
>>>
>>> Because Qemu now supports SVM, I expect to see the SVM flag in
>>> /proc/cpuinfo, but that is not the case.
>>>
>>> So it seems SVM support is not enabled by default configuration??
>>>
>>
>> My host and guest are both 32 bit Linux, if that matters.
>>
>> (And this is pure Qemu, without using KVM or KQemu)
>
> Kqemu actually works with svm emulation.
>
> Have you tried -cpu qemu32,+svm? I think I only enabled svm on qemu64,
> because I'm not aware of 32-bit AMD CPUs that can do svm.
>
> If you use -cpu qemu32 that also means you'll get an emulated Intel CPU.
> KVM-AMD will refuse there.
>
> Also, back when I developed it, 32-bit kvm didn't really work properly. So
> please let me know what you find out!
I tried the latest Qemu code, with the following command:
qemu -m 500 -cpu qemu32,+svm -cdrom ubuntu.iso
I verified that /proc/cpuinfo has no svm flag. So SVM doesnt work on 32bit host.
I will try that with 64bit host to see how it goes.
Thanks,
Jun
next prev parent reply other threads:[~2009-12-18 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 2:37 [Qemu-devel] SVM support in 0.12? Jun Koi
2009-12-18 2:39 ` [Qemu-devel] " Jun Koi
2009-12-18 11:35 ` Alexander Graf
2009-12-18 16:52 ` Jun Koi [this message]
2009-12-18 17:34 ` Alexander Graf
2009-12-21 10:06 ` Jun Koi
2009-12-21 10:26 ` Andre Przywara
2009-12-21 11:37 ` Andre Przywara
2009-12-18 20:03 ` Jamie Lokier
2009-12-18 20:05 ` Alexander Graf
2009-12-18 11:44 ` Paolo Bonzini
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=fdaac4d50912180852u679d6774o265cd4c324e720ba@mail.gmail.com \
--to=junkoi2004@gmail.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).