Hello, i run Debian Etch amd64 on my dom0, if i try to create a domU with a 32Bit Kernel, i get: Using config file "123.conf". Error: (22, ''Invalid argument'') If i try a 64Bit guest kernel, it works fine. Is there a way to run a 32-Bit domU on a 64bit based dom0 os? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
You might do a "xm info" to see what types of domUs are supported under the version of Xen you''re running, which is displayed on the xen_caps line. Mine looks like this: 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 What''s important to note here is that the Xen version I''m running only supports 32-bit PAE kernels for PV domUs (for HVMs it supports non-PAE, but not for paravirtualized kernels). Check yours and see which types of kernels are supported - you may need to use a PAE kernel, instead. -Nick>>> On 2008/05/20 at 05:51, MS <ms@toefke.com> wrote:Hello, i run Debian Etch amd64 on my dom0, if i try to create a domU with a 32Bit Kernel, i get: Using config file "123.conf". Error: (22, ''Invalid argument'') If i try a 64Bit guest kernel, it works fine. Is there a way to run a 32-Bit domU on a 64bit based dom0 os? 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
There is only xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 but no "xen-3.0-x86_32p". How can i change it? Another Dom0-kernel? Nick Couchman schrieb:> You might do a "xm info" to see what types of domUs are supported > under the version of Xen you''re running, which is displayed on the > xen_caps line. Mine looks like this: > 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 > > What''s important to note here is that the Xen version I''m running only > supports 32-bit PAE kernels for PV domUs (for HVMs it supports > non-PAE, but not for paravirtualized kernels). Check yours and see > which types of kernels are supported - you may need to use a PAE > kernel, instead. > > -Nick > > >>> On 2008/05/20 at 05:51, MS <ms@toefke.com> wrote: > Hello, > > i run Debian Etch amd64 on my dom0, > if i try to create a domU with a 32Bit Kernel, i get: > > Using config file "123.conf". > Error: (22, ''Invalid argument'') > > If i try a 64Bit guest kernel, it works fine. > > Is there a way to run a 32-Bit domU on a 64bit based dom0 os? > > > ------------------------------------------------------------------------ > 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 don''t think it has to do with the dom0 kernel, I think it has to do with the Xen hypervisor you''re loading. What version of Xen are you running? -Nick>>> On 2008/05/20 at 06:18, MS <ms@toefke.com> wrote:There is only xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 but no "xen-3.0-x86_32p". How can i change it? Another Dom0-kernel? Nick Couchman schrieb:> You might do a "xm info" to see what types of domUs are supported > under the version of Xen you''re running, which is displayed on the > xen_caps line. Mine looks like this: > 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 > > What''s important to note here is that the Xen version I''m running only > supports 32-bit PAE kernels for PV domUs (for HVMs it supports > non-PAE, but not for paravirtualized kernels). Check yours and see > which types of kernels are supported - you may need to use a PAE > kernel, instead. > > -Nick > > >>> On 2008/05/20 at 05:51, MS <ms@toefke.com> wrote: > Hello, > > i run Debian Etch amd64 on my dom0, > if i try to create a domU with a 32Bit Kernel, i get: > > Using config file "123.conf". > Error: (22, ''Invalid argument'') > > If i try a 64Bit guest kernel, it works fine. > > Is there a way to run a 32-Bit domU on a 64bit based dom0 os? > > > ------------------------------------------------------------------------ > 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.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
It was out of the dist deb. I compiled it by my self, now it works fine. 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 Thank you! Nick Couchman schrieb:> I don''t think it has to do with the dom0 kernel, I think it has to do > with the Xen hypervisor you''re loading. What version of Xen are you > running? > > -Nick > > >>> On 2008/05/20 at 06:18, MS <ms@toefke.com> wrote: > There is only > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p > hvm-3.0-x86_64 > > but no "xen-3.0-x86_32p". > > How can i change it? Another Dom0-kernel? > > Nick Couchman schrieb: > > You might do a "xm info" to see what types of domUs are supported > > under the version of Xen you''re running, which is displayed on the > > xen_caps line. Mine looks like this: > > 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 > > > > What''s important to note here is that the Xen version I''m running only > > supports 32-bit PAE kernels for PV domUs (for HVMs it supports > > non-PAE, but not for paravirtualized kernels). Check yours and see > > which types of kernels are supported - you may need to use a PAE > > kernel, instead. > > > > -Nick > > > > >>> On 2008/05/20 at 05:51, MS <ms@toefke.com> wrote: > > Hello, > > > > i run Debian Etch amd64 on my dom0, > > if i try to create a domU with a 32Bit Kernel, i get: > > > > Using config file "123.conf". > > Error: (22, ''Invalid argument'') > > > > If i try a 64Bit guest kernel, it works fine. > > > > Is there a way to run a 32-Bit domU on a 64bit based dom0 os? > > > > > > ------------------------------------------------------------------------ > > 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. > > ------------------------------------------------------------------------ > 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
If you''ve upgraded Xen make sure you have properly uninstalled the old tools and installed the new ones to match your Xen. nb. to actually use 32-on-64 you also need a sufficiently new dom0 kernel that supports this feature. Cheers, Mark On Tuesday 20 May 2008, MS wrote:> It was out of the dist deb. > I compiled it by my self, now it works fine. > > 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 > > Thank you! > > Nick Couchman schrieb: > > I don''t think it has to do with the dom0 kernel, I think it has to do > > with the Xen hypervisor you''re loading. What version of Xen are you > > running? > > > > -Nick > > > > >>> On 2008/05/20 at 06:18, MS <ms@toefke.com> wrote: > > > > There is only > > > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p > > hvm-3.0-x86_64 > > > > but no "xen-3.0-x86_32p". > > > > How can i change it? Another Dom0-kernel? > > > > Nick Couchman schrieb: > > > You might do a "xm info" to see what types of domUs are supported > > > under the version of Xen you''re running, which is displayed on the > > > xen_caps line. Mine looks like this: > > > 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 > > > > > > What''s important to note here is that the Xen version I''m running only > > > supports 32-bit PAE kernels for PV domUs (for HVMs it supports > > > non-PAE, but not for paravirtualized kernels). Check yours and see > > > which types of kernels are supported - you may need to use a PAE > > > kernel, instead. > > > > > > -Nick > > > > > > >>> On 2008/05/20 at 05:51, MS <ms@toefke.com> wrote: > > > > > > Hello, > > > > > > i run Debian Etch amd64 on my dom0, > > > if i try to create a domU with a 32Bit Kernel, i get: > > > > > > Using config file "123.conf". > > > Error: (22, ''Invalid argument'') > > > > > > If i try a 64Bit guest kernel, it works fine. > > > > > > Is there a way to run a 32-Bit domU on a 64bit based dom0 os? > > > > > > > > > ----------------------------------------------------------------------- > > >- 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. > > > > ------------------------------------------------------------------------ > > 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-- 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
> If you''ve upgraded Xen make sure you have properly uninstalled the old tools > and installed the new ones to match your Xen. > > nb. to actually use 32-on-64 you also need a sufficiently new dom0 kernel that > supports this feature. > > Cheers, > Mark >Hello, I am hanging also on this issue, I want to a boot 32bit debian domu on my 64bit host with XEN 3.2.1. The 32bit debian 4.0 boots fine with my default 64bit domU kernel. This makes me really wonder. But with a 64bit kernel the 32bit domU is not that usable as I thought. For example, openpkg and probably other software looks what kernel is running and then thinks its on a 64bit system. Now I am trying to figure out a new kernel-config to make this work. Maybe you can give some tips what changes to the kernel configs are needed. Thanks in advance Jens _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday 20 May 2008, Jens Kleikamp wrote:> > If you''ve upgraded Xen make sure you have properly uninstalled the old > > tools and installed the new ones to match your Xen. > > > > nb. to actually use 32-on-64 you also need a sufficiently new dom0 kernel > > that supports this feature. > > > > Cheers, > > Mark > > Hello, > > I am hanging also on this issue, I want to a boot 32bit debian domu on > my 64bit host with XEN 3.2.1. > > The 32bit debian 4.0 boots fine with my default 64bit domU kernel. This > makes me really wonder. > > But with a 64bit kernel the 32bit domU is not that usable as I thought. > For example, openpkg and probably other software looks what kernel is > running and then thinks its on a 64bit system.OK. 32-bit distros can often boot on a 64-bit kernel due to the binary compatibility provided. Your package manager''s confusion can probably be fixed but there are other things which may still break.> Now I am trying to figure out a new kernel-config to make this work. > > Maybe you can give some tips what changes to the kernel configs are needed.On 3.2.1 you should be able to boot a 32-bit Xenified kernel instead of the 64-bit one and have it Just Work(TM). Have you tried this? Were there problems? The 32-bit kernel needs to support PAE (CONFIG_HIGHMEM_64G) in order to run on 64-bit Xen. I''m not sure if suspend/resume/migration will work for that setup but just running the domain paravirtualised ought to be OK. Cheers, Mark -- 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
Mark Williamson schrieb:> On Tuesday 20 May 2008, Jens Kleikamp wrote: >>> If you''ve upgraded Xen make sure you have properly uninstalled the old >>> tools and installed the new ones to match your Xen. >>> >>> nb. to actually use 32-on-64 you also need a sufficiently new dom0 kernel >>> that supports this feature. >>> >>> Cheers, >>> Mark >> Hello, >> >> I am hanging also on this issue, I want to a boot 32bit debian domu on >> my 64bit host with XEN 3.2.1. >> >> The 32bit debian 4.0 boots fine with my default 64bit domU kernel. This >> makes me really wonder. >> >> But with a 64bit kernel the 32bit domU is not that usable as I thought. >> For example, openpkg and probably other software looks what kernel is >> running and then thinks its on a 64bit system. > > OK. 32-bit distros can often boot on a 64-bit kernel due to the binary > compatibility provided. Your package manager''s confusion can probably be > fixed but there are other things which may still break. > >> Now I am trying to figure out a new kernel-config to make this work. >> >> Maybe you can give some tips what changes to the kernel configs are needed. > > On 3.2.1 you should be able to boot a 32-bit Xenified kernel instead of the > 64-bit one and have it Just Work(TM). Have you tried this? Were there > problems? The 32-bit kernel needs to support PAE (CONFIG_HIGHMEM_64G) in > order to run on 64-bit Xen. > > I''m not sure if suspend/resume/migration will work for that setup but just > running the domain paravirtualised ought to be OK. > > Cheers, > Mark >I build my 32bit xen-dumU Kernel with CONFIG_HIGHMEM_64G set and all is fine. Thank you very much! Thanks Jens _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users