All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Andreu <manuel.andreu@freenet.de>
To: kvm@vger.kernel.org
Subject: Getting VIA Padlock hardware encryption to work inside kvm guest
Date: Thu, 13 Dec 2012 20:48:40 +0100	[thread overview]
Message-ID: <50CA3118.5010108@freenet.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

Hi everyone,

i am trying to set up a virtualized server on Zotac Z-Box with VIAs Nano 
X2 processor.

I have set up a host system based upon the current debian wheezy testing 
with kernel 3.2.0-4-amd64 and qemu 1.1.2+dfsg-2 and have succeeded to 
create virtual guests for debian and windows.

Now i am trying to get the VIA Padlick hardware encryption working 
inside the guests.

As the page http://www.linux-kvm.org/page/Tuning_KVM suggest, i tried to 
enable the host cpu feature for the guests with "qemu -cpu host", but i 
get "Unable to find x86 CPU definition". With "qemu -cpu ?" i get a list 
of supported cpus, but host is not part of it. When i try "qemu -cpu 
qemu64,+ace,+ace_en" i get "CPU feature ace not found" and "CPU feature 
ace_en not found".

As the page https://patchwork.kernel.org/patch/702631/ suggests, support 
for the VIA Padlock CPUID and flags should already be there.

I do not understand why qemu has no definition for the "host" cpu, can 
anybody please help me with this problem or at least point me somewhere 
for more information?

Sincerely,
Manuel Andreu


[-- Attachment #2: S/MIME Kryptografische Unterschrift --]
[-- Type: application/pkcs7-signature, Size: 4450 bytes --]

             reply	other threads:[~2012-12-13 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 19:48 Manuel Andreu [this message]
2012-12-13 20:22 ` Getting VIA Padlock hardware encryption to work inside kvm guest Stefan Ahrens

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=50CA3118.5010108@freenet.de \
    --to=manuel.andreu@freenet.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.