Re: [Xen-users] DomU kernel parameters

[Christian <chris@xxxxxxxxxxxxxxxx>]

Hi Henning,

I got it :)
Thanks for your help.

max_loop Solution for DomU( SLES10):
do not use "extra = 3 max_loop=64" inside your vm-config-file
just let it as is: "extra = 3"

instead edit "/etc/modprobe.conf.local" inside your DomU and add
options loop max_loop=64

then it works as expected.
Now I'm able to use this vm as an autoyast Server ;)

Henning Sprang schrieb:
> On 2/7/07, Christian Wittmer <chris@xxxxxxxxxxxxxxxx> wrote:
>> It's a module: (on Dom0 and DomU)
>> srv-ux-0014:/etc/xen/vm # zcat /proc/config.gz | grep BLK_DEV_LOOP
>> CONFIG_BLK_DEV_LOOP=m
>>
>> for dom0 "max_loop=64" works
>> for domU "extra = "3 TERM=xterm max_loop=64"" this does not work.
>
> When it's a module you need to make sure it's loaded with this param.
> The module doesn't use the parameter from the kernel command line.
> You have to load the module for example like
> modprobe loop max_loop=64
> or add sometthing like that in your module config.
>
> The tap:aio itamar wrote about might also work - but on some settings
> we had problems with the stability of this, and not sure if all
> distribution packages already support this.
>
> Henning
>
> _______________________________________________
> 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