Hi, I tried to start a 32Bit PVM system on a 64Bit dom0, and got the following error: Using config file "./VM1". Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n'') and it just did not started. Is ist just because of the different 32/64Bit of domU and dom0? The xen in the dom0 is configured to be backward compatible. The dom0 is a xen 3.1.0, the domU is a xen 3.0.3. When this is just not working, then I have to run the dom0 in 32Bit. Do I can then assign 4GB RAM to each domU, or will the dom0 be unable to handle that amount of memory? I assume I need a PAE enabled Xen kernel for the dom0? But will I need such a kernel then for the domU''s too? kind regards Sebastian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I tried to start a 32Bit PVM system on a 64Bit dom0, and got the following error: Using config file "./VM1". Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n'') and it just did not started. Is ist just because of the different 32/64Bit of domU and dom0? The xen in the dom0 is configured to be backward compatible. The dom0 is a xen 3.1.0, the domU is a xen 3.0.3. When this is just not working, then I have to run the dom0 in 32Bit. Do I can then assign 4GB RAM to each domU, or will the dom0 be unable to handle that amount of memory? I assume I need a PAE enabled Xen kernel for the dom0? But will I need such a kernel then for the domU''s too? kind regards Sebastian Sorry if this mail hits the M/L twice, I sent the original yesterday afternoon, and still nothing on the list, therefore resending it now. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sebastian Reitenbach schrieb:> Hi,> When this is just not working, then I have to run the dom0 in 32Bit. Do I > can then assign 4GB RAM to each domU, or will the dom0 be unable to handle > that amount of memory? I assume I need a PAE enabled Xen kernel for the > dom0? But will I need such a kernel then for the domU''s too?Take a look at xm info if you''re running a 64bit hypervisor on recent platform you should see something like xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 this indicates, you''re able to run PV 64bin, PV 32bit PAE, hvm x86, hvm PAE and hvm 64bit ... NOT PV 32bit ;) hope this helps. btw. if you quickly need a 2.6.18.8 kernel, you can take http://boreas.netz-haut.net/pub/kernelpack-2.6.18.8-xen-x86_32.tar.gz I''ve built this one from xen 3.2.0. cheers, Stephan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, That looks like a paravirtualization error. Do you have a xen compatible kernel booting in your domain? Tait -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Sebastian Reitenbach Sent: Friday, February 22, 2008 2:38 AM To: xen-users@lists.xensource.com Subject: [Xen-users] 32Bit PVM on 64Bit dom0? Hi, I tried to start a 32Bit PVM system on a 64Bit dom0, and got the following error: Using config file "./VM1". Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n'') and it just did not started. Is ist just because of the different 32/64Bit of domU and dom0? The xen in the dom0 is configured to be backward compatible. The dom0 is a xen 3.1.0, the domU is a xen 3.0.3. When this is just not working, then I have to run the dom0 in 32Bit. Do I can then assign 4GB RAM to each domU, or will the dom0 be unable to handle that amount of memory? I assume I need a PAE enabled Xen kernel for the dom0? But will I need such a kernel then for the domU''s too? kind regards Sebastian Sorry if this mail hits the M/L twice, I sent the original yesterday afternoon, and still nothing on the list, therefore resending it now. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
If you look at xm info you should see the list of supported architectures on a line with the label "xen_caps." My 64-bit XEN boxes require that domUs use a 32-bit PAE kernel.>>> On 2008/02/22 at 00:38, "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> wrote:Hi, I tried to start a 32Bit PVM system on a 64Bit dom0, and got the following error: Using config file "./VM1". Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n'') and it just did not started. Is ist just because of the different 32/64Bit of domU and dom0? The xen in the dom0 is configured to be backward compatible. The dom0 is a xen 3.1.0, the domU is a xen 3.0.3. When this is just not working, then I have to run the dom0 in 32Bit. Do I can then assign 4GB RAM to each domU, or will the dom0 be unable to handle that amount of memory? I assume I need a PAE enabled Xen kernel for the dom0? But will I need such a kernel then for the domU''s too? kind regards Sebastian Sorry if this mail hits the M/L twice, I sent the original yesterday afternoon, and still nothing on the list, therefore resending it now. This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I tried to start a 32Bit PVM system on a 64Bit dom0, and got the following > error: > Using config file "./VM1". > Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest type > xen-3.0-x86_32 not supported by xen kernel, sorry\n'')That is a non-PAE kernel, right? If it were PAE, I''d expect the guest type to be "xen-3.0-x86_32p". Only 32-bit PAE kernels will boot on 64-bit so you''d need to get a guest kernel with PAE enabled (either rebuild it or see if your distro has a PAE-enabled package).> and it just did not started. Is ist just because of the different 32/64Bit > of domU and dom0? The xen in the dom0 is configured to be backward > compatible. The dom0 is a xen 3.1.0, the domU is a xen 3.0.3.3.1 had backwards compatibility for 32-bit PAE domains on a 64-bit Xen, however, if I recall correctly the original 3.1.0 release didn''t work with older 32-bit guest kernels (full backwards compatibility was implemented in a subsequent patch - it''s probably in a later release in the 3.1 series). So you *might* need a newer release of 3.1 to run your guest; I''m not sure on this, though because I never really looked into what the limitation was. I think a few things (live migration / save-restore) were also not supported for domains of a different addressing mode to dom0 under 3.1 (e.g. can''t save/restore/migrate 32-bit domUs if dom0 is 64-bit, or vice-versa) but the basic functionality of booting and running domains ought to work OK...> When this is just not working, then I have to run the dom0 in 32Bit. Do I > can then assign 4GB RAM to each domU, or will the dom0 be unable to handle > that amount of memory? I assume I need a PAE enabled Xen kernel for the > dom0? But will I need such a kernel then for the domU''s too?You can have 32-bit dom0 and still run 64-bit domUs, if your Xen itself is 64-bit; you should be able to run 32-bit PAE domUs with > 4G of memory as well, I think. Hope that helps, Cheers, Mark> kind regards > Sebastian > > Sorry if this mail hits the M/L twice, I sent the original yesterday > afternoon, and still nothing on the list, therefore resending it now. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, "Nick Couchman" <Nick.Couchman@seakr.com> wrote:> If you look at xm info you should see the list of supported architectureson a line with the label "xen_caps." My 64-bit XEN boxes require that domUs use a 32-bit PAE kernel. this is interesting information, taking the right kernel, made the domU start up. thanks Sebastian> > >>> On 2008/02/22 at 00:38, "Sebastian Reitenbach"<sebastia@l00-bugdead-prods.de> wrote:> Hi, > > I tried to start a 32Bit PVM system on a 64Bit dom0, and got the following > error: > Using config file "./VM1". > Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest typexen-3.0-x86_32> not supported by xen kernel, sorry\n'') > > and it just did not started. Is ist just because of the different 32/64Bit > of domU and dom0? The xen in the dom0 is configured to be backward > compatible. The dom0 is a xen 3.1.0, the domU is a xen 3.0.3. > > When this is just not working, then I have to run the dom0 in 32Bit. Do I > can then assign 4GB RAM to each domU, or will the dom0 be unable to handle > that amount of memory? I assume I need a PAE enabled Xen kernel for the > dom0? But will I need such a kernel then for the domU''s too? > > kind regards > Sebastian > > Sorry if this mail hits the M/L twice, I sent the original yesterday > afternoon, and still nothing on the list, therefore resending it now. > > > > > > This e-mail may contain confidential and privileged material for the soleuse of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.>_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users