Re: AESNI and guest hosts
On 02/15/2012 02:02 PM, Ryan Brown wrote: > >> > >> I don't think it's supported to pass that functionality to the guest. > >> > > > > Why not? Perhaps a new libvirt or qemu is needed. > > > > Should it be the case to add one of the following? > > > or.. > > > something like that? The qemu name is aes. Don't know about libvirt, suggest you start with bare qemu first. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: AESNI and guest hosts
>> >> I don't think it's supported to pass that functionality to the guest. >> > > Why not? Perhaps a new libvirt or qemu is needed. > Should it be the case to add one of the following? or.. something like that? Host is using linux kernel 3.2.4 (Debian Wheezy) libvirt (0.9.8-2), qemu (1.0+dfsg-2), Guest is on linux kernel Ubuntu/3.2.5 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: AESNI and guest hosts
On 02/14/2012 08:18 PM, Brian Jackson wrote: > 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 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. > Why not? Perhaps a new libvirt or qemu is needed. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: AESNI and guest hosts
Thanks for the reply, I was thinking AESNI was supported in the way SSE/MMX and other cpu flags are supported? is a QEMU or a KVM issue? On Wed, Feb 15, 2012 at 7:18 AM, Brian Jackson wrote: > 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 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. > > > >> > >> > >> > x86_64 >> > Westmere >> > Intel >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > 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 majord...@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: AESNI and guest hosts
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 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. > > > > > > x86_64 > > Westmere > > Intel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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 majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: AESNI and guest hosts
Sorry for being a noob here, Any clues with this?, anyone ... On Mon, Feb 13, 2012 at 2:05 AM, Ryan Brown 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? > > > x86_64 > Westmere > Intel > > > > > > > > > > > > > > > > > > > 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
AESNI and guest hosts
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? x86_64 Westmere Intel 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
