General user support mailing list
<a0fb14ab-7aa0-166a-8cd7-7342d508a94f@arcor.de>Hi, i use Alpine-Linux-Xen4.12 with kernel 4.19.58-0-vanilla with several domU's. Now I need more than 8 loop-devices for domU's. So, I tried to configure max_loop=32. Where i can configure for permanent usage ? Any idea? best regards Helmut
<CALci+FShPeX4quQJ=W0Cmn-O7RBVz46zyUyuFSLg70JseYGf7A@mail.gmail.com>
<a0fb14ab-7aa0-166a-8cd7-7342d508a94f@arcor.de>
(view parent)
El jue., 1 de ago. de 2019 a la(s) 15:39, Helmut (helmut_pohl@arcor.de) escribió: > So, I tried to configure max_loop=32. Where i can configure for > permanent usage ? > http://qgqlochekone.blogspot.com/2010/10/lopp-management-manejo-de-loops.html > > Any idea? > > best regards > Helmut > > >
<alpine.DEB.2.21.99999.352.1908011727010.8246@trent.utfs.org>
<a0fb14ab-7aa0-166a-8cd7-7342d508a94f@arcor.de>
(view parent)
On Thu, 1 Aug 2019, Helmut wrote: > i use Alpine-Linux-Xen4.12 with kernel 4.19.58-0-vanilla with several > domU's. Now I need more than 8 loop-devices for domU's. > So, I tried to configure max_loop=32. Where i can configure for > permanent usage ? Depends on where you need those loop devices. If they are needed in the Dom0 _for_ the DomUs, then max_loop=32 can be added to the kernel's command line in the Dom0's boot loader, i.e /boot/extlinux.conf. Slightly off-topic, but: why do you need so many loop-devices? If these loop devices are needed within the DomUs, then it depends how these are started. PV domains can accept an "extra=" line for kernel parameters in the domU configuration file. Or maybe it's a HVM domain and has its own bootloader (pygrub), then the max_loop=32 should be added to the kernel command line within that domain. Or maybe the DomU has "loop" compiled as a module, then it should go into the module configuration within that domain. So many possibilities! :-D C. -- BOFH excuse #305: IRQ-problems with the Un-Interruptible-Power-Supply
<fc1573bf-e97a-d1e7-2b06-7b5553faa256@arcor.de>
<CALci+FShPeX4quQJ=W0Cmn-O7RBVz46zyUyuFSLg70JseYGf7A@mail.gmail.com>
(view parent)
Hello, thx for the link. My actual config is: /etc/modprobe.d/loop options loop max_loop=32 /etc/modprobe.d/xen options loop max_loop=32 /boot/extlinux.conf APPEND xen.gz dom0_mem=2048M dom0_max_vcpus=2 dom0_vcpus_pin --- vmlinuz-vanilla root=UUID=dad93766-6001-4458-a5de-d6ac14007b4c modules=sd-mod,usb-storage,ext4,loop,xen-pciback nomodeset quiet rootfstype=ext4 max_loop=32 xen-pciback.hide=(0000:04:01.0) --- initramfs-vanilla NO SUCCESS !! only my manual script has succes: for i in $(seq 8 32) ; do mknod /dev/loop$i b 7 $i ;done chmod 664 /dev/loop* chown 0.disk /dev/loop* But I need a permanently configure, did you more idea`s ? best regards Helmut Am 02.08.2019 um 02:08 schrieb PICCORO McKAY Lenz: > > El jue., 1 de ago. de 2019 a la(s) 15:39, Helmut (helmut_pohl@arcor.de > <mailto:helmut_pohl@arcor.de>) escribió: > > So, I tried to configure max_loop=32. Where i can configure for > permanent usage ? > > > > http://qgqlochekone.blogspot.com/2010/10/lopp-management-manejo-de-loops.html > > > > > Any idea? > > best regards > Helmut > >
<96332485-3151-db7d-42ea-460009edec42@arcor.de>
<alpine.DEB.2.21.99999.352.1908011727010.8246@trent.utfs.org>
(view parent)
Hello Christian, thx for your help. My actual config is: /etc/modprobe.d/loop options loop max_loop=32 /etc/modprobe.d/xen options loop max_loop=32 /boot/extlinux.conf APPEND xen.gz dom0_mem=2048M dom0_max_vcpus=2 dom0_vcpus_pin --- vmlinuz-vanilla root=UUID=dad93766-6001-4458-a5de-d6ac14007b4c modules=sd-mod,usb-storage,ext4,loop,xen-pciback nomodeset quiet rootfstype=ext4 max_loop=32 xen-pciback.hide=(0000:04:01.0) --- initramfs-vanilla NO SUCCESS !! only my manual script has succes: for i in $(seq 8 32) ; do mknod /dev/loop$i b 7 $i ;done chmod 664 /dev/loop* chown 0.disk /dev/loop* But I need a permanently configure in dom0 for start of 10 domU within hd-devices, did you more idea`s ? best regards Helmut Am 02.08.2019 um 02:34 schrieb Christian Kujau: > On Thu, 1 Aug 2019, Helmut wrote: >> i use Alpine-Linux-Xen4.12 with kernel 4.19.58-0-vanilla with several >> domU's. Now I need more than 8 loop-devices for domU's. >> So, I tried to configure max_loop=32. Where i can configure for >> permanent usage ? > Depends on where you need those loop devices. > > If they are needed in the Dom0 _for_ the DomUs, then max_loop=32 can be > added to the kernel's command line in the Dom0's boot loader, i.e > /boot/extlinux.conf. Slightly off-topic, but: why do you need so many > loop-devices? > > If these loop devices are needed within the DomUs, then it depends how > these are started. PV domains can accept an "extra=" line for kernel > parameters in the domU configuration file. Or maybe it's a HVM domain and > has its own bootloader (pygrub), then the max_loop=32 should be added to > the kernel command line within that domain. > > Or maybe the DomU has "loop" compiled as a module, then it should go into > the module configuration within that domain. > > So many possibilities! :-D > > C.
<CALci+FTP0DPoi1jKnSwXqibxL+grpaChzZHX52Wafu=JyOMdhQ@mail.gmail.com>
<fc1573bf-e97a-d1e7-2b06-7b5553faa256@arcor.de>
(view parent)
El vie., 2 de ago. de 2019 a la(s) 05:36, Helmut (helmut_pohl@arcor.de) escribió: > > thx for the link. My actual config is: > > APPEND xen.gz dom0_mem=2048M dom0_max_vcpus=2 dom0_vcpus_pin --- vmlinuz-vanilla root=UUID=dad93766-6001-4458-a5de-d6ac14007b4c modules=sd-mod,usb-storage,ext4,loop,xen-pciback nomodeset quiet rootfstype=ext4 max_loop=32 xen-pciback.hide=(0000:04:01.0) --- initramfs-vanilla OH xen vm! so i must do furter investigations.. i'll back with some info.. later > > NO SUCCESS !! > > > only my manual script has succes: > > for i in $(seq 8 32) ; do mknod /dev/loop$i b 7 $i ;done > chmod 664 /dev/loop* > chown 0.disk /dev/loop* > > > But I need a permanently configure, did you more idea`s ? > > best regards > Helmut > > > > > Am 02.08.2019 um 02:08 schrieb PICCORO McKAY Lenz: > > > El jue., 1 de ago. de 2019 a la(s) 15:39, Helmut (helmut_pohl@arcor.de) escribió: >> >> So, I tried to configure max_loop=32. Where i can configure for >> permanent usage ? > > > > http://qgqlochekone.blogspot.com/2010/10/lopp-management-manejo-de-loops.html > > >> >> >> Any idea? >> >> best regards >> Helmut >> >>
<7d1e84c4-fd53-0d89-0c6e-d70f46a5e3fd@arcor.de>
<CALci+FTP0DPoi1jKnSwXqibxL+grpaChzZHX52Wafu=JyOMdhQ@mail.gmail.com>
(view parent)
Hello, do you have a solution for my problem with Alpine-Linux-Xen and max_loops ? best regards Helmut Pohl Am 02.08.2019 um 18:05 schrieb PICCORO McKAY Lenz: > El vie., 2 de ago. de 2019 a la(s) 05:36, Helmut > (helmut_pohl@arcor.de) escribió: >> thx for the link. My actual config is: >> >> APPEND xen.gz dom0_mem=2048M dom0_max_vcpus=2 dom0_vcpus_pin --- vmlinuz-vanilla root=UUID=dad93766-6001-4458-a5de-d6ac14007b4c modules=sd-mod,usb-storage,ext4,loop,xen-pciback nomodeset quiet rootfstype=ext4 max_loop=32 xen-pciback.hide=(0000:04:01.0) --- initramfs-vanilla > OH xen vm! so i must do furter investigations.. i'll back with some info.. later > > >> NO SUCCESS !! >> >> >> only my manual script has succes: >> >> for i in $(seq 8 32) ; do mknod /dev/loop$i b 7 $i ;done >> chmod 664 /dev/loop* >> chown 0.disk /dev/loop* >> >> >> But I need a permanently configure, did you more idea`s ? >> >> best regards >> Helmut >> >> >> >> >> Am 02.08.2019 um 02:08 schrieb PICCORO McKAY Lenz: >> >> >> El jue., 1 de ago. de 2019 a la(s) 15:39, Helmut (helmut_pohl@arcor.de) escribió: >>> So, I tried to configure max_loop=32. Where i can configure for >>> permanent usage ? >> >> >> http://qgqlochekone.blogspot.com/2010/10/lopp-management-manejo-de-loops.html >> >> >>> >>> Any idea? >>> >>> best regards >>> Helmut >>> >>>
<2f74e87d-41fc-505e-3e88-48e435f98a61@cosmoborsky.com>
<7d1e84c4-fd53-0d89-0c6e-d70f46a5e3fd@arcor.de>
(view parent)
On 8/6/19 7:59 AM, Helmut wrote: > Hello, > > do you have a solution for my problem with Alpine-Linux-Xen and max_loops ? > > best regards > Helmut Pohl > Try adding `loop max_loop=32` to /etc/modules and reboot.
<2a4bbe0d-96da-d94c-4244-05647501698c@arcor.de>
<2f74e87d-41fc-505e-3e88-48e435f98a61@cosmoborsky.com>
(view parent)
Hello,
thanks for your help. My actual config is:
/etc/modules
loop max_loop=32
/etc/modprobe.d/loop
options loop max_loop=32
/etc/modprobe.d/xen
options loop max_loop=32
/boot/extlinux.conf
APPEND xen.gz dom0_mem=2048M dom0_max_vcpus=2 dom0_vcpus_pin ---
vmlinuz-vanilla root=UUID=dad93766-6001-4458-a5de-d6ac14007b4c
modules=sd-mod,usb-storage,ext4,loop,xen-pciback nomodeset quiet
rootfstype=ext4 max_loop=32 xen-pciback.hide=(0000:04:01.0) ---
initramfs-vanilla
NO SUCCESS !!
only my manual script has succes:
for i in $(seq 8 32) ; do mknod /dev/loop$i b 7 $i ;done
chmod 664 /dev/loop*
chown 0.disk /dev/loop*
But I need a permanently configure in dom0 for start of 10 domU within
hd-devices, did you more idea`s ?
best regards
Helmut
Am 06.08.2019 um 14:10 schrieb Cosmo Borsky:
> On 8/6/19 7:59 AM, Helmut wrote:
>> Hello,
>>
>> do you have a solution for my problem with Alpine-Linux-Xen and max_loops ?
>>
>> best regards
>> Helmut Pohl
>>
>
> Try adding `loop max_loop=32` to /etc/modules and reboot.
>
<3c595b7d-b26b-815f-25da-1c4432b3b3f9@cosmoborsky.com>
<2a4bbe0d-96da-d94c-4244-05647501698c@arcor.de>
(view parent)
On 8/6/19 8:26 AM, Helmut wrote: > Hello, > > thanks for your help. My actual config is: > > /etc/modules > loop max_loop=32 > > /etc/modprobe.d/loop > options loop max_loop=32 > > /etc/modprobe.d/xen > options loop max_loop=32 > > /boot/extlinux.conf > > APPEND xen.gz dom0_mem=2048M dom0_max_vcpus=2 dom0_vcpus_pin --- > vmlinuz-vanilla root=UUID=dad93766-6001-4458-a5de-d6ac14007b4c > modules=sd-mod,usb-storage,ext4,loop,xen-pciback nomodeset quiet > rootfstype=ext4 max_loop=32 xen-pciback.hide=(0000:04:01.0) --- > initramfs-vanilla > > NO SUCCESS !! > > > only my manual script has succes: > > for i in $(seq 8 32) ; do mknod /dev/loop$i b 7 $i ;done > chmod 664 /dev/loop* > chown 0.disk /dev/loop* > > > But I need a permanently configure in dom0 for start of 10 domU within > hd-devices, did you more idea`s ? > > best regards > Helmut > I see now, when booting only 8 loop modules will be made regardless of the max_loop parameter. The loops will be made when: ``` # ls /dev/loop[0-9]* | wc -l 8 # rmmod loop # modprobe loop max_loop=32 # ls /dev/loop[0-9]* | wc -l 32 ``` The loop module is loaded from the initfs without the /etc/modules and /etc/modprobe.d options. In order to load those options, you will need to add loop to /etc/mkinitfs/mkinitfs.conf, like so: `/etc/mkinitfs/mkinitfs.conf/` ``` features="... loop" ``` After adding loop to your features list, run `mkinitfs` as root and then reboot.
<CALci+FTvDNYLeXk-_KWyWVfO9zKQU5aa_wbkvrp5aAvjhj1rNw@mail.gmail.com>
<2a4bbe0d-96da-d94c-4244-05647501698c@arcor.de>
(view parent)
El mar., 6 de ago. de 2019 a la(s) 08:25, Helmut (helmut_pohl@arcor.de) escribió: > /etc/modules > loop max_loop=32 > /etc/modprobe.d/loop > options loop max_loop=32 > /etc/modprobe.d/xen > options loop max_loop=32 > /boot/extlinux.conf THAT never will work due only affect your main operatin system.. not the xen node The internal emulated system must have all those changes!
<fb2be6a1-83e3-01ed-210a-cfc7fb7fd9ca@cosmoborsky.com>
<3c595b7d-b26b-815f-25da-1c4432b3b3f9@cosmoborsky.com>
(view parent)
After some testing, the `/etc/mkinitfs/mkinitfs.conf` edit is unnecessary. `mkinitfs` is all you need after updating `/etc/modprobe.d/loop.conf` I have posted this on the Alpine Linux Xen wiki page: https://wiki.alpinelinux.org/wiki/Xen_Dom0#Loop_Devices On 8/6/19 8:46 AM, Cosmo Borsky wrote: > On 8/6/19 8:26 AM, Helmut wrote: >> Hello, >> >> thanks for your help. My actual config is: >> >> /etc/modules >> loop max_loop=32 >> >> /etc/modprobe.d/loop >> options loop max_loop=32 >> >> /etc/modprobe.d/xen >> options loop max_loop=32 >> >> /boot/extlinux.conf >> >> APPEND xen.gz dom0_mem=2048M dom0_max_vcpus=2 dom0_vcpus_pin --- >> vmlinuz-vanilla root=UUID=dad93766-6001-4458-a5de-d6ac14007b4c >> modules=sd-mod,usb-storage,ext4,loop,xen-pciback nomodeset quiet >> rootfstype=ext4 max_loop=32 xen-pciback.hide=(0000:04:01.0) --- >> initramfs-vanilla >> >> NO SUCCESS !! >> >> >> only my manual script has succes: >> >> for i in $(seq 8 32) ; do mknod /dev/loop$i b 7 $i ;done >> chmod 664 /dev/loop* >> chown 0.disk /dev/loop* >> >> >> But I need a permanently configure in dom0 for start of 10 domU within >> hd-devices, did you more idea`s ? >> >> best regards >> Helmut >> > > I see now, when booting only 8 loop modules will be made regardless of > the max_loop parameter. > The loops will be made when: > ``` > # ls /dev/loop[0-9]* | wc -l > 8 > # rmmod loop > # modprobe loop max_loop=32 > # ls /dev/loop[0-9]* | wc -l > 32 > ``` > > The loop module is loaded from the initfs without the /etc/modules and > /etc/modprobe.d options. In order to load those options, you will need > to add loop to /etc/mkinitfs/mkinitfs.conf, like so: > > `/etc/mkinitfs/mkinitfs.conf/` > ``` > features="... loop" > ``` > > After adding loop to your features list, run `mkinitfs` as root and then > reboot. >
<760263a9-709c-bfa3-4a80-aab3daaf5222@arcor.de>
<fb2be6a1-83e3-01ed-210a-cfc7fb7fd9ca@cosmoborsky.com>
(view parent)
Hello that's it. That's the solution for my problem. THANK YOU Now, after reboot the xen-dom0 have 32 /dev/loop* :-))) /etc/modprobe.d/loop.conf and mkinitfs were the solution. best regards Helmut Pohl Am 06.08.2019 um 16:33 schrieb Cosmo Borsky: > After some testing, the `/etc/mkinitfs/mkinitfs.conf` edit is > unnecessary. `mkinitfs` is all you need after updating > `/etc/modprobe.d/loop.conf` > > I have posted this on the Alpine Linux Xen wiki page: > https://wiki.alpinelinux.org/wiki/Xen_Dom0#Loop_Devices > > On 8/6/19 8:46 AM, Cosmo Borsky wrote: >> On 8/6/19 8:26 AM, Helmut wrote: >>> Hello, >>> >>> thanks for your help. My actual config is: >>> >>> /etc/modules >>> loop max_loop=32 >>> >>> /etc/modprobe.d/loop >>> options loop max_loop=32 >>> >>> /etc/modprobe.d/xen >>> options loop max_loop=32 >>> >>> /boot/extlinux.conf >>> >>> APPEND xen.gz dom0_mem=2048M dom0_max_vcpus=2 dom0_vcpus_pin --- >>> vmlinuz-vanilla root=UUID=dad93766-6001-4458-a5de-d6ac14007b4c >>> modules=sd-mod,usb-storage,ext4,loop,xen-pciback nomodeset quiet >>> rootfstype=ext4 max_loop=32 xen-pciback.hide=(0000:04:01.0) --- >>> initramfs-vanilla >>> >>> NO SUCCESS !! >>> >>> >>> only my manual script has succes: >>> >>> for i in $(seq 8 32) ; do mknod /dev/loop$i b 7 $i ;done >>> chmod 664 /dev/loop* >>> chown 0.disk /dev/loop* >>> >>> >>> But I need a permanently configure in dom0 for start of 10 domU within >>> hd-devices, did you more idea`s ? >>> >>> best regards >>> Helmut >>> >> I see now, when booting only 8 loop modules will be made regardless of >> the max_loop parameter. >> The loops will be made when: >> ``` >> # ls /dev/loop[0-9]* | wc -l >> 8 >> # rmmod loop >> # modprobe loop max_loop=32 >> # ls /dev/loop[0-9]* | wc -l >> 32 >> ``` >> >> The loop module is loaded from the initfs without the /etc/modules and >> /etc/modprobe.d options. In order to load those options, you will need >> to add loop to /etc/mkinitfs/mkinitfs.conf, like so: >> >> `/etc/mkinitfs/mkinitfs.conf/` >> ``` >> features="... loop" >> ``` >> >> After adding loop to your features list, run `mkinitfs` as root and then >> reboot. >>