public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] virtualbox in headless configuration broken after update: delayed echo [ RESOLVED, kinda ]
Date: Tue, 16 Jun 2020 23:08:23 +0200	[thread overview]
Message-ID: <bc7d5e91-e704-b2f5-abb1-d06e6b67375c@web.de> (raw)
In-Reply-To: <FC9FE60B-DDB7-4A7C-9255-F587D9E5DAD4@antarean.org>

On 06/16/20 22:36, J. Roeleveld wrote:
> On 16 June 2020 21:07:56 CEST, n952162 <n952162@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"?



  reply	other threads:[~2020-06-16 21:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 13:19 [gentoo-user] virtualbox in headless configuration broken after update: delayed echo n952162
2020-06-16 19:07 ` [gentoo-user] virtualbox in headless configuration broken after update: delayed echo [ RESOLVED, kinda ] n952162
2020-06-16 20:36   ` J. Roeleveld
2020-06-16 21:08     ` n952162 [this message]
2020-06-17  4:48       ` J. Roeleveld
2020-06-17  5:42         ` n952162
2020-06-17  6:32           ` J. Roeleveld
2020-06-17 17:01             ` Michael
2020-06-17 17:31               ` J. Roeleveld
2020-06-17 19:32                 ` Michael
2020-06-17 19:55                   ` J. Roeleveld
2020-06-17 23:05                     ` Michael
2020-06-17 23:09                     ` William Kenworthy
2020-06-18  9:21                       ` Michael

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=bc7d5e91-e704-b2f5-abb1-d06e6b67375c@web.de \
    --to=n952162@web.de \
    --cc=gentoo-user@lists.gentoo.org \
    /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