Hello,
I think it may have something to do with udev. Device files are created
at boot time (you can see a message "waiting for /dev to be fully
populated" when a phisical computer starts) but this is useless in a VE
context.
Check that udev is not being started at boot (does not hurt, but it's
useless) and add /sbin/MAKEDEV tty
/sbin/MAKEDEV pty
in the rc.sysinit file of the VE.
This was explained here: http://forum.openvz.org/index.php?t=msg&goto=34305
Massimiliano
On 10/04/2012 22:26, Corey Carpenter wrote:
Hey All - I am attempting to run a container from a backup...
I am backing up via rsync and trying to run it within a vm. The vm is
the same host, kernel version and just about everything is the same.
Whatever I try, I can't enter the VE; Unable to open pty: No such file
or directory
It is indeed there though, I have tried everything I can find.
Although previously I have ran the same VE from a different days
backup on this setup.
All I want to do is be able to take an rsync of a running container
and throw it into the vm for development purposes.
What should I look into first? I have modified the private location
but I have a feeling it is a permissions issue. The host is Debian 5
and the guest is Ubuntu 10.
Thanks
_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users
