On Fri, Mar 31, 2017 at 12:59:56PM +0000, ng0 wrote:
> before I go ahead and create an intermediate image  -  I'd like to explore
> the option of getting IN-Berlin closer into the creation of the 'deploy'
> process of Guix which is being worked on  -  I need to find out how the
> redirection to	"/sbin/agetty --keep-baud 115200 38400 9600 ttyS0 vt102"
> can be honored.
> As far as I understand, we use mingetty which according to the mingetty
> manpages is not suited for tasks agetty can do.
> 
> IN-Berlin runs a Consoleserver which redirects ssh logins to it via
> "virsh console $vserver" to the /sbin/agetty (on debian vservers) on
> your server. The KVM configuration can be seen below.
> 
> How can I achieve this (the agetty part) with GuixSD?

You can use the agetty-service, like this

(kernel-arguments
  ;; Adjust these arguments as desired.
  '("console=ttyS0,115200n8 gfxpayload=text earlyprintk=serial,tty,115200"))

(services
  (cons (agetty-service (agetty-configuration
                          (tty "ttys0")
                          (term "vt102")
                          (keep-baud? #t)
                          (baud-rate "115200,38400,9600)))
        %base-services))			    

And you will probably want a non-graphical GRUB menu as well (this
should be parameterized eventually...):

diff --git a/gnu/system/grub.scm b/gnu/system/grub.scm
index b18b8be6d..d94b1a266 100644
--- a/gnu/system/grub.scm
+++ b/gnu/system/grub.scm
@@ -197,7 +197,7 @@ system string---e.g., \"x86_64-linux\"."
     insmod efi_uga
   fi
 
-  terminal_output gfxterm
+  terminal_output console
 "
         ""))
 
Finally, you can test it in QEMU by appending '-serial pty' to the
QEMU invocation. When it starts, QEMU will tell you which pty it's
using, and you can connect to it with something like `screen`.