Am Dienstag, 31. Januar 2006 14:20 schrieb Molle Bestefich:
> Stephan Augustin wrote:
> > > That may be true, but it's much easier to adjust it on the kernel
> > > command line. Just add max_loop=128 or some such.
> >
> > Do you mean the commandline
> > kernel /boot/xen.gz
> > in /boot/grub/menu.lst ?
>
> No, that's the parameter line for the hypervisor.
> The loop devices exist within the domain 0 kernel.
> So you must append the max_loop parameter to the
> "module=<linux-dom0-kernel>" line in your grub configuration file.
>
> Sorry, should've mentioned that.
Sorry , but this doesnt work for me..
do I have to do something else for get this working ?
i have this script :
"If you have the “loop” driver compiled into your kernel, you need to add
“max_loop=64” to your kernel boot arguments (the “append=” line in lilo.conf,
or to the end of the “kernel” line in grub’s menu.lst), and reboot."
If you have the “loop” driver compiled as a module, you need to insmod it with
“max_loop=64” added to its options. On Debian systems, you
edit /etc/modules.conf and add “options loop max_loop=64”, and “rmmod loop”
“modprobe loop”.
If you’re using devfs, then stop here. The new /dev/loop* will appear
automatically. If not, you’ll need to edit and run MAKEDEV:
Change:
loop)
for part in 0 1 2 3 4 5 6 7
do
makedev loop$part b 7 $part $disk
done
;;
To:
loop)
for part in `seq 0 63`
do
makedev loop$part b 7 $part $disk
done
;;
And run “MAKEDEV loop”.
"
with the original debian -kernel, It is possible to use the modules - but this
doesnt create more loop-devices.
and even the kernel /boot/vmlinuz-2.6[...] max_loop=64
line does not work.
under the xen-kernel the command-line doesnt work ( I dont get more devices) ,
and the modprobe command aborts with an error
stephan
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home