From: Brian Jackson <iggy@theiggy.com>
To: Ryan Brown <mp3geek@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: AESNI and guest hosts
Date: Tue, 14 Feb 2012 12:18:45 -0600 [thread overview]
Message-ID: <201202141218.45880.iggy@theiggy.com> (raw)
In-Reply-To: <CAG_yTXy0WFZ0tU8S7jdnPjZ2pvk7=gHkNbgOjh7GKJ3DMH6aUw@mail.gmail.com>
On Tuesday, February 14, 2012 03:31:10 AM Ryan Brown wrote:
> Sorry for being a noob here, Any clues with this?, anyone ...
>
> On Mon, Feb 13, 2012 at 2:05 AM, Ryan Brown <mp3geek@gmail.com> wrote:
> > Host/KVM server is running linux 3.2.4 (Debian wheezy), and guest
> > kernel is running 3.2.5. The cpu is an E3-1230, but for some reason
> > its not able to supply the guest with aesni. Is there a config option
> > or is there something we're missing?
I don't think it's supported to pass that functionality to the guest.
> >
> > <cpu>
> > <arch>x86_64</arch>
> > <model>Westmere</model>
> > <vendor>Intel</vendor>
> > <topology sockets='1' cores='4' threads='2'/>
> > <feature name='rdtscp'/>
> > <feature name='x2apic'/>
> > <feature name='xtpr'/>
> > <feature name='tm2'/>
> > <feature name='est'/>
> > <feature name='vmx'/>
> > <feature name='ds_cpl'/>
> > <feature name='monitor'/>
> > <feature name='pbe'/>
> > <feature name='tm'/>
> > <feature name='ht'/>
> > <feature name='ss'/>
> > <feature name='acpi'/>
> > <feature name='ds'/>
> > <feature name='vme'/>
> > </cpu>
> >
> > Guest:
> > [root@fanboy:~]# cat /proc/cpuinfo
> > processor : 0
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 2
> > model name : QEMU Virtual CPU version 1.0
> > stepping : 3
> > microcode : 0x1
> > cpu MHz : 3192.748
> > cache size : 4096 KB
> > fdiv_bug : no
> > hlt_bug : no
> > f00f_bug : no
> > coma_bug : no
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 4
> > wp : yes
> > flags : fpu de pse tsc msr pae mce cx8 apic mtrr pge mca
> > cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm pni cx16 popcnt
> > hypervisor lahf_lm
> > bogomips : 6385.49
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 40 bits physical, 48 bits virtual
> > power management:
> >
> > processor : 1
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 2
> > model name : QEMU Virtual CPU version 1.0
> > stepping : 3
> > microcode : 0x1
> > cpu MHz : 3192.748
> > cache size : 4096 KB
> > fdiv_bug : no
> > hlt_bug : no
> > f00f_bug : no
> > coma_bug : no
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 4
> > wp : yes
> > flags : fpu de pse tsc msr pae mce cx8 apic mtrr pge mca
> > cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm pni cx16 popcnt
> > hypervisor lahf_lm
> > bogomips : 6385.49
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 40 bits physical, 48 bits virtual
>
> > power management:
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-02-14 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 13:05 AESNI and guest hosts Ryan Brown
2012-02-14 9:31 ` Ryan Brown
2012-02-14 18:18 ` Brian Jackson [this message]
2012-02-14 22:07 ` Ryan Brown
2012-02-15 9:29 ` Avi Kivity
2012-02-15 12:02 ` Ryan Brown
2012-02-15 14:04 ` Avi Kivity
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=201202141218.45880.iggy@theiggy.com \
--to=iggy@theiggy.com \
--cc=kvm@vger.kernel.org \
--cc=mp3geek@gmail.com \
/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