Opened 14 years ago
Closed 11 years ago
#9332 closed defect (obsolete)
clipboard support broken - OEL 5.6, OEL 6.1
| Reported by: | Peter Asboeck | Owned by: | |
|---|---|---|---|
| Component: | clipboard | Version: | VirtualBox 4.1.0 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description (last modified by )
VirtualBox 4.1.0 installed on Windows 7 64bit host.
Guests: Oracle Enterprise Linux 5.6 -> clipboard support broken
Oracle Enterprise Linux 6.1 -> clipboard support broken
Ubuntu 11.4 -> clipboard support OK (copy/paste between guest/host - OK)
Fedora 14 (Laughlin) -> clipboard support OK (copy/paste between guest/host - OK)
Attachments (1)
Change History (8)
follow-up: 2 comment:1 by , 14 years ago
comment:2 by , 14 years ago
Details about the installed guest OS - Oracle Enterprise Linux 6.1
$ lsb_release LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch [itsme@vm-oel-1 ~]$ lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: OracleServer Description: Oracle Linux Server release 6.1 Release: 6.1 Codename: n/a $ uname -a Linux vm-oel-1 2.6.32-100.34.1.el6uek.x86_64 #1 SMP Wed May 25 17:46:45 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux $ rpm -qa | grep uek kernel-uek-headers-2.6.32-100.34.1.el6uek.x86_64 kernel-uek-devel-2.6.32-100.34.1.el6uek.x86_64 kernel-uek-firmware-2.6.32-100.34.1.el6uek.noarch kernel-uek-2.6.32-100.34.1.el6uek.x86_64
You can get the kernel from http://public-yum.oracle.com/ ...
by , 14 years ago
| Attachment: | vboxadd-install.log added |
|---|
comment:3 by , 14 years ago
Sorry, forgot to check if VBoxClient is running ... VBoxClient doesn't start with "normal" user ... only with root ... then Clipboard Support (copy/paste) is ok.
[itsme@vm-oel-1 Desktop]$ uptime 11:04:49 up 0 min, 2 users, load average: 0.22, 0.06, 0.02 [itsme@vm-oel-1 Desktop]$ ps -ef | grep VBoxClient itsme 2334 2314 0 11:04 pts/0 00:00:00 grep VBoxClient [itsme@vm-oel-1 Desktop]$ VBoxClient --clipboard Failed to connect to the VirtualBox kernel service [itsme@vm-oel-1 Desktop]$ ping -c 3 www.yahoo.com PING eu-fp3.wa1.b.yahoo.com (87.248.122.122) 56(84) bytes of data. 64 bytes from ir1.fp.vip.ch1.yahoo.com (87.248.122.122): icmp_seq=1 ttl=56 time=62.2 ms 64 bytes from ir1.fp.vip.ch1.yahoo.com (87.248.122.122): icmp_seq=2 ttl=56 time=81.1 ms 64 bytes from ir1.fp.vip.ch1.yahoo.com (87.248.122.122): icmp_seq=3 ttl=56 time=85.3 ms --- eu-fp3.wa1.b.yahoo.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2087ms rtt min/avg/max/mdev = 62.297/76.244/85.326/10.016 ms [itsme@vm-oel-1 Desktop]$ su - root Password: [root@vm-oel-1 ~]# cd /media/VBOX* [root@vm-oel-1 VBOXADDITIONS_4.1.0_73009]# ls 32Bit runasroot.sh VBoxWindowsAdditions.exe 64Bit VBoxLinuxAdditions.run VBoxWindowsAdditions-x86.exe AUTORUN.INF VBoxSolarisAdditions.pkg autorun.sh VBoxWindowsAdditions-amd64.exe [root@vm-oel-1 VBOXADDITIONS_4.1.0_73009]# ./VBoxLinuxAdditions.run Verifying archive integrity... All good. Uncompressing VirtualBox 4.1.0 Guest Additions for Linux......... VirtualBox Guest Additions installer Removing installed version 4.1.0 of VirtualBox Guest Additions... Removing existing VirtualBox DKMS kernel modules [ OK ] Removing existing VirtualBox non-DKMS kernel modules [ OK ] Building the VirtualBox Guest Additions kernel modules Building the main Guest Additions module [ OK ] Building the shared folder support module [ OK ] Building the OpenGL support module [FAILED] (Look at /var/log/vboxadd-install.log to find out what went wrong) Installing the Window System drivers Installing X.Org Server 1.7 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 ] [root@vm-oel-1 VBOXADDITIONS_4.1.0_73009]# ps -ef | grep VBoxClient root 6541 2347 0 11:06 pts/0 00:00:00 grep VBoxClient [root@vm-oel-1 VBOXADDITIONS_4.1.0_73009]# exit logout [itsme@vm-oel-1 Desktop]$ VBoxClient --clipboard Failed to connect to the VirtualBox kernel service [itsme@vm-oel-1 Desktop]$ su - root Password: [root@vm-oel-1 ~]# VBoxClient --clipboard [root@vm-oel-1 ~]# echo $? 0 [root@vm-oel-1 ~]# ps -ef | grep VBoxClient root 6575 1 0 11:07 ? 00:00:00 VBoxClient --clipboard root 6579 6552 0 11:07 pts/0 00:00:00 grep VBoxClient [root@vm-oel-1 ~]#
comment:4 by , 14 years ago
[itsme@vm-oel-1 log]$ VBoxClient-all Failed to connect to the VirtualBox kernel service Failed to connect to the VirtualBox kernel service Failed to connect to the VirtualBox kernel service Failed to connect to the VirtualBox kernel service [itsme@vm-oel-1 log]$ su - root Password: [root@vm-oel-1 ~]# VBoxClient-all [root@vm-oel-1 ~]# echo $? 0 [root@vm-oel-1 ~]# ps -ef | grep VBoxClient root 3438 1 0 11:58 ? 00:00:00 /usr/bin/VBoxClient --clipboard root 3448 1 0 11:58 ? 00:00:00 /usr/bin/VBoxClient --display root 3453 1 0 11:58 ? 00:00:00 /usr/bin/VBoxClient --seamless root 3460 3407 0 11:59 pts/0 00:00:00 grep VBoxClient [root@vm-oel-1 ~]#
comment:5 by , 14 years ago
In this case "connect to the kernel service" means to open /dev/vboxuser, nothing network-related. Perhaps not the best way of expressing it in the error message... so it sounds like a permissions problem. Any idea what may be going wrong? Permissions are normally set in /etc/udev/rules.d/60-vboxadd.rules or /etc/init.d/vboxadd.
comment:6 by , 14 years ago
I FOUND THE WORKAROUND TO GET EVERYTHING RUNNING (including #9307) ... make -i !!
This steps "repair" some installation problems (diff is FAILED/OK on OpenGL !)
[root@vm-oel-2 ~]# cd /media/VBOXADDITIONS_4.1.0_73009 [root@vm-oel-2 VBOXADDITIONS_4.1.0_73009]# export MAKE='/usr/bin/gmake -i' [root@vm-oel-2 VBOXADDITIONS_4.1.0_73009]# ls 32Bit runasroot.sh VBoxWindowsAdditions.exe 64Bit VBoxLinuxAdditions.run VBoxWindowsAdditions-x86.exe AUTORUN.INF VBoxSolarisAdditions.pkg autorun.sh VBoxWindowsAdditions-amd64.exe [root@vm-oel-2 VBOXADDITIONS_4.1.0_73009]# ./VBoxLinuxAdditions.run Verifying archive integrity... All good. Uncompressing VirtualBox 4.1.0 Guest Additions for Linux......... VirtualBox Guest Additions installer Removing installed version 4.1.0 of VirtualBox Guest Additions... Removing existing VirtualBox DKMS kernel modules [ OK ] Removing existing VirtualBox non-DKMS kernel modules [ OK ] Building the VirtualBox Guest Additions kernel modules Building the main Guest Additions module [ OK ] Building the shared folder support module [ OK ] Building the OpenGL support module [ 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.7 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 ] [root@vm-oel-2 VBOXADDITIONS_4.1.0_73009]# /etc/init.d/vboxadd start Starting the VirtualBox Guest Additions [ OK ] [root@vm-oel-2 VBOXADDITIONS_4.1.0_73009]# ps -ef | grep -i vbox root 6438 1 0 13:07 ? 00:00:00 /usr/sbin/VBoxService root 6554 2286 0 13:08 pts/0 00:00:00 grep -i vbox [root@vm-oel-2 VBOXADDITIONS_4.1.0_73009]# /usr/bin/VBoxClient-all [root@vm-oel-2 VBOXADDITIONS_4.1.0_73009]#
REBOOT and services are starting ... clipboard working / mount of vboxsf working (#9307)
comment:7 by , 11 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Could you please include a log file as requested for at least one of the broken guests, preferably OEL6.1 as I am downloading that now? You also didn't mention whether the guests were 32 or 64bit, which at least with OEL5.6 is likely to be relevant as I believe they use a different kernel by default for the 64bit version.
If you are interested in helping to debug this, you could do the following on one of the affected guests: stop the process "VBoxClient --clipboard", and restart it (as your user on the VM, not as root!) exporting the environment variables "VBOX_RELEASE_LOG_DEST=file=<your home directory on the guest>/clipboard.log" and "VBOX_RELEASE_LOG=all.e.l.l2.l3.f". This should log all information about attempts to transfer clipboard data between guest and host (from the guest's point of view) to the file clipboard.log, which you can then upload here.
Thanks.