sysfs question

sysfs question

[Mark Ryden]

Hello,
I am trying to follow the
Linux Containers - Network Namespace configuration instructions from
http://lxc.sourceforge.net/network/configuration.php


I had built a kernel with CONFIG_SYS=n and  CONFIG_NET_NS=y
and CONFIG_VETH=y , etc, according to the instructions.


Now, the CONFIG_SYSFS help text says:

sysfs is currently used by the block subsystem to mount the root
partition. If sysfs is disabled you must specify the boot device on
the kernel boot command line via its major and minor numbers. For
example, "root=03:01" for /dev/hda1.


So I added root=08,02 to my kernel boot parameter line and booted.


it starts booting, but then gets:
switchroot: mount failed: No such file or directory.
Booting has failed.

8 is the majoror number and 2 is the minor number of /dev/sda2, where I have
my root partition.

Googling for this found the following, which not helped much:
http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-11/msg05032.html

Any ideas?
Regards,
Mark

Re: sysfs question

[Mark Ryden]

In fact, after looking more closely, I see that before that message appears:
Error: unmouting old /sys
ERROR unmounting old /sys: Invalid argument.
forcing unmount of /sys
switchroot...

Any ideas?
Rgs,
Mark


On Thu, Sep 11, 2008 at 5:01 PM, Mark Ryden <markryde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hello,
> I am trying to follow the
> Linux Containers - Network Namespace configuration instructions from
> http://lxc.sourceforge.net/network/configuration.php
>
>
> I had built a kernel with CONFIG_SYS=n and  CONFIG_NET_NS=y
> and CONFIG_VETH=y , etc, according to the instructions.
>
>
> Now, the CONFIG_SYSFS help text says:
>
> sysfs is currently used by the block subsystem to mount the root
> partition. If sysfs is disabled you must specify the boot device on
> the kernel boot command line via its major and minor numbers. For
> example, "root=03:01" for /dev/hda1.
>
>
> So I added root=08,02 to my kernel boot parameter line and booted.
>
>
> it starts booting, but then gets:
> switchroot: mount failed: No such file or directory.
> Booting has failed.
>
> 8 is the majoror number and 2 is the minor number of /dev/sda2, where I have
> my root partition.
>
> Googling for this found the following, which not helped much:
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-11/msg05032.html
>
> Any ideas?
> Regards,
> Mark
>

Re: sysfs question

[xiaoming.zhang]

On Thursday 11 September 2008 10:05:43 pm Mark Ryden wrote:
> In fact, after looking more closely, I see that before that message
> appears: Error: unmouting old /sys
> ERROR unmounting old /sys: Invalid argument.
> forcing unmount of /sys
> switchroot...
>

My experience is you'd better to find a sysfs patch, since the sysfs 
filesystem is required by ramdisk and some system utilities, e.g., system 
network configuration scripts.

Patch for mm-tree can be found here:
	http://lxc.sourceforge.net/patches/2.6.26/

This is what I used:
http://lxc.sourceforge.net/patches/2.6.26/2.6.26-rc8-mm1-lxc1/broken-out/sysfs/

I merged these 11 patches on Linux-2.6.26.1 though I don't understand these 
patches, luckily enough it worked for me.

> Any ideas?
> Rgs,
> Mark
>
> On Thu, Sep 11, 2008 at 5:01 PM, Mark Ryden <markryde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Hello,
> > I am trying to follow the
> > Linux Containers - Network Namespace configuration instructions from
> > http://lxc.sourceforge.net/network/configuration.php
> >
> >
> > I had built a kernel with CONFIG_SYS=n and  CONFIG_NET_NS=y
> > and CONFIG_VETH=y , etc, according to the instructions.
> >
> >
> > Now, the CONFIG_SYSFS help text says:
> >
> > sysfs is currently used by the block subsystem to mount the root
> > partition. If sysfs is disabled you must specify the boot device on
> > the kernel boot command line via its major and minor numbers. For
> > example, "root=03:01" for /dev/hda1.
> >
> >
> > So I added root=08,02 to my kernel boot parameter line and booted.
> >
> >
> > it starts booting, but then gets:
> > switchroot: mount failed: No such file or directory.
> > Booting has failed.
> >
> > 8 is the majoror number and 2 is the minor number of /dev/sda2, where I
> > have my root partition.
> >
> > Googling for this found the following, which not helped much:
> > http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-11/msg05032.html
> >
> > Any ideas?
> > Regards,
> > Mark
>
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers



-- 
Have fun,
Xiaoming Zhang

Re: sysfs question

[Daniel Lezcano]

xiaoming.zhang wrote:
> On Thursday 11 September 2008 10:05:43 pm Mark Ryden wrote:
>> In fact, after looking more closely, I see that before that message
>> appears: Error: unmouting old /sys
>> ERROR unmounting old /sys: Invalid argument.
>> forcing unmount of /sys
>> switchroot...
>>
> 
> My experience is you'd better to find a sysfs patch, since the sysfs 
> filesystem is required by ramdisk and some system utilities, e.g., system 
> network configuration scripts.
> 
> Patch for mm-tree can be found here:
> 	http://lxc.sourceforge.net/patches/2.6.26/
> 
> This is what I used:
> http://lxc.sourceforge.net/patches/2.6.26/2.6.26-rc8-mm1-lxc1/broken-out/sysfs/
> 
> I merged these 11 patches on Linux-2.6.26.1 though I don't understand these 
> patches, luckily enough it worked for me.

As mentioned Benjamin, it is hard to boot a distro without sysfs. I 
think it is a good idea to use the lxc patchset.

You can use the latest version:

http://lxc.sourceforge.net/patches/2.6.27/2.6.27-rc6-lxc1/

If you want to play with the container, you have the userspace tools at:

http://lxc.sourceforge.net/download/lxc/

Don't forget to check the README in the directory ;)

   -- Daniel

Re: sysfs question

[xiaoming.zhang]

On Thursday 11 September 2008 11:37:33 pm Daniel Lezcano wrote:
> xiaoming.zhang wrote:
> > On Thursday 11 September 2008 10:05:43 pm Mark Ryden wrote:
> >> In fact, after looking more closely, I see that before that message
> >> appears: Error: unmouting old /sys
> >> ERROR unmounting old /sys: Invalid argument.
> >> forcing unmount of /sys
> >> switchroot...
> >
> > My experience is you'd better to find a sysfs patch, since the sysfs
> > filesystem is required by ramdisk and some system utilities, e.g., system
> > network configuration scripts.
> >
> > Patch for mm-tree can be found here:
> > 	http://lxc.sourceforge.net/patches/2.6.26/
> >
> > This is what I used:
> > http://lxc.sourceforge.net/patches/2.6.26/2.6.26-rc8-mm1-lxc1/broken-out/
> >sysfs/
> >
> > I merged these 11 patches on Linux-2.6.26.1 though I don't understand
> > these patches, luckily enough it worked for me.
>
> As mentioned Benjamin, it is hard to boot a distro without sysfs. I
> think it is a good idea to use the lxc patchset.
>
> You can use the latest version:
>
> http://lxc.sourceforge.net/patches/2.6.27/2.6.27-rc6-lxc1/
>
Thank you very much. And is there any patchset for Linux-2.6.26.* (not the 
mm-tree)?


> If you want to play with the container, you have the userspace tools at:
>
> http://lxc.sourceforge.net/download/lxc/
>
> Don't forget to check the README in the directory ;)
>
>    -- Daniel



-- 
Have fun,
Xiaoming Zhang

Re: sysfs question

[Daniel Lezcano]

xiaoming.zhang wrote:
> On Thursday 11 September 2008 11:37:33 pm Daniel Lezcano wrote:
>> xiaoming.zhang wrote:
>>> On Thursday 11 September 2008 10:05:43 pm Mark Ryden wrote:
>>>> In fact, after looking more closely, I see that before that message
>>>> appears: Error: unmouting old /sys
>>>> ERROR unmounting old /sys: Invalid argument.
>>>> forcing unmount of /sys
>>>> switchroot...
>>> My experience is you'd better to find a sysfs patch, since the sysfs
>>> filesystem is required by ramdisk and some system utilities, e.g., system
>>> network configuration scripts.
>>>
>>> Patch for mm-tree can be found here:
>>> 	http://lxc.sourceforge.net/patches/2.6.26/
>>>
>>> This is what I used:
>>> http://lxc.sourceforge.net/patches/2.6.26/2.6.26-rc8-mm1-lxc1/broken-out/
>>> sysfs/
>>>
>>> I merged these 11 patches on Linux-2.6.26.1 though I don't understand
>>> these patches, luckily enough it worked for me.
>> As mentioned Benjamin, it is hard to boot a distro without sysfs. I
>> think it is a good idea to use the lxc patchset.
>>
>> You can use the latest version:
>>
>> http://lxc.sourceforge.net/patches/2.6.27/2.6.27-rc6-lxc1/
>>
> Thank you very much. And is there any patchset for Linux-2.6.26.* (not the 
> mm-tree)?

We worked most of the time sticked with the devel version of the kernel 
tree. The kernel which is the nearest of the version you are describing 
is 2.6.27-rc6-lxc1 which is not based on the -mm but on the 2.6.27 
release candidate. IMO, this is the most stable version of the LXC.

Re: sysfs question

[Benjamin Thery]

Hi Mark,

Indeed booting a distro without sysfs can be tricky because, for
example, initrd might need it (eg. Fedora).

IIRC, to boot without sysfs, in addition to the "root=" option,  you
have to create some devices nodes in advance in your /dev tree
(mainly the /dev/sda* ones, plus a bunch of others /dev/urandom,
/dev/null, /dev/console, /dev/tty).

mknod /dev/sda b 8 0
mknod /dev/sda1 b 8 1
...

But my advice to test netns is to apply the tagged directories sysfs
patchses. It is a lot easier (and complete).

Gregkh is merging the patchset to his tree today (he has added 6 out of
the 8 remaining patches this morning) :)
Once the patchset is completely merged I'll update the howto.

Also I can send you tarball too if you want. Which kernel version do you 
use?

Regards,
Benjamin


Mark Ryden wrote:
> Hello,
> I am trying to follow the
> Linux Containers - Network Namespace configuration instructions from
> http://lxc.sourceforge.net/network/configuration.php
> 
> 
> I had built a kernel with CONFIG_SYS=n and  CONFIG_NET_NS=y
> and CONFIG_VETH=y , etc, according to the instructions.
> 
> 
> Now, the CONFIG_SYSFS help text says:
> 
> sysfs is currently used by the block subsystem to mount the root
> partition. If sysfs is disabled you must specify the boot device on
> the kernel boot command line via its major and minor numbers. For
> example, "root=03:01" for /dev/hda1.
> 
> 
> So I added root=08,02 to my kernel boot parameter line and booted.
> 
> 
> it starts booting, but then gets:
> switchroot: mount failed: No such file or directory.
> Booting has failed.
> 
> 8 is the majoror number and 2 is the minor number of /dev/sda2, where I have
> my root partition.
> 
> Googling for this found the following, which not helped much:
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-11/msg05032.html
> 
> Any ideas?
> Regards,
> Mark
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
> 
> 


-- 
B e n j a m i n   T h e r y  - BULL/DT/Open Software R&D

    http://www.bull.com