[PVE-User] Serial console

[Guy]

Rather than using a :socket... I use this

-serial tcp:0.0.0.0:<VMID>,server,nowait

This allows me to telnet direct to the proxmox head on this port <VMID> and connect to the serial of my linux systems. That way I don't need to let the world and his dog have access to the proxmox shell.

I use ID of the VM as the port as it's nice and easy to be sure the port is unique, if you use low numbers then you might want to multiply by 1000 just to get it out of the os space range.

--Guy



On 1 Apr 2014, at 08:29, Philippe Andersson <pan at iba-group.com> wrote:

> Hello Dietmar,
> 
> On 01/04/14 06:14, Dietmar Maurer wrote:
>>> 1./ is there a different way to define this virtual hardware that would offer
>>> the same functionalities while maintaining the ability to live migrate ?
>>> 
>>> 2./ is there a plan at some point in the Proxmox roadmap to lift this limitation
>>> and make this "socket" compatible with live migration ?
>> 
>> This open a local socket. Such device will never be able to migrate correctly.
> OK, understood.
> 
>> I guess you just use it as serial console?
>> 
> Yes. For remote admin, serial console has our preference over the more
> conventional Spice or VNC because it's lighter, requires nothing more
> than an SSH client, and bypasses all the keyboard mapping issues you get
> with the regular consoles.
> 
> But if it doesn't migrate, it's no use in a cluster, which is a real pity.
> 
> Any chance for a different implementation? VMware redirects to a network
> socket, and this still allows for vMotion (i.e. live migration).
> 
> TIA
> 
> Cheers. Bye.
> 
> Ph. A.
> 
> -- 
> 
> *Philippe Andersson*
> Unix System Administrator
> IBA Particle Therapy |
> Tel: +32-10-475.983
> Fax: +32-10-487.707
> eMail: pan at iba-group.com
> <http://www.iba-worldwide.com>
> 
> 
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user