Virtualisation from an arch host to an 64x windows guest causes keyboard-layout troubles
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
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.
Virtualisation from an arch host to an 64x windows guest causes keyboard-layout troubles
hi there,
so when starting aqemu and setting up an windows 10 guest, write into at the very beginning you need the german layout, but secondary, when you have to enter layouts at configuration part of installation as german IBM with a wonderful keyboard definition (p.e. "g4" instead of "g" and "h7" instead of "h", use backspace as logout on kde...), it will change this to uefi-bios. when you try to login as administrator, you can't bacause you can't see what you're typing because of security reasens (the ***...), I couldn't enter bios. thank god I had a user-bios-pwd that fit with both layouts so I could look in kate what I entered.
Solution: reinstall the vm ASAP with the right definition again, but with aqemu not with vmware (or vbox? - with zen kernel???) as there are different parititon schemes with floppy and an interface for directly enter your name and password at the creation of the VM, so windows install won't ask again.
This is a big security leak, and can lead to the last alternative: reset the BIOS by manually set the jumper back to initialisation and even then it's on doubt that it could be changed back to us-en again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
