From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christoph Egger" Subject: Re: freebsd domU boot problem Date: Mon, 12 Nov 2007 14:06:07 +0100 Message-ID: <200711121406.07539.Christoph.Egger@amd.com> References: <4738397B.9050406@andrew.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4738397B.9050406@andrew.cmu.edu> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: sanket hase List-Id: xen-devel@lists.xenproject.org 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 laun= ch a paravirtualized FreeBSD 32bit DomU which has no PAE support. Christoph =2D-=20 AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Gesch=E4ftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht Dresden: HRA 4896 vertretungsberechtigter Komplement=E4r: AMD Saxony LLC (Sitz Wilmington, Delaware, USA) Gesch=E4ftsf=FChrer der AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy