[Spice-devel] SPICE for text mode serial consoles ?
A long time back OpenStack had a remote text console service, in parallel with its VNC console console. This was later deleted because it was using insecure code from an unmaintained 3rd party project. Fairly frequently though people raise the issue of re-enabling remote text (ie serial) console access, as a low bandwidth alternative to a fully graphical console. I was wondering, given that SPICE is designed with many independant data channels, would it make sense to provide a way to add new channel type that could transport a text mode console ? eg SPICE would act as the backend for QEMU serial ports, as well as the graphical display. Clients could have a choice of opening the graphics related channels, the serial port channels, or both. NB I'm not saying I've time to work on this at all - I was just wondering if this was conceptually a reasonable feature to propose. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] SPICE for text mode serial consoles ?
Hi Daniel, Would the spiceterm project from Proxmox be of interest? https://git.proxmox.com/?p=spiceterm.git;a=blob_plain;f=spiceterm.pod;hb=master Cheers! iordan On Wed, Jan 15, 2014 at 10:37 AM, Daniel P. Berrange wrote: > A long time back OpenStack had a remote text console service, in parallel > with its VNC console console. This was later deleted because it was using > insecure code from an unmaintained 3rd party project. Fairly frequently > though people raise the issue of re-enabling remote text (ie serial) > console access, as a low bandwidth alternative to a fully graphical > console. > > I was wondering, given that SPICE is designed with many independant > data channels, would it make sense to provide a way to add new channel > type that could transport a text mode console ? eg SPICE would act as > the backend for QEMU serial ports, as well as the graphical display. > Clients could have a choice of opening the graphics related channels, > the serial port channels, or both. > > NB I'm not saying I've time to work on this at all - I was just wondering > if this was conceptually a reasonable feature to propose. > > Regards, > Daniel > -- > |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/:| > |: http://libvirt.org -o- http://virt-manager.org:| > |: http://autobuild.org -o- http://search.cpan.org/~danberr/:| > |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc:| > ___ > Spice-devel mailing list > Spice-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/spice-devel > -- The conscious mind has only one thread of execution. ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] SPICE for text mode serial consoles ?
On Wed, Jan 15, 2014 at 11:01:16AM -0500, i iordanov wrote: > Hi Daniel, > > Would the spiceterm project from Proxmox be of interest? > > https://git.proxmox.com/?p=spiceterm.git;a=blob_plain;f=spiceterm.pod;hb=master That is running a shell server side and then rendering it into a graphical display which is then transported over SPICE as a bitmap. That is a rather inefficient way of sending a plain text data stream, and the client can't turn this bitmap back into plain text for display on a local text terminal. For this to be of value we want to be transporting plain text end-to-end in both directions. > On Wed, Jan 15, 2014 at 10:37 AM, Daniel P. Berrange > wrote: > > > A long time back OpenStack had a remote text console service, in parallel > > with its VNC console console. This was later deleted because it was using > > insecure code from an unmaintained 3rd party project. Fairly frequently > > though people raise the issue of re-enabling remote text (ie serial) > > console access, as a low bandwidth alternative to a fully graphical > > console. > > > > I was wondering, given that SPICE is designed with many independant > > data channels, would it make sense to provide a way to add new channel > > type that could transport a text mode console ? eg SPICE would act as > > the backend for QEMU serial ports, as well as the graphical display. > > Clients could have a choice of opening the graphics related channels, > > the serial port channels, or both. > > > > NB I'm not saying I've time to work on this at all - I was just wondering > > if this was conceptually a reasonable feature to propose. Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] SPICE for text mode serial consoles ?
Hi Daniel, On Wed, Jan 15, 2014 at 11:08 AM, Daniel P. Berrange wrote: > For this to be of value we want > to be transporting plain text end-to-end in both directions. > This makes sense. Cheers, iordan ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] SPICE for text mode serial consoles ?
- Original Message - > A long time back OpenStack had a remote text console service, in parallel > with its VNC console console. This was later deleted because it was using > insecure code from an unmaintained 3rd party project. Fairly frequently > though people raise the issue of re-enabling remote text (ie serial) > console access, as a low bandwidth alternative to a fully graphical > console. > > I was wondering, given that SPICE is designed with many independant > data channels, would it make sense to provide a way to add new channel > type that could transport a text mode console ? eg SPICE would act as > the backend for QEMU serial ports, as well as the graphical display. > Clients could have a choice of opening the graphics related channels, > the serial port channels, or both. It's kind of possible today -chardev spiceport,name=org.spice.spicy,id=charchannel1 -serial chardev:charchannel1 booting kernel with console=tty0 console=ttyS0,115200n8 and connecting with spicy will give you kernel log in client console.. There is even a standard port name for it: org.qemu.console.serial.0 But integration with client is left to do, also I don't know what's the right way to setup the VM to make this work nicely with login etc.. ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] SPICE for text mode serial consoles ?
On Wed, Jan 15, 2014 at 11:18:42AM -0500, Marc-André Lureau wrote: > > > - Original Message - > > A long time back OpenStack had a remote text console service, in parallel > > with its VNC console console. This was later deleted because it was using > > insecure code from an unmaintained 3rd party project. Fairly frequently > > though people raise the issue of re-enabling remote text (ie serial) > > console access, as a low bandwidth alternative to a fully graphical > > console. > > > > I was wondering, given that SPICE is designed with many independant > > data channels, would it make sense to provide a way to add new channel > > type that could transport a text mode console ? eg SPICE would act as > > the backend for QEMU serial ports, as well as the graphical display. > > Clients could have a choice of opening the graphics related channels, > > the serial port channels, or both. > > It's kind of possible today > > -chardev spiceport,name=org.spice.spicy,id=charchannel1 -serial > chardev:charchannel1 > > booting kernel with console=tty0 console=ttyS0,115200n8 and connecting with > spicy will give you kernel log in client console.. > > There is even a standard port name for it: org.qemu.console.serial.0 Cool, I love it when my ideas have already been mostly implemented :-) > But integration with client is left to do, also I don't know what's > the right way to setup the VM to make this work nicely with login etc.. If you boot with "console=ttyS0" then systemd would automatically start a login prompt on the serial port. I think you can probably even make it do both graphical & text logins using 'console=ttyS0 console=tty' Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
