virtualbox.org

virtualbox 4.3.8 r92456

two vm's on same 64 bit . . . windows 7 service pack 1 . . . host

see the two vm desktops side by side running on the same windows 7 host . . . 1) bmw (guest 64 bit linux rhel 6.5 server) . . . mouse fails . . . as soon as the mouse enters vm graphical area the screen saver stays black . . . if one clicks once with the left mouse button mouse disappears and then to get the mouse pointer to reappear one has to press the Right Ctrl key 2) benz (guest 64 bit linux rhel 6.5 server) . . . mouse works great . . . as soon as the mouse enters vm graphical area the screen saver stops and the mouse can click on the gui linux desktop items just fine

This sounds normal since there is no X on the server and as such no guest additions are installed to allow for mouse integration.

what is meant by "X on the server and as such no guest additions are installed to allow for mouse integration." please advise . . . what are the steps to put "X on the server?"

the 2014_03_14__bmw__evidence.txt shows guest additions are installed and loaded / running at least at the command line through putty . . .

Starting the VirtualBox Guest Additions [ OK ]
Starting VirtualBox Guest Addition service [ OK ]

When you start the server do you get a desktop or just the CLI ( TTY )?
If you don't startx then the drivers are not loaded and can not be used.

yes when the server is started a gui x windows desktop appears on bmw just like benz with a list of users to pick from . . . so now what you meant by "X on the server" is X windows gui desktop on the server . . . and if one would look at the 2014_03_14__bmw__evidence.txt file provided one would see the following showing evidence that the X windows gui desktop is loading just fine . . .

Starting xrdp: [ OK ]
Starting xrdp-sesman: [ OK ]

. . . to prove with gui desktop pictures the one posting this thread will have to post pictures MONDAY__2014_03_18 . . . since the vm's are at the office rather than here at home . . . so for now all will need to trust bmw is just like benz and has the same gui desktop behind the black screen saver screen shown on the left of the picture already provided . . . please until MONDAY just imagine the same looking gui desktop for bmw that one sees for benz except on bmw one is unable to get past the choose a userid gui screen because the mouse disappears as soon as one tries to click on the gui and then one has to press the Right Ctrl key to free up the mouse back to windows 7 . . . yes it is understood that the evidence above is somewhat weak because xrdp (used for RDC . . . remote desktop connection client to connect and display the linux gui desktop) is indirectly related to pure xwindow's processes . . . so new graphic images will be posted and a list of xwindows processes will also be provided in due time if this is really needed to make progress on this item.

Man you are bouncing all over the place. Let's stick with the facts and go through this logically. First the indications in your first post was misleading. Servers normally don't have desktops. So now you say the reason for the black screen was because of a screen saver. Anyway, if you have a desktop you have X so forget that part.

Now the part where you say the mouse gets captured and you need to press the host key to release it means that mouse integration is not working or the guest additions are not installed or working properly. Next if you are using RDP to get to the server you need to take into account that mouse may not work properly at all. VNC is better for Linux in that respect.

Is this remote server something that you will be physically near in the future, where you can work on it locally?

facts
1) these two servers have gui desktops . . . why would someone post something about mouse failing to work with guest additions if the linux servers where completely accessed through a text based interface?
2) let's remember both have gui x windows desktops . . . why would we forget this crucial fact?
3) only on bmw does the mouse get captured and one has to press the Right Ctrl key to release it
4) on benz which was setup the same way the mouse works seamlessly . . . transitions automatically between windows 7 and linux . . . works great
5) one is not using RDP to get to the server yet . . . only brought this up to assure all that xwindows is installed, configured, and running on both servers.
6) please just focus on this problem (guest additions by all evidence is installed correctly on both servers but one server is working properly and the other server is failing) and stay away from troubleshooting some other imagined problem like "if you are using RDP to get to the server you need to take into account that mouse may not work properly at all. VNC is better for Linux in that respect." RDP is working just fine with RDC. "VNC is better for linux" is an opinion. so as one recently said "Let's stick with the facts" and leave opinion out of this. the one who started this thread has been accused of bouncing all over the place but the one responding to this post seems to be the one bouncing all over the place . . . 1st bounce [attempted to assert the troublesome server was without an X windows gui desktop] . . . 2nd bounce [attempted to troubleshoot a non-existent RDP issue]
7) "Is this remote server something that you will be physically near in the future, where you can work on it locally?" yes as stated earlier . . . MONDAY__2014_03_17(oops associated the wrong calendar day number with the next MONDAY coming up) . . . either way MONDAY__2014_03_17 and / or TUESDAY__03_18 are both in the future.

In that case it may be easier to fix Monday when you can eliminate the remote desktop protocol.

But in any case, if you are having to press the host key to release the mouse, the mouse integration is not working. If it were you would not need to press the host key to release it.
Only two things will cause this.

1) guest additions failed at some point.
2) mouse integration is disabled for the guest.

The ( host+i ) toggle turns this off and on, if you can get that to work remotely, or open the machine tab at the top of the guest and make sure that it is enabled.

1) benz . . . Disable Mouse Integration . . . is working and (Host+I) worky . . . toggles this item on and off just fine 2) bmw . . . Disable Mouse Integration . . . is greyed out and (Host+I) thus fails . . . nothing changes when Host+I is attempted

2) bmw . . . Disable Mouse Integration . . . is greyed out and (Host+I) thus fails . . . nothing changes when Host+I is attempted

Then the guest additions are either not installed or not working. Install them again and watch the terminal window closely for errors.

Something else bothers me. You always show "bmw" without a desktop. Show me a valid desktop.

also RDP (remote desktop protocol) plus RDC (remote desktop connection) works (worky) just fine . . . and the mouse on the gui desktop there works just fine . . . on both guest rhel 6.5 vm's . . .

Remote is not the same as local. You say locally that the mouse integration is disabled. I can't say it any clearer, if the integration is not available the guest additions are not working. Install the guest additions again in a terminal and watch for errors. If no errors then reboot the guest and see if it works and if not then post the /var/log/vboxadd-install.log and the /var/log/Xorg.0.log ( as attachments )

the guest additions appear to install . . . but fails to work . . . installed them again and watched the terminal window closely and all looks error free?
**************************************************************************
cd /mnt
umount /mnt/iso
ls -al
mount -t iso9660 /dev/dvd iso
cd iso
ls -al ./VBoxLinuxAdditions.run
./VBoxLinuxAdditions.run
**************************************************************************
**************************************************************************
tcsh:root@bmw:/> cd /mnt
tcsh:root@bmw:/mnt> ls -al
total 10
drwxr-xr-x. 3 root root 4096 Mar 13 18:25 .
dr-xr-xr-x. 28 root root 4096 Mar 17 08:37 ..
dr-xr-xr-x 6 root root 2048 Feb 25 10:27 iso
tcsh:root@bmw:/mnt> mount -t iso9660 /dev/dvd iso
mount: block device /dev/sr0 is write-protected, mounting read-only
tcsh:root@bmw:/mnt> cd iso
tcsh:root@bmw:/mnt/iso> ls -al
total 56927
dr-xr-xr-x 6 root root 2048 Feb 25 10:27 .
drwxr-xr-x. 3 root root 4096 Mar 13 18:25 ..
dr-xr-xr-x 2 root root 2048 Feb 25 10:27 32Bit
dr-xr-xr-x 2 root root 2048 Feb 25 10:27 64Bit
-r-xr-xr-x 1 root root 647 Oct 8 09:30 AUTORUN.INF
-r-xr-xr-x 1 root root 6966 Feb 25 10:20 autorun.sh
dr-xr-xr-x 2 root root 2048 Feb 25 10:27 cert
dr-xr-xr-x 2 root root 2048 Feb 25 10:27 OS2
-r-xr-xr-x 1 root root 5523 Feb 25 10:20 runasroot.sh
-r-xr-xr-x 1 root root 9891275 Feb 25 10:23 VBoxLinuxAdditions.run
-r-xr-xr-x 1 root root 20738048 Feb 25 10:34 VBoxSolarisAdditions.pkg
-r-xr-xr-x 1 root root 16878160 Feb 25 10:18 VBoxWindowsAdditions-amd64.exe
-r-xr-xr-x 1 root root 311584 Feb 25 10:08 VBoxWindowsAdditions.exe
-r-xr-xr-x 1 root root 10444920 Feb 25 10:10 VBoxWindowsAdditions-x86.exe
tcsh:root@bmw:/mnt/iso> ./VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.3.8 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 4.3.8 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox DKMS kernel modules [ OK ]
Removing existing VirtualBox non-DKMS kernel modules [ OK ]
Building the VirtualBox Guest Additions kernel modules [ OK ]
Doing non-kernel setup of the Guest Additions [ OK ]
You should restart your guest to make sure the new modules are actually used

Installing the Window System drivers
Installing X.Org Server 1.13 modules [ OK ]
Setting up the Window System to use the Guest Additions [ OK ]
You may need to restart the hal service and the Window System (or just restart
the guest system) to enable the Guest Additions.

Installing graphics libraries and desktop services componen[ OK ]
tcsh:root@bmw:/mnt/iso>

**************************************************************************

**************************************************************************
ls -al /var/log/vboxadd-install.log
cat /var/log/vboxadd-install.log
**************************************************************************
**************************************************************************
tcsh:root@bmw:/> ls -al /var/log/vboxadd-install.log
-rw-r--r-- 1 root root 1236 Mar 17 11:24 /var/log/vboxadd-install.log
tcsh:root@bmw:/> cat /var/log/vboxadd-install.log
Uninstalling modules from DKMS
Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxguest/4.3.8/source ->
/usr/src/vboxguest-4.3.8

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area...
make KERNELRELEASE=2.6.32-431.1.2.el6.x86_64 -C /lib/modules/2.6.32-431.1.2.el6.x86_64/build M=/var/lib/dkms/vboxguest/4.3.8/build...........
cleaning build area...

DKMS: build completed.

vboxguest:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/2.6.32-431.1.2.el6.x86_64/extra/

vboxsf.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/2.6.32-431.1.2.el6.x86_64/extra/

vboxvideo.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/2.6.32-431.1.2.el6.x86_64/extra/
Adding any weak-modules

depmod...

DKMS: install completed.
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.
tcsh:root@bmw:/>

**************************************************************************

And the /var/log/Xorg.0.log ( as an attachment )

Extra question, do you Always run as root?