Michael Thayer <michael.tha...@oracle.com> writes: > Hello Harry, > > On 11/07/14 02:12, Harry Putnam wrote: >> Running 4.3.12 VB on win7 host, with guest openindiana (solaris) >> >> What setting is likely to be responsible for me losing the keyboard on >> an existing vbox vm when updated to newest 4.3.12? >> >> Something to do with new USB code?.... currently that is set to `USB >> tablet' >> >> Then right below that setting, at `extended features' I have: >> >> [X] enable IO apic >> >> Is any of that relevant? > > I am jumping in a little late here. What is your keyboard set-up? > Standard PS/2 keyboard or USB? If you don't know it is likely the > first, you can also check in the machine XML file (the ".vbox" file for > the machine). Or are you using a physical USB keyboard directly with > the machine? Can you start an Ubuntu live CD in the virtual machine to > see if the keyboard works there?
Actual keyboard setup is usb. Virtual Keyboard setup is: Under `System' in vm settings: usb tablet Note that I have tried all the setting on that drop down: ps2/mouse usb tablet usb multi touch tablet Just now installed 4.3.14 and nothing changed. Installed 4.3.14 user additions.... again ... not change. I went back to `usb tablet' since 2 other vms on that same host work fine on that setting. (the other guests are Debian linux and the oracle release of solaris 11). Both other vms have no problem with keyboard working I didn't start an ubuntu live cd, but I had a SystemRescueCD disk (its based on gentoo) so started that and found the keyboard works as expected. OK, so its seems apparent that I've done something scewy to this one vm. The vm in question is running OpenIndiana solaris 151_9. Here is what happens at bootup: When the welcome/signin screen appears, the keyboard works fine to type in my username and passwd. Once the desktop appears, I click on the few Icons I have and they respond as expected... so mouse is fine. I click an Xterm icon.... when xterm starts I cannot type anything into it. Click an emacs icon... ditto... and onward. I can ssh into the vm and do anything I like. So still a mystery, but at least its apparent that it is a local situation. And further that it only occurs in X. Anymore input of ideas would be well received here. PS - I've been running this same vm for several months, and its only a few weeks since this problem started. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
