Numlock status on boot
-
- Posts: 63
- Joined: 29. Jun 2012, 10:02
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows (XP, 7, 10), Linux
Numlock status on boot
Since as it seems, there is no way to alter any BIOS settings in VBox, it would be really great if there was an option in settings to let the user define the NumLock state at boot.
Re: Numlock status on boot
All of the online guides I've seen are OS Specific, i.e. they do have to be set/activated within the OS, in which case you would have to work directly with the individual Guest OS(s), not the Host OS/VirtualBox. For MS Windows there are many online guides to the Registry tweak(s) required, and similar guides for Linux variants.
-
- Posts: 63
- Joined: 29. Jun 2012, 10:02
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows (XP, 7, 10), Linux
Re: Numlock status on boot
Yup, i know. I'm talking about the BIOS one. All BIOSs (the older ones at least) have such a setting. It would be nice if there was one in VBox too.erdeslawe wrote:All of the online guides I've seen are OS Specific, i.e. they do have to be set/activated within the OS, in which case you would have to work directly with the individual Guest OS(s), not the Host OS/VirtualBox.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Numlock status on boot
A quick search of the pdf version reveals three things:
First, the manual writers chose to write both "numlock" and "num lock", so we'd have to search for both.
Second, searching for "numlock" we find that the only reference is under "Known Issues", section 14.2, that Mac hosts don't have numlock emulation yet.
Third, searching "num lock" has this as the only reference:
It seems that on Windows and Linux hosts, the status of numlock in the guest is supposed to be the same as the numlock status in the host.
All the settings in a normal old-school BIOS that the developers determined to make any sense in adjusting in a guest are in the Guest settings in the main Virtualbox window, or in the Vboxmanage commands. We can consider the guest Settings to be our guest's BIOS adjustment page.
If you can make a case for why Numlock should always be a certain way when starting a particular guest you can suggest it to the developers as an enhancement on the Bugtracker. But having the guest follow the keyboard status rather than a BIOS setting seems to me to be better. Imagine someone sets the "BIOS" to have Numlock off when starting the guest rather than synchronize with the host Numlock status, and forgets about it, then starts the guest while used to the usual Numlock On behavior of the host, he'll go around the forums saying "Virtualbox is broken!"
First, the manual writers chose to write both "numlock" and "num lock", so we'd have to search for both.
Second, searching for "numlock" we find that the only reference is under "Known Issues", section 14.2, that Mac hosts don't have numlock emulation yet.
Third, searching "num lock" has this as the only reference:
I sure seem to remember some Vboxmanage command about numlock, but I can't find it searching the manual, and I might be remembering incorrectly. Might have been about the lights rather than the key status itself.The Manual wrote:15.19 Version 5.0.4 (2015-09-08)
This is a maintenance release. The following items were fixed and/or added:
.........
• GUI: fixed issues with synchronization of Caps lock / Num lock / Scroll lock on Windows hosts (bug #14302)
It seems that on Windows and Linux hosts, the status of numlock in the guest is supposed to be the same as the numlock status in the host.
All the settings in a normal old-school BIOS that the developers determined to make any sense in adjusting in a guest are in the Guest settings in the main Virtualbox window, or in the Vboxmanage commands. We can consider the guest Settings to be our guest's BIOS adjustment page.
If you can make a case for why Numlock should always be a certain way when starting a particular guest you can suggest it to the developers as an enhancement on the Bugtracker. But having the guest follow the keyboard status rather than a BIOS setting seems to me to be better. Imagine someone sets the "BIOS" to have Numlock off when starting the guest rather than synchronize with the host Numlock status, and forgets about it, then starts the guest while used to the usual Numlock On behavior of the host, he'll go around the forums saying "Virtualbox is broken!"
Re: Numlock status on boot
This is my top complaint on VirtualBox.
Relying on guest OS hacks is bad practice and advice, this has to be fixed in VM configuration, because that is the way physical systems behave!
Relying on guest OS hacks is bad practice and advice, this has to be fixed in VM configuration, because that is the way physical systems behave!
-
- Volunteer
- Posts: 2560
- Joined: 30. May 2007, 18:05
- Primary OS: Fedora other
- VBox Version: PUEL
- Guest OSses: XP, Win7, Win10, Linux, OS/2
Re: Numlock status on boot
I haven't seen a physical system BIOS with a with a num lock setting for many years...
Re: Numlock status on boot
In case someone else stumbles across this via Google - this is the solution (may have to be run while VirtualBox is closed):
Source (and more detailed info in case you need it): https://martinvanbeurden.nl/blog/virtua ... weirdness/
Code: Select all
VBoxManage setextradata "<machine-name>" GUI/HidLedsSync "0"
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Numlock status on boot
In case someone else wants to actually read the User Manual (which BTW comes in searchable PDF format), go to chapter 9.28. Support for keyboard indicators synchronization, no need for 3rd party sites. In fact, I'll quote the whole thing here:notthere wrote:In case someone else stumbles across this via Google
BTW @notthere, makes me wonder why you posted this info on another person's thread, and not on your very own "Num lock? Still? Seriously?" that deals with the same issue...This feature makes the host keyboard lights match those of the virtual machine's virtual keyboard when the machine window is selected. It is currently implemented for Mac OS X and Windows hosts and available as of releases 4.2.24 and 4.3.8. The feature can be enabled using the following command:In order to disable it, use the same command but change "1" to "0", or use the VBoxManage command to remove the extra data. This is a per-VM setting and it is disabled by default.
VBoxManage setextradata "VM name" GUI/HidLedsSync "1"
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 2
- Joined: 8. Feb 2019, 13:33
Re: Numlock status on boot
Hi, I had the same problem. I have VirtualBox 5.2, host machine Windows 8, guest VM Linux Lubuntu 18. I solved this way:
from Lubuntu settings: Preferences > Keyboard > Activate numpad at start
Hope it helps.
from Lubuntu settings: Preferences > Keyboard > Activate numpad at start
Hope it helps.
-
- Posts: 1
- Joined: 14. Apr 2021, 22:29
Re: Numlock status on boot
I am not sure if the described setting would trigger or solve my problem.
When I had installed a Linux Endeavour OS after trying to boot it from the vdi the screen stayed black and the screen message was flickering, like blinking on and off on top of the black creen: "scroll lock on" and "scroll lock off" permanently.
Maybe it has to do with the situation, tht I connect to my workstation PC (which is the virtualbox host, a Z440 by HP) via itarian, one RMM tool. Then I use the virtualbox on the remotely managed system from here on my laptop (a zbook by HP).
Is this a common behaviuor that happens with the installation of Arch?
When I had installed a Linux Endeavour OS after trying to boot it from the vdi the screen stayed black and the screen message was flickering, like blinking on and off on top of the black creen: "scroll lock on" and "scroll lock off" permanently.
Maybe it has to do with the situation, tht I connect to my workstation PC (which is the virtualbox host, a Z440 by HP) via itarian, one RMM tool. Then I use the virtualbox on the remotely managed system from here on my laptop (a zbook by HP).
Is this a common behaviuor that happens with the installation of Arch?
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Numlock status on boot
"Suggestions" is not for support questions. Please ask your own question in an appropriate forum, i.e. "Linux Guests".