[SOLVED] VirtualBox Guest: Spawning echoes/returns following some commands
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
VirtualBox Guest: Spawning echoes/returns following some commands
Not sure if I can describe this It seems to only be happening when I drop down to init 3 from init 4
If I do a slackpkg update the command finishes successfully, but I see the command prompt repeated a number of times. Sometimes it's just 3 or 4 other times it may be tens of times so much that the output from slackpkg disappears of the screen
It gets a bit frustrating when running slackpkg upgrade-all when there's been a change to the kernel and new config files. All those nice messages about a new kernel and new config files disappear of the top of the screen.
Generally I know that there's a new kernel.
For the new config files I have to run
slackpkg new-config
several times
Any thoughts as to what's going wrong?
Last edited by aikempshall; 03-17-2021 at 09:52 AM.
Reason: add virtualbox to title
No problem with the keyboard. I see the same problem irrespective of what [Enter] key I use. The Enter key on the number pad or the Return key on the QWERTY keyboard.
I not aware of any problems I may have created for myself in respect of PS1 or environment.
The problem only occurs at levels 3, 2 and 1. Level 4 works as expected.
Level 4 works as expected, is not quite true, as if I set up a virtual console the problem appears.
It appears that if I'm working in an environment that's been touched by KDE4 i.e. level 4, virtual terminal excluded, everything works as expected. It's only if I drop out of a KDE environment to levels 3, 2 and 1 or to a virtual terminal that I get problems.
The only other potential cause is that these problems are occurring in a VirtualBox guest. I have no other issues with the guest - in level 4 LibreOffice, kate, filezilla, Firefox, Dolphin. adobereader. okular and keepassxc all work as expected.
As the problem only occurs levels 3 or below and I only need to drop to level 3 if I'm updating KDE, so when we reach a Stable 15.0 the need to drop levels will become less and less. Anyway it's not as though this problem is a show stopper. I'm flagging it up in case someone else either falls upon this problem or can shed some light on the root cause.
The only place I see this behavior is in my VirtualBox slackware installs when I was testing with VboxVGA or VboxSVGA set for the Graphics Controller. Switching back to VMSVGA, this problem goes away. This is without Guest Additions installed. Not sure if installing Guest Additions would make a difference.
Last edited by chrisretusn; 03-11-2021 at 05:46 AM.
The only place I see this behavior is in my VirtualBox slackware installs when I was testing with VboxVGA or VboxSVGA set for the Graphics Controller. Switching back to VMSVGA, this problem goes away. This is without Guest Additions installed. Not sure if installing Guest Additions would make a difference.
It was VirtualBox that was causing the problem. I'm was on VirtualBox 5.0.40 from slackbuilds.org.
Took the plunge and installed the Linux 64-bit from the VirtualBox Testbuilds
Had the same echo/return problem using the VBoxVGA graphics Controller. The machine would start, but the screen would resize (auto-resize guest display was enabled)
Didn't have the problem with the VMSVGA graphics Controller. The machine would start, but the screen wouldn't resize (auto-resize guest display was greyed out)
Installed Guest Additions which fixed the problem with VMSVGA. I can now resize.
The unintended consequence is that when using the VBoxVGA graphics Controller the guest won't start.
It was VirtualBox that was causing the problem. I'm was on VirtualBox 5.0.40 from slackbuilds.org.
Took the plunge and installed the Linux 64-bit from the VirtualBox Testbuilds
Had the same echo/return problem using the VBoxVGA graphics Controller. The machine would start, but the screen would resize (auto-resize guest display was enabled)
Didn't have the problem with the VMSVGA graphics Controller. The machine would start, but the screen wouldn't resize (auto-resize guest display was greyed out)
Installed Guest Additions which fixed the problem with VMSVGA. I can now resize.
The unintended consequence is that when using the VBoxVGA graphics Controller the guest won't start.
I'll mark this as solved.
Probably why it says "invalid settings". Got to admit I was a bit excited when you first reported on using VboxVGA. I really don't like installing the Guest Additions. Tried it and VboxSVGA too, had same issue. Went back to VMSVGA.
I have a Current VM running in 6.1.18. Guest Additions (GA) are not installed. When I select VBoxSVGA I see the reported repeated echos. When I toggle to VMSVGA the echos stop, but then the system always boots with the following error message:
Code:
kernel: [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message.
I have not tested installing the GA. For this specific VM I don't want that.
For me the bug is relatively recent. I am guessing the bug was introduced after 6.1.12 or with the jump from 5.4 to 5.10.
Over the last few years various VirtualBox elements seem to have been introduced into the mainline kernel.
First if was auto-resize guest display
More recently shared folders
The problem I identified here was occurring in a Guest with no Guest Additions. Even then it wasn't a problem at level 4 only at levels 3, 2 and 1. I don't know whether when a new guest is created does VirtualBox automatically suck in it's bespoke drivers or does it leave the Guest alone until Guest Additions is installed.
I'm led to the conclusion that this problem is with the mainline kernel and not VirtualBox.
Well based on what I have read in the VirtualBox help and manual, I going with not a bug. Bold is mine.
Quote:
Graphics Controller: Specifies the graphics adapter type used by the guest VM. Note that
you must install the Guest Additions on the guest VM to specify the VBoxSVGA or VMSVGA
graphics controller. The following options are available:
– VBoxSVGA: The default graphics controller for new VMs that use Windows 7 or later.
This graphics controller improves performance and 3D support when compared to the
legacy VBoxVGA option.
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default
graphics controller for Windows versions before Windows 7 and for Oracle Solaris.
3D acceleration is not supported for this graphics controller.
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device. This is the default graphics controller for Linux guests.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.