[arch-general] Can't SSH into Arch VM until login screen is viewed
I have a weird issue I’m trying to figure out with Arch and SystemD, and I wonder if anyone here has run into this issue: I’m running ArchLinux as a Xen VM. Every time I reboot the system, I can no longer ping it or access it via SSH. However, if I go into the XenCenter UI and click the “Console” tab to view the VM’s login screen, all of a sudden SSH and ping works again. It’s as if systemd is waiting for the login screen to be viewed before it allows SSH to work. Is this some kind of systemd socket-activated functionality related to the getty service? How can I prevent this so that I can log in via SSH after reboot without having to run the XenCenter UI? Thanks, Ben Booth
On 07.07.14 at 9:59, Ben Booth wrote:
I have a weird issue I’m trying to figure out with Arch and SystemD, and I wonder if anyone here has run into this issue:
I’m running ArchLinux as a Xen VM. Every time I reboot the system, I can no longer ping it or access it via SSH. However, if I go into the XenCenter UI and click the “Console” tab to view the VM’s login screen, all of a sudden SSH and ping works again. It’s as if systemd is waiting for the login screen to be viewed before it allows SSH to work. Is this some kind of systemd socket-activated functionality related to the getty service? How can I prevent this so that I can log in via SSH after reboot without having to run the XenCenter UI?
Thanks, Ben Booth
If even the ping does not work, it sounds more like an issue with firewall to me. I have no idea if xen modifies the firewall, check its state before and after running xen and compare the differences. -- jlk
On 07-07-14 18:59, Ben Booth wrote:
I have a weird issue I’m trying to figure out with Arch and SystemD, and I wonder if anyone here has run into this issue:
I’m running ArchLinux as a Xen VM. Every time I reboot the system, I can no longer ping it or access it via SSH. However, if I go into the XenCenter UI and click the “Console” tab to view the VM’s login screen, all of a sudden SSH and ping works again. It’s as if systemd is waiting for the login screen to be viewed before it allows SSH to work. Is this some kind of systemd socket-activated functionality related to the getty service? How can I prevent this so that I can log in via SSH after reboot without having to run the XenCenter UI?
Thanks, Ben Booth
Ben, Try adding console=ttyS0 as kernel parameter to the boot command. see http://0pointer.de/blog/projects/serial-console.html for details LW
On Jul 7, 2014, at 12:27 PM, LoneVVolf <lonewolf@xs4all.nl> wrote:
Try adding console=ttyS0 as kernel parameter to the boot command.
see http://0pointer.de/blog/projects/serial-console.html for details
Thanks for the link! I did the following and that fixed the problem for me: # systemctl enable serial-getty@ttyS0.service # systemctl start serial-getty@ttyS0.service Ben
LW
participants (3)
-
Ben Booth
-
Jakub Klinkovský
-
LoneVVolf