From: Piavlo <piavka@cs.bgu.ac.il>
To: kvm@vger.kernel.org
Subject: Re: which -cpu to use
Date: Thu, 26 Feb 2009 13:07:44 +0200 [thread overview]
Message-ID: <49A67800.9020304@cs.bgu.ac.il> (raw)
In-Reply-To: <9EBA26E4-6C58-4983-B614-9DB6B9247620@suse.de>
Alexander Graf wrote:
>> 2) I want to optimize/recompile a gentoo VM system packages for the
>> chosen cpu - if that matters.
>> Does rebuilding the VM packages to fine tuned for the emulated cpu
>> give any advantages?
>
> I don't think features like SSE3 matter that much in a normal environment.
I just wanted to rebuild the guest with following basic CGLAGS
"-march=opteron -O2 -pipe" (no sse3 and like features) tuned for my
hardware node cpu.
In Xen then i use guest linux VM both in fully virtualized mode and
paravirtual mode I see in guest's /proc/cpuinfo the same
naitive cpu model as in hardware node (while of course some feature
flags like svm,sse3 are missing) - but I can build the guests
with cpu native gcc -march support anyway. While seeing emulated cpu
model in /proc/cpuinfo
model name : QEMU Virtual CPU version 0.9.1
is confusing and i'm not sure if i can use -march=opteron here?
> You won't get too much more benefit from choosing a different CPU type.
>> 3) Do I have to boot a VM kernel with guest viritio drivers, to get a
>> not emulated real cpu access - like I have in Xen?
>
> virtio drivers have nothing to do with CPU.
Yes I mistakenly used the term "viritio drivers" instead of
"paravirtual guest support". So what I wanted to ask is if I build a
guest kernel with paravitual support
will it make the native hardware cpu features available inside the guest
like in Xen kernel? Or paravirtual support is for device drivers only
and has no impact on CPU handling like in Xen?
I thought that KVM (as Xen) is a bare metal hypervisor with regards to
giving access native access to the CPU which have svm or vmx support,
and not just CPU emulation.
I'm confused here - can someone shed some light on my ignorance on the
matter?
Thanks
Alex
> They are about devices like network and block. If you want to have PV
> drivers for those, you need to have a kernel that supports virtio
> (incl. virtio_pci) and specify that you want to use virtio on the qemu
> command line as options to -net or -drive.
>
> Alex
next prev parent reply other threads:[~2009-02-26 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 0:48 which -cpu to use Piavlo
2009-02-26 9:31 ` Alexander Graf
2009-02-26 11:07 ` Piavlo [this message]
2009-02-26 12:07 ` Alexander Graf
2009-02-26 12:16 ` Javier Guerra Giraldez
2009-02-26 12:57 ` Piavlo
2009-02-26 15:22 ` Javier Guerra
2009-02-27 7:50 ` paolo pedaletti
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=49A67800.9020304@cs.bgu.ac.il \
--to=piavka@cs.bgu.ac.il \
--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