[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FW: FW: [Xen-users] Xen and OpenSSI


  • To: Owen Campbell <owen@xxxxxxxxxxxxx>
  • From: N Clements <optionc.ltd@xxxxxxxxx>
  • Date: Fri, 17 Feb 2006 09:17:48 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 17 Feb 2006 15:30:35 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bNFMZM513LzTVT1sBLhECo7l92FiYSD/QbqwQ7w7vlFyCcUMg38TYlNT8dPqHyVzOET2GoACOp6e2/F6XHPNjCGuwjd8oeqr4qdArgLwmGzKLlA2HV6pw2RskqSq3dr1lR0pq95OTdJXlUu+xgCK5tkJs11YSBhXveX9Lj7ZCCA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

What's the error message this time? The reason I ask is that my
version of node1 has the loop devices (/dev/loop{0-7}) -- the SSI
kernel (the one from the OpenSSI site) has the loop devices built-in.

I believe another reason the mkinitrd can fail is due to low memory. I
seem to recall that when I was first setting it up I tried a 64MB
machine (maybe less) and it didn't like that at all.

Option-C will probably be making an SSI kernel package available at
some point in the near future, and that will have a set of modules
with it, but that's not going to help you now.


On 2/17/06, Owen Campbell <owen@xxxxxxxxxxxxx> wrote:
> Almost there!!!!
>
> I've now got the domU to boot (by copying in the modules for
> 2.6.11-ocxenu as suggested).
>
> My problem now is creating the initrd to add new nodes to the cluster.
> Because I downloaded the openssi kernel (which is based on 2.6.10), I
> don't have the associated modules and the mkinitrd fails.
>
> Is there anywhere I can get them?
>
> Owen
>
> -----Original Message-----
> From: N Clements [mailto:optionc.ltd@xxxxxxxxx]
> Sent: 16 February 2006 17:01
> To: Owen Campbell
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: FW: [Xen-users] Xen and OpenSSI
>
> You need to make sure you've got the appropriate modules inside the
> domU. Look in the /lib/modules directory. If there's nothing in there
> then you'll need to copy them from the dom0. Either shut down the
> domU, mount the image/device with the root vbd and copy them across,
> or scp/ftp  them in.
>
> For example (from the dom0, assuming the domU is not running):
> # mkdir /mnt/domU
> # mount -o loop /images/domU.img /mnt/domU
> # cp -dpR /lib/modules/2.6.11-ocxenu /mnt/domU/lib/modules
> # umount /mnt/domU
>
> Reboot your domU. Then try the modprobe function again.
>
> After that mkinitrd ought to work.
>
>
> On 2/16/06, Owen Campbell <owen@xxxxxxxxxxxxx> wrote:
> > Ok, I tried from scratch again and here's where I got to.....
> >
> > When I run 'mkinitrd -o /tmp/initrd', I get
> >
> > cpio: initrd/lib/libc.so.6 not created: newer or same age version
> exists
> > cpio: initrd/lib/libcluster.so.0 not created: newer or same age
> version
> > exists
> > 4584+0 records in
> > 4584+0 records out
> > 4694016 bytes transferred in 0.291641 seconds (16095183 bytes/sec) All
> > of your loopback devices are in use!
> >
> > And initrd is created in the /tmp directory
> >
> > If I run 'modprobe loop' I get
> >
> > modprobe: Can't open dependencies file
> > /lib/modules/2.6.11-ocxenu/modules.dep (No such file or directory)
> >
> > So it looks like you were all correct and the problem is initrd
> > creation!!!
> >
> > I'm afraid I've always avoided kernel building, so this is all a bit
> new
> > to me. Any ideas how I get the initrd created?
> >
> > Owen
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.