On 06/16/20 22:36, J. Roeleveld wrote:
On 16 June 2020 21:07:56 CEST, n952162 <n952...@web.de> wrote:
On 06/10/20 15:19, n952162 wrote:
I updated my system and now characters typed into vbox over ssh are
not echo-ed until *after* a CR is entered.
I diffed the stty output, to see if I could spot anything:
10~>cat /tmp/sttydiff
2,3c2,3
< rows 37
< columns 100
---
rows 44
columns 88
21d20
< discard = ^O
23c22,23
< min = 1
---
discard = ^O
min = 1
30c30
< hupcl
---
-hupcl
36c36
< brkint
---
-brkint
48,49c48,49
< imaxbel
< iutf8
---
-imaxbel
-iutf8
Also, the font seems to be screwed up, because the last line of the
window only shows the top half of the line.
Anybody else encounter this or know what's wrong?
Vbox seems to work okay when run locally, on the machine it's
installed on.
I think this is resolved, kinda.
I just discovered that if I turn off the vbox menu bar, the command
entry line works properly again, both in X-less console mode and in X.
Settings -> User Interface -> Enable menu bar (disable this)
I've always had that menu bar, and need it, so something got
changed/broken, and I still have a problem, but at least now I don't
have to enter commands in blindly.
Are these Virtualbox VMs critical?
If yes, I would suggest migrating them to a more reliable virtualisation
technology.
I do not consider Virtualbox suitable for anything but a desktop based VM
method for a quick test or simulation.
Gor anything serious, I would suggest Xen, KVM or VMWare.
--
Joost
Well, no, they're really not critical, but your comment surprises me.
I've been using vbox for years, on various assignments, and never
encountered anything else. Can you say a word or two to that, or
provide a URL? Which free vm is "the best"?
