Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Num lock state for phyical key board read and set for vm #7307

Closed
Studmuffin1134 opened this issue Jan 13, 2024 · 9 comments
Closed

Num lock state for phyical key board read and set for vm #7307

Studmuffin1134 opened this issue Jan 13, 2024 · 9 comments

Comments

@Studmuffin1134
Copy link

The only feature I miss from Vmware's ESXI and Vcenter is how it could know that if you had your num lock on your keyboard on it would be on in the vm i dont know if you would have to do that through an option in the bios and or uefi firmware or if that could be a option in the advanced vm settings either way it would be nice

@olivierlambert
Copy link
Member

Hi,

Just to be sure: what you'd like to have is when you get access to the console, the num lock would be enabled by default, right?

@olivierlambert
Copy link
Member

Might be related or not, but posting as reference to investigate further:

@Studmuffin1134
Copy link
Author

but i dont use vnc typically if i need to do something quick i do it in the remote console insed of xo

@olivierlambert
Copy link
Member

So I'm not sure to understand. You want the VM to get caps lock on at boot then, regardless the way you access it?

It might be more an XCP-ng feature request than XO :) (also you have XO Lite BTW)

@Studmuffin1134
Copy link
Author

I did try it in xo lite it did not work and i dont think it is a feature in xcp-ng or xo i think it might be something u will need to do to the bios and uefi layer like TIANO core

@olivierlambert
Copy link
Member

Please try with XO Lite in case to confirm, and then we'll probably open a GH issue for XCP-ng project to investigate which component is doing this.

@Studmuffin1134
Copy link
Author

alright

@Studmuffin1134
Copy link
Author

yeah no she dont work i had to cycle my num lock after reboot of the vm in order to get it to work

@olivierlambert
Copy link
Member

Okay so probably an investigation for the XCP-ng team :) Please open an issue at https://github.com/xcp-ng/xcp/issues

Closing here!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants