Running Ubuntu 17.10 as a VirtualBox guest works fine except for accessing files located on the host.
Only vboxguest and vboxvideo modules are available and loaded.
vboxsf module is missing.
Load the Guest Additions ISO image and let run the installer.
On a fresh new install, you may have this error :
Make sure to install the build-essential package :
apt install build-essential
One completed, reboot your system to make sure the right modules are loaded : vboxguest, vboxvideo, vboxsf
Once logged in, access to a directory located on your host may be denied.
Be sure that your user account is part of the vboxsf local group.
Add yourself :
usermod -aG vboxsf your_login
Log out and log in again. This should be good now
This issue appeared on HP blade Proliant XL170r Gen9 running ESXi 6.0.0, 4192238.
Make sure that your blades have their firmwares updated to the latest version.
Have a look at iLO self-Test Results :
Before firmwares upgrade :
After firmwares upgrade :
If you get a message within your vSphere client “Retrieve a ticket to register the Virtual SAN VASA Provider” for each of your ESXi host, this is a bug that appeared in vCenter Server 6.0 Update 2.
This bug is known but harmless. No patch available to fix it for now.
More details in this KB :
VMWare KB2145308 : Retrieve a ticket to register the Virtual SAN VASA Provider
This error can pop up when rebooting an ESXi host.
Make sure there is no hardware failure at the USB module level by reinstalling ESXi.
If you failed to reinstall ESXi, replace the USB module with a new one.
To install VirtualBox Guest Additions kernel modules on Debian Jessie, make sure to attach the “Guest Additions” CD-ROM image.
Copy the “VBoxLinuxAdditions.run script to /tmp
Then run it as below :
Install the missing tools gcc and make :
[fool@localhost:~]$ sudo apt-get install gcc make
Run the script again :
There is still a missing dependency :
Install it :
[fool@localhost:~]$ sudo apt-get install linux-headers-$(uname -r)
The VirtualBox Guest additions kernel modules can now be compiled and be loaded successfully :
Having either of these errors can lead to some services not started on the vCenter server.
503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec:00000000011D7F00] _serverNamespace = / _isRedirect = false _pipeName =\\.\pipe\vmware-vpxd-webserver-pipe)
503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::LocalServiceSpec:00000000012B0BA0] _serverNamespace = /vsphere-client _isRedirect = false _port = 9090)
If your vCenter is running on a Windows box, checking the status of its services can provide some first-hand information :
cd C:\Program Files\VMware\vCenter Server\bin
To stop all the services :
./service-control --stop --all
To start all the services :
./service-control --start --all
VMWare KB 2109881
A quick tip to check the version of the vmware tools installed in a Linux virtual server :
root@localhost:~# /usr/bin/vmware-toolbox-cmd -v
This command line tool is available if your VM is running on top of a host whose ESXi version is newer that 4.1