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

Re: [Xen-users] XEN Howto/ Host FC7 Guest Windows Me or Xp

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Jamie Gavahan" <redpike@xxxxxxxxx>
  • Date: Thu, 8 Nov 2007 01:44:13 -0600
  • Delivery-date: Wed, 07 Nov 2007 23:44:55 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LsEIRtezU0ETecZTRPgYJBRutzpy/rJ6sHs1xInu8/4RUa5pnjuA9ZP6+3JVsAUGZw8Yfn0XMfJqhg4iKa8KW65lApZqhGDXSyQQ+mtUoRIIuVEW90q5UyC6y1AvjrSA7oBrPAqGiEF5594jSzKzivZE3KOWM+Jp1qsQoBdk94Q=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 11/8/07, Jens Seidel <jensseidel@xxxxxxxxxxxx> wrote:
> On Wed, Nov 07, 2007 at 07:29:25PM -0600, Jamie Gavahan wrote:
> > The OP doesn't mention if it is an AMD or an Intel processor.
> > So in addition to doing xm dmesg | grep -i vmx, which would only work
> > if it's an intel processor, xm dmesg | grep -i svm should be done as
> > well.
> Strange, is it really necessary to have xm already installed to test for
> CPU support? I expected a
>  grep ??? /proc/cpuinfo
> kind of test.
> Jens

The OP already have xen installed so that was my rationale for
utilizing that command.
Using cat or grep on /proc/cpuinfo would work as well.


Xen-users mailing list



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