From: Christian Tramnitz <chris.ace@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: pv_ops dom0 kernel and VT cpu extensions
Date: Tue, 29 Dec 2009 10:53:38 +0100 [thread overview]
Message-ID: <hhcjj2$2uj$1@ger.gmane.org> (raw)
In-Reply-To: <4B398B40.3040204@verizon.net>
Gerry Reno wrote:
> I compiled a pv_ops dom0 kernel from Jeremy's latest git tree and
> upgraded Xen to 3.4.1 following one of Boris' blog entries. From the
> Xen perspective everything seems to work as expected. But, I want to be
> able to run both Xen and KVM existing guests in a single cloud on a farm
> of VT-enabled machines. So after booting into the new pv_ops dom0
> kernel as a test I tried starting one of my KVM guests. It ran
> extremely slow so I knew immediately that it wasnt' using the VT
> acceleration. I then looked at /proc/cpuinfo and saw that the VT cpu
> flag (svm on this machine) was not there. The machine has a VT
> processor and hardware virtualization is enabled in the BIOS and I
> rebooted to check with a regular kernel and it of course the guest runs
> with VT acceleration there.
> My question is how can I get pv_ops dom0 kernel or Xen 3.4.1 to pass the
> cpu VT flags through so that existing KVM guests will run with cpu VT
> acceleration at full speed?
>
You need to start the pvops kernel on bare metal (without Xen) to make
use of VT. dom0 is already a (privileged) guest (of Xen), so the
hardware assisted virtualization interface is simply not accessible at
this point anymore...
Best regards,
Christian
prev parent reply other threads:[~2009-12-29 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 4:53 pv_ops dom0 kernel and VT cpu extensions Gerry Reno
2009-12-29 9:03 ` Keir Fraser
2009-12-29 9:53 ` Christian Tramnitz [this message]
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='hhcjj2$2uj$1@ger.gmane.org' \
--to=chris.ace@gmx.net \
--cc=xen-devel@lists.xensource.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 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.