All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sanket Hase <shase@andrew.cmu.edu>
To: xen-devel@lists.xensource.com
Cc: xen-users@lists.xensource.com
Subject: supported guest type
Date: Thu, 15 Nov 2007 02:27:31 -0500	[thread overview]
Message-ID: <473BF4E3.4050506@andrew.cmu.edu> (raw)

Heres output of my : xm info

xen412:/usr/412# xm info
host                   : xen412.ugrad.cs.cmu.edu
release                : 2.6.18-xen
version                : #1 SMP Mon Oct 29 19:45:43 EDT 2007
machine                : i686
nr_cpus                : 2
nr_nodes               : 1
sockets_per_node       : 2
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 864
hw_caps                : 0383fbff:00000000:00000000:00000040
total_memory           : 1023
free_memory            : 256
xen_major              : 3
xen_minor              : 1
xen_extra              : .0
xen_caps               : xen-3.0-x86_32p
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xf5800000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)
cc_compile_by          : root
cc_compile_domain      : ugrad.cs.cmu.edu.ugrad.cs.cmu.e
cc_compile_date        : Sat Oct 27 23:23:39 EDT 2007
xend_config_format     : 4


If you notice supported guest types is xen-3.0-x86_32p  thats PAE
enabled guest.

Now, I want to run a 32bit freebsd domU which doesnt have PAE support.
When I try booting this domU i get compatibility error as it is not
PAE enabled.

How do I ensure that domO supports xen-3.0-x86_32 guest along with (
or without xen-3.0-x86_32p )


-Sanket

             reply	other threads:[~2007-11-15  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15  7:27 Sanket Hase [this message]
2007-11-15  7:34 ` supported guest type Atsushi SAKAI

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=473BF4E3.4050506@andrew.cmu.edu \
    --to=shase@andrew.cmu.edu \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.