I've got a little more info by the way.
If I try to do a vzctl enter immediately after a vzctl start, I get:
Unable to get tty name: Bad file descriptor
smoothwall (root) / $ got signal 9
exited from VE 104
Performing an strace, I find:
[pid 22793] readlink("/proc/self/fd/5", 0x92f9fa0, 4095) = -1 ENOENT (No such file or directory)
[pid 22793] write(2, "Unable to get tty name", 22) = 22
[pid 22793] write(2, ": Bad file descriptor", 21) = 21
[pid 22793] write(2, "\n", 1) = 1
[pid 22793] ioctl(5, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
[pid 22793] readlink("/proc/self/fd/5", 0x92f9fa0, 4095) = -1 ENOENT (No such file or directory)
There were a few devices missing from 104, console, core, fd, full, kmem, mem and port. I've generated these as best I could.
And here's some output after I managed to perform a very quick ls -al on /proc inside the VE:
smoothwall (root) / $ ls -al /proc
total 8
dr-xr-xr-x 2 root root 4096 Jun 8 13:32 ./
drwxr-xr-x 16 root root 4096 Jun 7 17:36 ../
And finally, if I try ps ax:
Error, do this: mount -t proc none /proc
Maybe there's something up with the proc folder?
Nearly got those files ready.
they work out at about 60 Meg each.
Cheers
Simon
OpenVZ Forum
Members
Search
Help
Register
Login
Home
