From: Sanket Hase <shase@andrew.cmu.edu>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: Kip Macy <kip.macy@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: freebsd domU boot problem
Date: Wed, 14 Nov 2007 22:57:06 -0500 [thread overview]
Message-ID: <473BC392.3010908@andrew.cmu.edu> (raw)
In-Reply-To: <200711121406.07539.Christoph.Egger@amd.com>
Here is the output of my "xm info"
xen412:~# xm info
host : ****
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 : ****
cc_compile_date : Sat Oct 27 23:23:39 EDT 2007
xend_config_format : 4
Error that we are getting is "guest type xen-3.0-x86_32 not supported by
xen kernel"
If you have noticed above in the output of xm info
xen_caps : xen-3.0-x86_32p
Does this "p" in xen-3.0-x86_32p stands for PAE ?
Should there be an explicit mention of xen-3.0-x86_32 in xen_caps ?
If yes , what determines the type of supported guests ?
Thanks,
Sanket
Christoph Egger wrote:
> On Monday 12 November 2007 12:31:07 sanket hase wrote:
>> Hi Folks ,
>>
>> Heres something
>>
>> xen412:/etc/xen# xm create -c freebsd_xen
>> Using config file "./freebsd_xen".
>> Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type
>> xen-3.0-x86_32 not supported by xen kernel, sorry\n')
>>
>> Whats with "guest type xen-3.0-x86_32 not supported by xen kernel" ?
>
> "xm info" tells you what guest types are supported.
>
> To me, it looks like you are running a 64bit hypervisor and you try to launch
> a paravirtualized FreeBSD 32bit DomU which has no PAE support.
>
>
>
> Christoph
>
>
next prev parent reply other threads:[~2007-11-15 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 11:31 freebsd domU boot problem sanket hase
2007-11-12 13:06 ` Christoph Egger
2007-11-12 13:22 ` Sébastien RICCIO
2007-11-15 3:57 ` Sanket Hase [this message]
2007-12-02 5:08 ` Mark Williamson
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=473BC392.3010908@andrew.cmu.edu \
--to=shase@andrew.cmu.edu \
--cc=Christoph.Egger@amd.com \
--cc=kip.macy@gmail.com \
--cc=xen-devel@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.