Difference between revisions of "Container enter failed"
Sandro magri (talk | contribs) (alternative solution for the problem) |
Sandro magri (talk | contribs) |
||
| Line 23: | Line 23: | ||
</pre> | </pre> | ||
| − | Another solution: | + | '''Another solution''': |
enter the VE manually creating the LEGACY_PTYS devices | enter the VE manually creating the LEGACY_PTYS devices | ||
| Line 33: | Line 33: | ||
</pre> | </pre> | ||
| − | To save the changes | + | To save the changes force udev to make LEGACY_PTYS: |
<pre> | <pre> | ||
Revision as of 17:52, 26 March 2008
Problem: container created succesfully and started. But when trying to do
vzctl enter 101
you get
container enter failed(?)
Using strace, you see:
# strace -ff vzctl enter .... fstat64(...st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0)...) fail ....
Solution: Recompile the kernel with the following option:
CONFIG_LEGACY_PTYS=y
Another solution:
enter the VE manually creating the LEGACY_PTYS devices
vzctl exec 101 /sbin/MAKEDEV tty vzctl exec 101 /sbin/MAKEDEV pty vzctl enter 101
To save the changes force udev to make LEGACY_PTYS:
cat > /etc/udev/makedev.d/51-udev.nodes # These device have to be created manually tty0 tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 ttyp0 ttyp1 ttyp2 ttyp3 ttyp4 ttyp5 ttyp6 ptyp0 ptyp1 ptyp2 ptyp3 ptyp4 ptyp5
