From: Daniel Herzig <d.herzig@proxmox.com>
To: Aaron Lauterer <a.lauterer@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH manager] proxy: ui: vm console: autodetect novnc or xtermjs
Date: Mon, 25 Nov 2024 10:46:33 +0100 [thread overview]
Message-ID: <87cyijprwm.fsf@proxmox.com> (raw)
In-Reply-To: <20241122143817.352143-1-a.lauterer@proxmox.com> (Aaron Lauterer's message of "Fri, 22 Nov 2024 15:38:17 +0100")
I tested this patch a try with two guests:
+ debian bookworm (added a serial port, left display as default, mods from
cyberciti.biz as below):
+ /etc/default/grub
+ ~GRUB_CMDLINE_LINUX='console=tty0 console=ttyS0,19200n8'~
+ ~GRUB_TERMINAL=serial~
+ ~GRUB_SERIAL_COMMAND="serial --speed=19200 --unit=0 --word=8
--parity=no --stop=1"~
+ /etc/inittab
+ ~T0:23:respawn:/sbin/getty -L ttyS0 19200 vt100~
+ /etc/securetty
+ ~ttyS0~
+ debian bookworm (fresh installation, using ~Serial Terminal 0~ as
graphiccard, using non-graphical installer, startup mods from
infosecworrier.dk as below):
+ replace ~quiet~ with ~console=ttyS0,115200n81~
A rough edge I could think of would be, that if one merely adds a
serial port to the hardware configuration on a OS that does not
autosetup serial consoles, one would lose graphical connectivity.
On the setups above this works like a charm!
Tested-by: Daniel Herzig <d.herzig@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-25 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 14:38 Aaron Lauterer
2024-11-25 9:46 ` Daniel Herzig [this message]
2024-11-25 10:06 ` Aaron Lauterer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyijprwm.fsf@proxmox.com \
--to=d.herzig@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox