>>>>> Baruch Even <[email protected]> writes:
[...]
> If I try to connect with ssh (using NAT networking) I can connect and
> after loop mounting and setting a root password I can even login but
> I get an error that there is no tty and
Did you mean the message like the following?
$ ssh r...@xxx
stdin: is not a tty
Connection to XXX closed.
$
If so, I could confirm the bug.
> I cannot do much beyond that. I can however connect with ssh to
> execute commands inside the machine such as ls / and things seem to
> work and booted.
Apparently, /dev/pts/ somehow doesn't get created in the domU.
As a workaround, the following seems to work:
dom0 $ ssh -v r...@xxx mkdir /dev/pts \&\& invoke-rc.d mountdevsubfs.sh start
From then on, SSH sessions should become available (until the
next domU shutdown):
dom0 $ ssh r...@xxx
XXX #
[...]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
