Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


How to optimize KVM (i.e. how to enable aesni in KVM)?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

How to optimize KVM (i.e. how to enable aesni in KVM)?

komo2komo2 Member

I installed debian7.2 64bit in KVM (host debian 64bit). This is how my guest cpu looks like:

vendor_id   : GenuineIntel
cpu family  : 6
model       : 2
model name  : QEMU Virtual CPU version 1.1.2
stepping    : 3
microcode   : 0x1
cpu MHz     : 3199.934
cache size  : 4096 KB
fpu     : yes
fpu_exception   : yes
cpuid level : 4
wp      : yes
flags       : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl pni cx16 popcnt hypervisor lahf_lm
bogomips    : 6399.86
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual

I am missing a lot of stuff from host. This is how to the host look like:

vendor_id   : GenuineIntel
cpu family  : 6
model       : 58
model name  : Intel(R) Xeon(R) CPU E3-1225 V2 @ 3.20GHz
stepping    : 9
microcode   : 0x16
cpu MHz     : 1600.000
cache size  : 8192 KB
physical id : 0
siblings    : 4
core id     : 3
cpu cores   : 4
apicid      : 6
initial apicid  : 6
fpu     : yes
fpu_exception   : yes
cpuid level : 13
wp      : yes
flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips    : 6399.79
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

I tried some stuff (found on http://www.linux-kvm.org/page/Tuning_KVM) like

qemu -cpu host

but I got error "Unable to find x86 CPU definition".

I changed the command to

qemu-x86_64 -cpu host

but that does not work too. I just shows me "usage" for the command:

usage: qemu-x86_64 [options] program [arguments...]
Linux CPU emulator (compiled for x86_64 emulation)

Options and associated environment variables:
...

I don't see "host" on the list here:

# qemu-x86_64 -cpu ?
x86           [n270]
x86         [athlon]
x86       [pentium3]
x86       [pentium2]
x86        [pentium]
x86            [486]
x86        [coreduo]
x86          [kvm32]
x86         [qemu32]
x86          [kvm64]
x86       [core2duo]
x86         [phenom]
x86         [qemu64]

I tried replacing "host" with kvm64 but there is no change.

I installed guest with virt-install. Do I have to shutdown guest to run these commands? Is there some kind of "best config"?

Comments

  • I just tried this:

    # qemu-x86_64 -cpu qemu64, +aes
    Error -1 while loading +aes
    

    aes without + caused same error

  • SplitIceSplitIce Member, Host Rep

    My KVM gives me -

    Recognized CPUID flags:
    pbe ia64 tm ht ss sse2 sse fxsr mmx acpi ds clflush pn pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc pse de vme fpu
    hypervisor rdrand f16c avx osxsave xsave aes tsc-deadline popcnt movbe x2apic sse4.2|sse4_2 sse4.1|sse4_1 dca pcid pdcm xtpr cx16 fma cid ssse3 tm2 est smx vmx ds_cpl monitor dtes64 pclmulqdq|pclmuldq pni|sse3
    3dnow 3dnowext lm|i64 rdtscp pdpe1gb fxsr_opt|ffxsr mmxext nx|xd syscall
    perfctr_nb perfctr_core topoext tbm nodeid_msr tce fma4 lwp wdt skinit xop ibs osvw 3dnowprefetch misalignsse sse4a abm cr8legacy extapic svm cmp_legacy lahf_lm

    Doesnt seem to have support for aesni in the version bundled with proxmox squeeze. I dont have a copy of wheezy with KVM to check the later version.

  • I obviously forgot this question :). and unfortunately nobody was able to help.

    anyone?

Sign In or Register to comment.