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

[Xen-users] "xm dmesg" shows SVM but not /proc/cpuinfo

  • To: rudi@xxxxxxxxxxx
  • From: Larry Ing <larry@xxxxxxxx>
  • Date: Wed, 20 Jul 2011 15:54:16 -0700
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 20 Jul 2011 15:55:12 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=lwi3.net; h=Received:Subject:From:To:Cc:Content-Type:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding:X-Identified-User; b=aYfMh9NKDMMYQ80K5Y9vMegw2/d6TLYdm8lbhu8i6yvwVOzMcG0Ape6Mi+kPnYKjlR8Rwcmlfhm61isw1XtylWCJ55QSxO8CZkSApc7AtRrP2MNRRQz7eyOSMb0u+par;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Ah, thank you for pointing that out.  I forgot to include a subject, my
On Thu, Jul 21, 2011 at 12:46 AM, Larry Ing <larry@xxxxxxxx> wrote:
> Earlier I posed this question:
> "My Dom0 kernel is having issues detecting the SVM capabilities of my
> CPU.  Non-Xen kernels are able to see the capability just fine and I
> can't figure out why the Dom0 cannot.  I have an Opteron 6128 running
> an ASUS KGPE-D16.  I know the SVM capabilities are enabled in the
> I assume this problem is kernel related.  What in the kernel do I need
> to set such that /proc/cpuinfo lists SVM.  I am running a gentoo-dom0
> kernel."
> I have found that "xm dmesg | grep xvm" is indeed showing SVM is
> while "grep svm /proc/cpuinfo" is now.  Will this pose a problem or
> Windows guests be able to run just fine?
> _______________________________________________

You would probably get better answers if your post had a more
descriptive subject, other than "(no subject)"

Kind Regards
Rudi Ahlers

Website: http://www.SoftDux.com
Technical Blog: http://Blog.SoftDux.com
Office: 087 805 9573
Cell: 082 554 7532

Xen-users mailing list



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