virtualbox.org

I'll look around and try that.... I have no idea how I got them though as I do not have VMware on my machine.... Thanks!

Though I did just do this and have no clue how they got here:

sbh@sbh-MacBookPro:~$ locate *vmware*
/usr/bin/vmwarectrl
/usr/lib/directfb-1.2-9/gfxdrivers/libdirectfb_vmware.so
/usr/lib/xorg/modules/drivers/vmware_drv.so
/usr/share/app-install/desktop/vmware-view-open-client:vmware-view.desktop
/usr/share/app-install/icons/_usr_share_pixmaps_vmware-player.png
/usr/share/app-install/icons/vmware-view.png
/usr/share/apport/package-hooks/source_xserver-xorg-video-vmware.py
/usr/share/bug/xserver-xorg-video-vmware
/usr/share/bug/xserver-xorg-video-vmware/script
/usr/share/doc/xserver-xorg-video-vmware
/usr/share/doc/xserver-xorg-video-vmware/changelog.Debian.gz
/usr/share/doc/xserver-xorg-video-vmware/copyright
/usr/share/grub-gfxpayload-lists/blacklist/10_vmware
/usr/share/jockey/handlers/vmware-client.py
/usr/share/man/man4/vmware.4.gz
/usr/src/linux-headers-3.2.0-23-generic/include/config/vmware
/usr/src/linux-headers-3.2.0-23-generic/include/config/vmware/balloon.h
/usr/src/linux-headers-3.2.0-23-generic/include/config/vmware/pvscsi.h
/usr/src/linux-headers-3.2.0-60-generic/include/config/vmware
/usr/src/linux-headers-3.2.0-60-generic/include/config/vmware/balloon.h
/usr/src/linux-headers-3.2.0-60-generic/include/config/vmware/pvscsi.h
/var/lib/dpkg/info/xserver-xorg-video-vmware.conffiles
/var/lib/dpkg/info/xserver-xorg-video-vmware.list
/var/lib/dpkg/info/xserver-xorg-video-vmware.md5sums

Looking around I see that I do not have the open-vm-tools installed...:

sbh@sbh-MacBookPro:~$ apt-get -s install open-vm-tools
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Also keep in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
ethtool libdumbnet1 open-vm-dkms zerofree
Suggested packages:
open-vm-toolbox
The following NEW packages will be installed:
ethtool libdumbnet1 open-vm-dkms open-vm-tools zerofree
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Inst ethtool (1:3.1-1 Ubuntu:12.04/precise [amd64])
Inst libdumbnet1 (1.12-3.1 Ubuntu:12.04/precise [amd64])
Inst open-vm-dkms (2011.12.20-562307-0ubuntu1 Ubuntu:12.04/precise [all])
Inst open-vm-tools (2011.12.20-562307-0ubuntu1 Ubuntu:12.04/precise [amd64])
Inst zerofree (1.0.1-2ubuntu1 Ubuntu:12.04/precise [amd64])
Conf ethtool (1:3.1-1 Ubuntu:12.04/precise [amd64])
Conf libdumbnet1 (1.12-3.1 Ubuntu:12.04/precise [amd64])
Conf open-vm-dkms (2011.12.20-562307-0ubuntu1 Ubuntu:12.04/precise [all])
Conf open-vm-tools (2011.12.20-562307-0ubuntu1 Ubuntu:12.04/precise [amd64])
Conf zerofree (1.0.1-2ubuntu1 Ubuntu:12.04/precise [amd64])

I have no idea why this is giving me libGL errors.

Yikes, so we both have an issue... Well doing some googling I came across this:

sbh@sbh-MacBookPro:/usr/lib/nux$ ./unity_support_test -p
Xlib: extension "NV-GLX" missing on display ":0".
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x300)
OpenGL version string: 1.4 (2.1 Mesa 8.0.4)

Not software rendered: no
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: no
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: no

the take home being that the author was saying VMware, Inc. name was there only for the credit of llvmpipe. Mine also does say Gallium so I guess I have no reason to believe (this is a relatively new install) that these are not the wrong drivers. Of course I may very well likely be wrong.

could someone explain why I get this error in the above post?... libGL error: failed to load driver: vboxvideo

obviously since I can see my screen and 3D is working vboxvideo must me loaded.

@brett,
The VMware items are for software acceleration and don't mean a lot actually. Once you get the VBox guest additions working they will not be used.
I would purge all VBox packages from the guest and reboot, then install them again by clicking the device tab and insert guest additions. Watch the terminal closely for warnings and errors.

@loukingjr,
I see this as well in the newer versions of OSes and VBox. Not to worry though as I think it is just some reporting error.

thanks Perry. I thought perhaps it couldn't find it because another symlink was pointing to the wrong place.

Hi Perry, thanks for your suggestion! So I did

apt-cache search vbox

which resulted in a list of ISDN utilities I would never have installed (and I checked with apt-get -s install to make sure they weren't there).

So I couldn't really do a purge on a specific package or set of packages, even though I have done

sudo apt-get --purge autoclean.

So I then did this:

dpkg-query --list | tee /media/sf_sbh/Desktop/output.file

so I could see a list of packages and then looked for *vbox* and *Vbox* and *VBox* but turned up nothing.

SO. I am at a loss as to how to purge these problem packages without being able to know what they are! ha ha Any ideas? (I can include the text file [copy and paste] if needed).

P.S. Maybe the DKMS modules are listed by this command.... Is that the problem pieces maybe?

sbh@sbh-MacBookPro:~$ dkms status
bcmwl, 6.20.155.1+bdcom, 3.2.0-23-generic, x86_64: installed
bcmwl, 6.20.155.1+bdcom, 3.2.0-60-generic, x86_64: installed (WARNING! Diff between built and installed module!)
nvidia-304-updates, 304.116, 3.2.0-23-generic, x86_64: installed
nvidia-304-updates, 304.116, 3.2.0-60-generic, x86_64: installed
vboxguest, 4.3.10, 3.2.0-23-generic, x86_64: installed

Just saw your suggestion... so I did that:

The following packages will be REMOVED:
virtualbox-guest-utils*

try sudo apt-get purge virtualbox*

Okay... so I did

sudo apt-get purge virtualbox*

which cleared away

virtualbox-guest-utils*

I then rebooted the virtual machine, then re-installed the guest additions, and still greyed out seamless. I did notice as well that even during the virtualbox splash menu (before GRUB) that the options were greyed out... I'm at a loss...

brett wrote:So I used the uninstall tool and then reinstalled. I noticed that root:admin are all over the /Applications/VirtualBox.app/*

I wonder if this could have anything to do with it...(this is how I created the rawdisks);

sudo VBoxManage internalcommands createrawvmdk -filename VM.vmdk -rawdisk /dev/disk0 -partitions 4
chown 777 VM*
chown sbh:admin VM*
sudo chmod 777 /dev/disk0s4 (the ubuntu partition)

I also unmount the ubuntu partition from the Mac each time....

I missed this post altogether. I didn't realize you were trying to work with raw disks. I don't know anything about working with them. Perhaps that is causing your issue?

Well I don't really know much about them but I DO know that several versions of VB ago, and many kernels ago, it did work... Maybe my next step is to rebuild the vmdk files using the internal commands and try that, after all they are from several versions of VB ago. Not sure if there is anything in them that would change - I don't see why - no partition changes, etc.... Well thank you for your help though!

what I would try is to create a new vm using something like Lubuntu using a dynamic .vdi and once you install the GAs into that see if seamless is still greyed out once it's booted..

Sounds like a good idea to rule out certain things on the host or the VB install. Maybe I could even get it to work, hex/text/Diff the files between that and the rawdisks, and maybe even translate them! ha ha.. well sounds like a bit of work so it'll be a day before i get back. Thanks for the idea.

well good luck. I just know I have been using VB for almost 5 years and have installed hundreds of guests and never had the seamless menu grayed out.

edit: that was on three different iMacs starting on a 2007 iMac up through a late 2012 iMac.

FYI, well I got Linux Puppy to work - no greyed out selection. Seamless worked fine using your suggestion. I then "slowly" tried to change IDE and SATA controllers to the vmdk files and after changing the SATA controller the options got greyed out. So one last attempt at internal commands.