This feature is still HIGHLY experimental at this time. This yet to be officially named service enables users to access their Shared virtual machines via a web browser without installing any plug-ins or web controls.  This service renders an HTML5 web page that can connect to your Workstation hosts or ESXi servers (requires vSphere 5.0), enumerate the available virtual machines and allow you to power them on and interact with the desktop. Both the Windows .msi and Linux .bundle installations areavailable for download as part of the Technology Preview.

Both the Windows .msi and Linux .bundle installations are available for download as part of the Technology Preview.

This software has several limitations:

  • You must be on the same network as your host to access you VMs
  • This feature requires a very modern browser that supports HTML5 with WebSockets.   We have had success with Chrome 17, Firefox 10, IE 10 (currently not as well supported), Safari 5 on Mac OS hosts and iOS 5 on the iPad.  This may work with other browsers and on Android tablets running Ice Cream Sandwich with the latest version of Google Chrome installed, but we need to do more testing to get a more complete list.
  • This feature is not scalable.  We have not yet tested this for scalability and only expect it to work well for a couple of concurrent connections.

To run WSX on a Windows host

  1. Install WSX and choose a port
  2. Open a browser http://localhost:8888 (port defined above)
  3. The login and password that you need to use is your system login and password

To run WSX on a Linux host:

  1. Ensure that your Linux server has Python 2.6 installed!!!
  2. Install WSX and choose a port
  3. Launch the server by typing: sudo /etc/init.d/vmware-wsx-server start
  4. Open a browser http://localhost:8888 (port defined above)
  5. The login and password that you need to use is your system login and password

You can go to the configuration page and add additional hosts.

For more information about WSX you can read this blog post from the lead developer Christian Hammondhttp://blog.chipx86.com/.

Advertisements