So, originally I assumed this meant that ssh wasn't running right after "apt-get install openssh-server". But you are saying that it does not work after the first *boot*? Otherwise having these VMs and booting them would not be useful for debugging anything.
So the expectation is that booting max-ssh-recreate-base-clone.qcow2 will not start the ssh server, but a reboot will? What's the output of "sudo systemctl status ssh" after the first boot? Can you please also capture "sudo journalctl -b" and attach the output? Thanks! (BTW, I used the guest session in my previous comment, and tried to get some data as user, but at least under unity this is utterly impossible) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1554266 Title: sshd does not start on newly installed desktop system Status in openssh package in Ubuntu: Incomplete Bug description: When I preseed a desktop install using utah for daily iso testing, the ssh service is not running when it starts up. journalctl -u ssh shows no entries. If I manually start the ssh service, it seems to work. If I reboot, sshd is running. On the first boot, however, it is not. This problem appears to have started on the March 5 image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp