[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] amd-v -- passthrough supported?


  • To: chris <tknchris@xxxxxxxxx>
  • From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
  • Date: Mon, 25 Jan 2010 11:22:09 -0800
  • Cc: Xen User-List <Xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 25 Jan 2010 11:22:48 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=CWuochxOGcm1d3QNlbzs4jsWn2sKK6wx7UuXmwK1Cf78SNXGFjc3P7M4o0rBzWjKsw fJjp0o6co3/T5MQaCplwbBJ36NCGKwrlSQWkgmNeR2YVyvGSKF/2ISnK6KbQeLqw2iCZ B1HuKda5YrWtvC69MdsYgC+neeTxxA7I2ZQoA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

hi

On Mon, Jan 25, 2010 at 10:59 AM, chris <tknchris@xxxxxxxxx> wrote:
> vt-d is for passthrough to hvm domains, pv should always work afaik with no
> special cpu features...

if that's true, then i'm even more unclear as to why I'm being
referred to the VT-d spec to explain away the issues i'm seeing/having
...

in any case, for my box

reading @

"HVM refactors Xen's full virtualization support into a common layer
and defines an interface to architecture specific components. This
enables a single Xen hypervisor to dynamically detect and support
AMD's SVM or Intel's VT technology while providing a single uniform
management and user interface. "

and

cat /proc/cpuinfo | grep -i svm
  flags           :  ... svm ...

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.