Hi, my DomU has only 8 loop devices. How can I add kernel paramerters to my DomU to have more then 8 loop devices. For this to have in Dom0, that''s no question ''max_loop=64''. Any help would be apreciated. Thanks Chris ----------------------------------------- Diese E-Mail wurde durch SquirrelMail versandt "Webmail for nuts!" ----------------------------------------- Bereitgestellt fuer Kunden von Scorpio IT http://www.scorpio-it.net _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/6/07, Christian Wittmer <chris@computersalat.de> wrote:> Hi, > > my DomU has only 8 loop devices. How can I add kernel paramerters to my > DomU to have more then 8 loop devices. > > For this to have in Dom0, that''s no question ''max_loop=64''.Use the "extra" config pareamater in the vm config file to add arbitrary kernel options. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> but still can only use 8 loops :( > > any idea left ?Is your loop driver compiled in or do you use a mdoule? The module is not affected by the kernel params - you have to load it with the parameter max_loop. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Henning> > Is your loop driver compiled in or do you use a mdoule? > The module is not affected by the kernel params - you have to load it with > the parameter max_loop.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. after boot I have 8 loop devices. yalla:/dev # dir lo* srw-rw-rw- 1 root root 0 Feb 7 10:28 log brw-r----- 1 root disk 7, 0 Feb 7 10:28 loop0 brw-r----- 1 root disk 7, 1 Feb 7 10:28 loop1 brw-r----- 1 root disk 7, 2 Feb 7 10:28 loop2 brw-r----- 1 root disk 7, 3 Feb 7 10:28 loop3 brw-r----- 1 root disk 7, 4 Feb 7 10:28 loop4 brw-r----- 1 root disk 7, 5 Feb 7 10:28 loop5 brw-r----- 1 root disk 7, 6 Feb 7 10:28 loop6 brw-r----- 1 root disk 7, 7 Feb 7 10:28 loop7 I increase them with: i=8; j=64; while [ $i -lt $j ]; do mknod -m640 /dev/loop$i b 7 $i; i=$[$i+1]; done but still only 8 usable and after reboot there are again only 8 loops(0-7). Why doesn''t keep it the new generated loops (8-63)? Thanks for help Christian> > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >----------------------------------------- Diese E-Mail wurde durch SquirrelMail versandt "Webmail for nuts!" ----------------------------------------- Bereitgestellt fuer Kunden von Scorpio IT http://www.scorpio-it.net _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
use tap:aio then you don''t need the loop module. -------------------- Itamar Reis Peixoto e-mail: itamar@ispbrasil.com.br msn: itamarjp@starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 ----- Original Message ----- From: "Henning Sprang" <henning_sprang@gmx.de> To: "Christian Wittmer" <chris@computersalat.de> Cc: <xen-users@lists.xensource.com> Sent: Wednesday, February 07, 2007 10:55 AM Subject: Re: [Xen-users] DomU kernel parameters> >> but still can only use 8 loops :( >> >> any idea left ? > > Is your loop driver compiled in or do you use a mdoule? > The module is not affected by the kernel params - you have to load it with > the parameter max_loop. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/7/07, Christian Wittmer <chris@computersalat.de> 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@lists.xensource.com http://lists.xensource.com/xen-users
Hi Itamar, Itamar Reis Peixoto schrieb:> use tap:aio then you don''t need the loop module.I do not really understand that. I only know "tap:aio" in conjunction with "disk" when using xen "Images", but I use "phy" disks. I will give the module options a try ;) Thanks Chris> > -------------------- > > Itamar Reis Peixoto > > e-mail: itamar@ispbrasil.com.br > msn: itamarjp@starmedia.com > skype: itamarjp > icq: 81053601 > +55 34 3238 3845 > +55 11 4063 5033 > ----- Original Message ----- From: "Henning Sprang" > <henning_sprang@gmx.de> > To: "Christian Wittmer" <chris@computersalat.de> > Cc: <xen-users@lists.xensource.com> > Sent: Wednesday, February 07, 2007 10:55 AM > Subject: Re: [Xen-users] DomU kernel parameters > > >> >>> but still can only use 8 loops :( >>> >>> any idea left ? >> >> Is your loop driver compiled in or do you use a mdoule? >> The module is not affected by the kernel params - you have to load it >> with the parameter max_loop. >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@computersalat.de> 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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/8/07, Christian <chris@computersalat.de> wrote:> Hi Itamar, > > Itamar Reis Peixoto schrieb: > > use tap:aio then you don''t need the loop module. > I do not really understand that. I only know "tap:aio" in conjunction > with "disk" when using xen "Images", but I use "phy" disks.no, it works with both. I am only unsire if it is available on all distributions. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/8/07, Henning Sprang <henning_sprang@gmx.de> wrote:> On 2/8/07, Christian <chris@computersalat.de> wrote: > > > use tap:aio then you don''t need the loop module. > > I do not really understand that. I only know "tap:aio" in conjunction > > with "disk" when using xen "Images", but I use "phy" disks. > > no, it works with both. > I am only unsire if it is available on all distributions.But, hmm, wait. I wasn''t completely awake when writing this ;) : You said, on dom0 you have solved the loop problem, but for some other reason (that is not xen specific) you need more loop devices _inside_ the domU. For this, the tap:aio doesn''t help, it acts only inside dom0, for getting the domU started, but has no affect on the number of loop devices available inside the domU. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users