[Users] DEVNODES-statement does not create devices in directories anymore but in the root at VE /dev

[Kir Kolyshkin]

On 10/04/2013 01:38 PM, Johan Wilfer wrote:
> 2013-10-04 20:52, Kir Kolyshkin skrev:
>> On 10/04/2013 01:50 AM, Johan Wilfer wrote:
>>> Hi,
>>>
>>> I am evaluating how to migrate my Debian 6 HN's now when support soon
>>> will be dropped for Debian 6 and they also drop official support for
>>> Openvz.
>>>
>>> Right now I testing a Debian 7, with a RHEL-kernel:
>>> 2.6.32-openvz-042stab081.3-amd64 with vzctl version 4.5.1
>>>
>>> They are converted from rpm with alien and installed with dpkg. As
>>> instructed here on page 1:
>>> http://www.howtoforge.com/installing-and-using-openvz-on-debian-wheezy-amd64 
>>>
>>>
>>
>> There is a better way now! We have native Debian Wheezy builds
>> for kernel and tools, available at http://download.openvz.org/debian
>> (please see that page for more info). That stuff is still in beta, so
>> if you can test it and report possible bugs back to us that would
>> be just great.
>
> Ah, ok! I did try that first, but the vzkernel package in the 
> repository was actually an old release. So that's maybe a bug?
>
> Here: 
> http://download.openvz.org/debian/dists/wheezy/main/binary-amd64/Packages
>
> Package: vzkernel
> Filename: 
> dists/wheezy/main/binary-amd64/alien/vzkernel_2.6.32-042stab059.7_amd64.deb

This one is very old and shouldn't be used.

>
> After that I tried to install the package "linux-image-openvz-amd64" 
> as a replacement, but I got a package-error (this is from my memory so 
> I hope I'm not confusing it with another package now):
>
> From the same page:
> Package: linux-image-openvz-amd64
> Version: 042stab081.3
> Depends: linux-image-openvz-042stab081.3-amd64
>
> But there isn't any package by that name.

This is the bug I fixed just yesterday, so it should work now. Sorry for 
the problem.

>
> I did then install "linux-image-2.6.32-openvz-042stab081.3-amd64" and 
> it worked.
>
>
> After that I tried with alien instead, but it was very manual.
> Right now I'm evaluating using Centos 6 as a HN.

This would be a good alternative, I suppose.
Nevertheless we still want to maintain good stuff for Debian,
the problems that you faced are caused by the fact that all
this is very new, so there may still be some stupid bugs like
the one above.

>
>>
>>>
>>> I've noticed that when I create a VE with DEVNODES-statement, like 
>>> this:
>>> DEVNODES="dahdi/channel:rw dahdi/ctl:rw dahdi/pseudo:rw dahdi/timer:rw"
>>>
>>> It seems to be the same with other devices, like /dev/net/* or
>>> /dev/usb/* etc.
>>>
>>> Any thoughts?
>>
>> Most probably it has to do something with what distro you have inside a
>> container
>> rather than the kernel and vzctl.
>>
>> I tried to reproduce your issue using vzctl-4.5.1 and kernel
>> 2.6.32-042stab082.3,
>> with a container running centos-6-x86 template, and it works as it 
>> should
>> (well, almost -- see below):> I am not sure why that happens, but it 
>> doesn't look like a big issue to me.
>>
>> I re-did the same test with the debian-7-x86_64 template, with the
>> same results.
>>
>> Generally, such requests better to be filed as bugs to bugzilla (but for
>> this one,
>> so far, WORKSFORME).
>
> Okay, just wanted to confirm and to get feedback. Thanks for providing 
> that!
>
> The strange thing is it doesn't happen on my Debian 6 HN with Debian 6 
> VE's. I did try this with Debian 7 HN (alien kernel) and both Debian 6 
> template and Debian 7 template.
>
> The Debian 6 template is the same that works with Debian 6 HN.
>
> I'll try this again with Centos 6 HN (same kernel as above and same 
> vzctl) in the next week.

I can re-do the tests on a Debian 7 node, but I doubt it is in any way 
different.

>
> I can also try reinstall a fresh Debian 7 + vzkernel from 
> download.openvz.org/debian and re-try it. Maybe I broke something 
> trying these different kernels and versions. If it's possible to fix 
> the repro so vzkernel points to the latest release I could retry after 
> that?

Should already be fixed.

>
> Thanks!
>