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

Re: [Xen-users] (no subject)

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Larry Ing <larry@xxxxxxxx>
  • Date: Wed, 20 Jul 2011 15:46:41 -0700
  • Delivery-date: Wed, 20 Jul 2011 15:48:12 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=lwi3.net; h=Received:Subject:From:To:In-Reply-To:References:Content-Type:Date:Message-ID:Mime-Version:X-Mailer:Content-Transfer-Encoding:X-Identified-User; b=Fhu64smzosnpAnHtGtv53yDrpVOTKx7q2vgXT8lGbjZ11uJfXlW8X7AFhVmXWc/ims4mppCtNsX4QpYTmXr92jbyOt0iBgEyB5Dgmd8nboOf0d+CPueYizxx18wsaZWE;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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 on
an ASUS KGPE-D16.  I know the SVM capabilities are enabled in the bios.
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

I have found that "xm dmesg | grep xvm" is indeed showing SVM is enabled
while "grep svm /proc/cpuinfo" is now.  Will this pose a problem or will
Windows guests be able to run just fine?

Xen-users mailing list



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