devnodes don't create zaptel devices (kernel 2.6.24)
Hi, me again. I am trying to use zaptel modules in my VE. I added DEVNODES="zap/ctl:rw zap/channel:rw zap/pseudo:rw zap/timer:rw " in my VE Config. Under Kernel 2.6.18 it works and /dev/zap/... gets created. Now in 2.6.24 there is no /dev/zap and already manual added mknod devices are got deleted. Is there a problem with the devnodes? Also the command "vzctl set VEID --devnodes" removes every time the line DEVNODES. So there is always only 1 DEVNODES defined. thx
Re: devnodes don't create zaptel devices (kernel 2.6.24)
This must be http://bugzilla.openvz.org/show_bug.cgi?id=840 which means something is seriously screwed in VE.
Doesn't help, still after each restart of my VE the mknode-created-Devices are gone and after the last command of "vzctl set VEID --devnodes ...." it shows in the config only one devnode, the last one I added.
They dissappear because you have /dev on tmpfs inside VE.
But shouldn't they be created if they are defined in the VE-Configfile? Here my line: DEVNODES="zap/timer:rw zap/channel:rw zap/ctl:rw zap/timer:rw" But I don't have them after a VE-boot in my /dev/ If I make them with vzctl Device gets created and after a restart they are gone.
We create device in VE's /dev directory before VE start. However when udev stated inside VE it mounts tmpfs into /dev mountpoint and makes our device file invisible by following processes. As work-around you can change udev configuration to create required files persistent after each VE reboot. Unfortunately various Linux distributions stores udev configuration in different files. Therefore please create bug in our Bugzilla, we'll think how to resolve this issue in generic way. Thank you, Vasily Averin