No keyboard after update to 4.3.12

[Harry Putnam]

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?

[Frank Mehnert]

Hi Harry,

Post by Harry Putnam
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?

are you really talking about 4.3.12 or is it rather 4.3.14 RC1?

Post by Harry Putnam
Something to do with new USB code?.... currently that is set to `USB
tablet'

There were only a few changes in the 4.3.12 USB code, 4.3.14 RC1 contains
more fundamental changes.

Post by Harry Putnam
[X] enable IO apic
Is any of that relevant?

Should not make any difference. Did you change any VM setting during
the upgrade? What was the old version you used before the upgrade?

Kind regards,

Frank
--
Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox
ORACLE Deutschland B.V. & Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany

Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher

[Harry Putnam]

Post by Frank Mehnert
Hi Harry,

Post by Harry Putnam
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?

are you really talking about 4.3.12 or is it rather 4.3.14 RC1?

4.3.12 (How does one even get 4.3.14 RC1?)

Post by Frank Mehnert

Post by Harry Putnam
Something to do with new USB code?.... currently that is set to `USB
tablet'

There were only a few changes in the 4.3.12 USB code, 4.3.14 RC1 contains
more fundamental changes.

Post by Harry Putnam
[X] enable IO apic
Is any of that relevant?

Should not make any difference. Did you change any VM setting during
the upgrade? What was the old version you used before the upgrade?

At this point I really don't remember. I might have changed disc
type from PIIX3 to ICH9. But at any rate I have now tried both and
still have no keyboard input

(Frank M. Asked: What was previous version? [paraphrased by -ed])
I sound like a darned dope, but I'm not sure about that either.
Judging from the downloaded binaries still in ~/Download. Looks like
it might have been 4.1.32-92798 Win exe.

I've noticed an announcement about 4.3.14 being released... but when I
check for updates in 4.3.12... it tells me I'm running the latest.

Is it likely that upgrading to 4.3.14 would result in a working
keyboard input situation?

[Geoff Nordli]

Post by Harry Putnam

Post by Frank Mehnert
Hi Harry,

Post by Harry Putnam
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?

are you really talking about 4.3.12 or is it rather 4.3.14 RC1?

4.3.12 (How does one even get 4.3.14 RC1?)

4.3.14 was released a couple of days ago so you should be able to grab
it now.

I would try it out to see if it solves your KB issues.

Geoff

[Michael Thayer]

Hello Harry,

Post by Harry Putnam
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'
[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?

Regards,

Michael
--
ORACLE Deutschland B.V. & Co. KG Michael Thayer
Werkstrasse 24 VirtualBox engineering
71384 Weinstadt, Germany mailto:michael.thayer-QHcLZuEGTsvQT0dZR+***@public.gmane.org

Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher

[Harry Putnam]

Michael Thayer

Post by Michael Thayer
Hello Harry,

Post by Harry Putnam
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'
[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.

[Michael Thayer]

Hello Harry,

Post by Michael Thayer
Michael Thayer

Post by Michael Thayer

Post by Harry Putnam
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?

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.
usb tablet

[...]

Post by Michael Thayer
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.
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.

It sounds to me like something grabbing your keyboard. Perhaps one of
these two links would help you (don't worry about talk of grabbing the
pointer, it should still apply):

https://blogs.oracle.com/alanc/entry/grabbing_information_from_the_x
http://unix.stackexchange.com/questions/59141/find-x-org-pointer-grab-owner

Otherwise the traditional method to fix that, if that is really the
problem, is to ssh in and to kill things until the keyboard comes back.
You could begin with "VBoxClient" processes to establish from the
start whether we are to blame or not!

By the way, although it is almost certainly not important after all, I
presume your virtual machine is using PS/2 keyboard emulation. There is
no function to change that in the graphical interface, what you referred
to above is the pointer set-up.

Hope that helps.

Regards,

Michael
--
ORACLE Deutschland B.V. & Co. KG Michael Thayer
Werkstrasse 24 VirtualBox engineering
71384 Weinstadt, Germany mailto:michael.thayer-QHcLZuEGTsvQT0dZR+***@public.gmane.org

Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher

[Harry Putnam]

Michael Thayer

Post by Michael Thayer
Otherwise the traditional method to fix that, if that is really the
problem, is to ssh in and to kill things until the keyboard comes back.
You could begin with "VBoxClient" processes to establish from the
start whether we are to blame or not!

Thanks for the links... Just barely looked at the first so far... very
neat, what ever that software is that makes X-server reveal all that
stuff....

This is just a note and there will be a fuller response after I get
some sleep. Just wanted to let you know that I did ssh in and kill
everything to do with VboxClient.

Then shut down the services with vbox in there name: vboxserver and
vboxmslnk. And I've still got no keyboard.... so I guess vbox is not
the villain after all.

[Harry Putnam]

Michael Thayer

Post by Michael Thayer
It sounds to me like something grabbing your keyboard. Perhaps one of
these two links would help you (don't worry about talk of grabbing the
https://blogs.oracle.com/alanc/entry/grabbing_information_from_the_x
http://unix.stackexchange.com/questions/59141/find-x-org-pointer-grab-owner

It just seem a bit off the wall that resolution was fine just prior to
recent update.... Those links may be on the mark but can you examine
the commentary and output from installed a newer 'Guest Additions'
below?. It may give you some insight that I am totally missing.

A poster on debian.user group cited this url:

------- ------- ---=--- ------- -------
From: Andreas Rönnquist <***@gusnan.se>
Subject: Re: Lost high res desktop settings on vbox upgrade to 4.3.14
Newsgroups: gmane.linux.debian.user
Message-ID: <***@debian-workstation.lan>

An ISO with guest additions is linked in the final post here:

https://forums.virtualbox.org/viewtopic.php?f=3&t=62629

That solved the problem(s) for me.
------- ------- ---=--- ------- -------

What its about is installing 4.3.15 guest additions as a fix

Downloaded, mounted and installed from that iso.

However, after a restart I still have no res choices other than
1024x768.

Maybe this is the reason:

When I do the install, I get a warning that the header files for my
running kernel were not found.

ASIDE showing installed kernel and installed header pkgs:
NOTE: uname -r
3.14-1-486

aptitude search headers |grep ^i

i linux-headers-3.14-1-486 - Header files for Linux 3.14-1-486
i A linux-headers-3.14-1-686-pae - Header files for Linux 3.14-1-686-pae
i linux-headers-3.14-1-all-i386 - All header files for Linux 3.14 (meta-pack
i A linux-headers-3.14-1-amd64 - Header files for Linux 3.14-1-amd64
i A linux-headers-3.14-1-common - Common header files for Linux 3.14-1
i A linux-headers-3.14-1-common-rt - Common header files for Linux 3.14-1-rt
i A linux-headers-3.14-1-rt-686-pae - Header files for Linux 3.14-1-rt-686-pae

(surely one of those installed pkgs has to be the right headers..You'd
think the very first one is it....so why are they not found...)

The next steps are building the modules.... and near as I can tell it
succeeds:

here is the action:

------- ------- ---=--- ------- -------
NOTE:
Since I have already installed the iso you'll notice it remove that
pkg and then re-installs it.

There is some commentary about xorg driver not being installed that
might also be why I'm not getting the result you did.

There seems to be nothing mentioned to indicate any modules failed
to build so perhaps the bit about the X.org drivers not being
installed is the main culprit?
------- ------- ---=--- ------- -------

(I've marked out the pertinent parts with asterisks).

root # sh VBoxLinuxAdditions.run

Verifying archive integrity... All good.
Uncompressing VirtualBox 4.3.15 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 4.3.15 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules

*********************************************************
The headers for the current running kernel were not found. If the
following module compilation fails then this could be the reason.
*********************************************************

Building the main Guest Additions module ...done.
Building the shared folder support module ...done.
Building the OpenGL support module ...done.
Doing non-kernel setup of the Guest Additions ...done.

You should restart your guest to make sure the new modules are
actually used

Installing the Window System drivers

***************************************************************
Warning: unsupported pre-release version of X.Org Server installed. Not
installing the X.Org drivers.
...done.
***************************************************************

Installing graphics libraries and desktop services components ...done.


------------------------------------------------------------------------------
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-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe: mailto:vbox-users-com

[Michael Thayer]

Hello Harry,

Post by Michael Thayer
Michael Thayer

Post by Michael Thayer
It sounds to me like something grabbing your keyboard. Perhaps one of
these two links would help you (don't worry about talk of grabbing the
https://blogs.oracle.com/alanc/entry/grabbing_information_from_the_x
http://unix.stackexchange.com/questions/59141/find-x-org-pointer-grab-owner

It just seem a bit off the wall that resolution was fine just prior to
recent update.... Those links may be on the mark but can you examine
the commentary and output from installed a newer 'Guest Additions'
below?. It may give you some insight that I am totally missing.

The Guest Additions should not have anything to do with keyboard
handling. The only reason they might is if they contain a bug, in which
case removing them would be the way to check, but stopping VBoxClient
would be likely to have the same effect. Installing a different version
should really not be necessary for you, and the version you pointed to
is simply an update to support the X server version which was released a
few days ago.

It really does sound to me like you have a configuration problem in the
guest operating system or X server.

Regards,

Michael
--
ORACLE Deutschland B.V. & Co. KG Michael Thayer
Werkstrasse 24 VirtualBox engineering
71384 Weinstadt, Germany mailto:***@oracle.com

Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher

------------------------------------------------------------------------------
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-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe: mailto:vbox-users-community-request@