WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] SuSE 9.3 on a SMP machine

From: "Ralph Passgang" <ralph@xxxxxxxxxxxxx>
Am Mittwoch, 11. Januar 2006 19:49 schrieb Fernando Maior:
On 1/11/06, Daniel Bauer <dbauer@xxxxxxxxxxx> wrote:
> From: "Fernando Maior" <fernando.souto.maior@xxxxxxxxx>
>
> > On 1/10/06, Daniel Bauer <dbauer@xxxxxxxxxxx> wrote:
> >> Hi @all,
> >>
> >> I've installed a SuSE 9.3 with XEN 2.
> >>
> >> My machine have 8 cpu's and 10 GB RAM, but when I start the XEN
> >> kernel,
> >> only one cpu and 2 GB RAM appear. How to enable everything?
> >
> > As I recall it, Xen 2.x does not have support for more then 4gb > > and
> > SMP. Try Xen 3.x and OpenSUSE, and remember to download and
> > install Xen RPMs from garloff, at:
> >
> > http://www.suse.de/~garloff/linux/xen/RPMs-100/8259/
> >
> > The ones in the DVD are in bad shape.
>
> Hi Fernando,
>
> there are no xen 3 rpm for SuSE 9.3, so I installed SuSE 10.0 and
> updated with the rpm from Garloff, but when I try to start the xen
> kernel, a kernel panic comes up (same problem with the > DVD+Updates).
>
> I also started the system with the xen test cd and it looks like it
> works.
>
> My favorite is to run xen 3 on SuSE 9.3, is there a possibility > for?
>
> Thanks a lot
> Daniel

Daniel,

Usually kernel panics because you did not copy the kernel and
initrd from the /boot of dom0 to the /boot of the xen guest domain
you are trying to start. Just try it, may be that is what is needed.

copy kernel image and initrd to /boot of a domainU? Why that?

You should copy the correct modules directory (for
example /lib/modules/2.6.12.6-xen) to your domainU, so that modules can be
loaded in your guest domain.

The kernel and initrd has to be configured in the config of every domainU and gets loaded at domainUs inital "boot". They don't need to exist as files in /boot of any domainU. The domainU doesn't even tries to access them.

not the guest domain stop with kernelpanic, the machine couldn't boot, because of the missing modules ...

Daniel



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users