Os Server Vm For Mac Client



47 comments
  1. Vmware For Mac

I am a running a server based application on windows XP running under Parallels build 5582. I can connect to the application from the Mac (running Leopard 10.5.1) using Shared networking, everything operates as it should (meaning I can send requests and receive responses from the server app running on windows). N View Client for Mac OS X 1.4 and 1.5: Mac OS X Snow Leopard (10.6.8) and Mac OS X Lion (10.7) View Connection Server, Security Server, and View Agent Latest maintenance release of VMware View 4.6.x and later releases. VMware View Client with PCoIP for Mac OS X 16 December, 2011 Gabrie van Zanten Today VMware released their Technical Preview of the VMware View PCoIP client for OSX.

Ok, you read the title of this post, and you’re thinking “hey, this guy must be goin’ cuckoo for coco puffs.” No, this is FOR REAL. Here’s the deal: with the help of some people I met this week (Micheal Bell and the rest of the students from my VI3 Fast Track class in Irvine), I figured out how to run the vSphere Client on my Mac OS X. This is something that I’ve wanted to get up and running for a long time, ever since I converted from the Church of Gates and bowed down to the one true computer deity – the all enlightened Steve Jobs. That’s right folks…I’ve just plucked a bright shiny Apple from the Tree of Virtual Knowledge.

Let’s face it. All of us that use Macs would really love to have a native vSphere Client from VMware, but this is something that I don’t think they are going to focus on very much, at least in the near future. Up until now, If you wanted to run the vSphere Client on Mac OS X, you could go about implementing that via VMware Fusion by running a VM in Unity mode. If you didn’t know about Unity view, it removes or hides the VM from the screen and simply displays the applications that are running in the VM. That’s great and all – and I personally love VMware Fusion and think it’s a freaking awesome product – but I always thought it would be so much better to just have a client on Mac OS X that didn’t require me to load a VM just to get access to it.

Well, as the Beatles said, “I get by with a little help from my friends.” The other day, we finally figured out a way to get access to the vSphere Client on Mac OS X. Because this solution has only been done in a select few environments, it work for some but not others… so don’t hate! So far this has worked for me at my office and while connected remotely to my environments via VPN.

The way I got it to work was by using a few open source components and by installing a few extra bits of software on my Mac. I have to say that I didn’t really invent the wheel here. All I did was use X11, MacPorts, rdesktop, and Seamlessrdp to create a remote terminal session to a Windows Server 2003 R2 VM running in a remote VMware Fusion VM and also another one hosted on an ESX Server in my lab. Here is a step by step walkthrough detailing what I did and how I got everything flowing:

  • Install X11 on your Mac’s, you can find that on your Mac OS X DVD or it can even be downloaded from the web.
  • Go to the MacPorts site and download the version of the tools that matches your Mac. MacPorts also known as DarwinPorts is a free/open source package management system that simplifies the installation of software on the Mac OS X and Darwin operating systems.
  • After installing the MacPorts packages, open a terminal and run the ports update command to update the application to the latest and greatest version: sudo /opt/local/bin/port -v selfupdate
  • Install the rdesktop client with MacPorts by typing the following command in the Terminal: sudo /opt/local/bin/port install rdesktop
  • After the application is installed, confirm that you have the latest version of rdesktop by typing: /opt/local/bin/rdesktop scroll to the top of the Terminal windows and see that you have rdesktop version 1.6.0.
  • On the Windows Server 2003 VM, configure a user account that has permissions to access the vSphere environment. This could be a local system or Active Directory based account.
  • Configure the Windows Server 2003 R2 to allow remote desktop connections, and make sure to add the users that will be allow to connect to that system via RDP.
  • Install the vSphere Client on the Wndows Server 2003 R2 server
  • Modify the Windows Path Environment Variable and add the path of the directory where the vSphere Client executable file is located, the default path is always: C:Program FilesVMwareInfrastructureVirtual Infrastructure ClientLauncher make sure to put a semi-colon ; at the end of the path currently listed in the variable value field.
Vmware
Environment Variables
  • Download the seamlessrdp application and extract it to the root of the system drive called seamlessrdp
  • Test the connection to the Windows Server 2003 by opening a session from the Mac by typing the following command in the Terminal window: /opt/local/bin/rdesktop <ip or FQDN> A remote desktop windows should appear if everything is working correctly and you can connect to the system on the network.
  • Once the connection to the system works, test the seamlessrdp connection to the vSphere Client from the Mac by typing the following command on the Terminal window: /opt/local/bin/rdesktop -A -s “c:seamlessrdpseamlessrdpshell.exe VpxClient” -u username -p password -a 16 FQDN or IP

syntax breakdown:

  • -A = Start application in seamless mode
  • -s = Specifies the path to the location of the Seamless files
  • -u = Username
  • -p = Password
  • -a = Color bits (8, 16, or 32)

After the connection is made to the client, the capability to connect CD-ROM, Floppies is not available because it’s an obvious remote connection.

You can now launch the application from the terminal everytime or you can setup an icon for it so you can keep it in the dock.

Setting up Icon To Launch vSphere Client application:

  • Use a text editor and open a new document
  • Make sure is set to a plain text format
  • type the command used to connect to the Windows Server 2003
  • Save the file as vSphereClient and use the .command extension. Go to the location where the file is saved and use the Get Info and select to hide the extension on that file. This way you dont have to see that .command on the file and it looks like a regular icon in the dock.
  • Make the file executable by opening the Terminal application and entering the following command: sudo chmod 777 /path/to/vSphereClient.command file
  • You can now change the icon of the file to something you like or something that identifies with VMware.

This worked great with Windows Server 2003 R2 as the target server that I used to host the vSphere client, but when I tried the same steps listed on a Windows Server 2008 they didn’t work. I was able to open a remote desktop session to the VM but the session was a bif window and it didnt opent he application at all. So If any one with skills on UNIX, Linux, OS X can get this to work with Windows Server 2008 please let me know. Get ready to bite your chompers into that apple!

vSphere Client on Mac OS X Demo

Mac
Program execution
General concepts
  • Translation
    • Compiler
  • Intermediate representation (IR)
  • Execution
    • Runtime system
Types of code
Compilation strategies
  • Just-in-time (JIT)
  • Ahead-of-time (AOT)
Notable runtimes
  • Android Runtime (ART)
  • Common Language Runtime (CLR) & Mono
  • Java virtual machine (JVM)
  • V8
Notable compilers & toolchains
  • GNU Compiler Collection (GCC)
  • LLVM

In computing, a virtual machine (VM) is an emulation of a computer system. Virtual machines are based on computer architectures and provide functionality of a physical computer. Their implementations may involve specialized hardware, software, or a combination.

There are different kinds of virtual machines, each with different functions:

  • System virtual machines (also termed full virtualization VMs) provide a substitute for a real machine. They provide functionality needed to execute entire operating systems. A hypervisor uses native execution to share and manage hardware, allowing for multiple environments which are isolated from one another, yet exist on the same physical machine. Modern hypervisors use hardware-assisted virtualization, virtualization-specific hardware, primarily from the host CPUs.
  • Process virtual machines are designed to execute computer programs in a platform-independent environment.

Some virtual machines, such as QEMU, are designed to also emulate different architectures and allow execution of software applications and operating systems written for another CPU or architecture. Operating-system-level virtualization allows the resources of a computer to be partitioned via the kernel. The terms are not universally interchangeable.

  • 1Definitions
  • 3Full virtualization

Definitions[edit]

A 'virtual machine' was originally defined by Popek and Goldberg as 'an efficient, isolated duplicate of a real computer machine.'[1] Current use includes virtual machines that have no direct correspondence to any real hardware.[2]The physical, 'real-world' hardware running the VM is generally referred to as the 'host', and the virtual machine emulated on that machine is generally referred to as the 'guest'. A host can emulate several guests, each of which can emulate different operating systems and hardware platforms.

System virtual machines[edit]

The desire to run multiple operating systems was the initial motive for virtual machines, so as to allow time-sharing among several single-tasking operating systems. In some respects, a system virtual machine can be considered a generalization of the concept of virtual memory that historically preceded it. IBM's CP/CMS, the first systems to allow full virtualization, implemented time sharing by providing each user with a single-user operating system, the Conversational Monitor System (CMS). Unlike virtual memory, a system virtual machine entitled the user to write privileged instructions in their code. This approach had certain advantages, such as adding input/output devices not allowed by the standard system.[2]

As technology evolves virtual memory for purposes of virtualization, new systems of memory overcommitment may be applied to manage memory sharing among multiple virtual machines on one computer operating system. It may be possible to share memory pages that have identical contents among multiple virtual machines that run on the same physical machine, what may result in mapping them to the same physical page by a technique termed kernel same-page merging (KSM). This is especially useful for read-only pages, such as those holding code segments, which is the case for multiple virtual machines running the same or similar software, software libraries, web servers, middleware components, etc. The guest operating systems do not need to be compliant with the host hardware, thus making it possible to run different operating systems on the same computer (e.g., Windows, Linux, or prior versions of an operating system) to support future software.[3]

The use of virtual machines to support separate guest operating systems is popular in regard to embedded systems. A typical use would be to run a real-time operating system simultaneously with a preferred complex operating system, such as Linux or Windows. Another use would be for novel and unproven software still in the developmental stage, so it runs inside a sandbox. Virtual machines have other advantages for operating system development and may include improved debugging access and faster reboots.[4]

Multiple VMs running their own guest operating system are frequently engaged for server consolidation.[5]

Process virtual machines[edit]

Vmware For Mac

A process VM, sometimes called an application virtual machine, or Managed Runtime Environment (MRE), runs as a normal application inside a host OS and supports a single process. It is created when that process is started and destroyed when it exits. Its purpose is to provide a platform-independent programming environment that abstracts away details of the underlying hardware or operating system and allows a program to execute in the same way on any platform.

A process VM provides a high-level abstraction – that of a high-level programming language (compared to the low-level ISA abstraction of the system VM). Process VMs are implemented using an interpreter; performance comparable to compiled programming languages can be achieved by the use of just-in-time compilation.[citation needed]

This type of VM has become popular with the Java programming language, which is implemented using the Java virtual machine. Other examples include the Parrot virtual machine and the .NET Framework, which runs on a VM called the Common Language Runtime. All of them can serve as an abstraction layer for any computer language.

A special case of process VMs are systems that abstract over the communication mechanisms of a (potentially heterogeneous) computer cluster. Such a VM does not consist of a single process, but one process per physical machine in the cluster. They are designed to ease the task of programming concurrent applications by letting the programmer focus on algorithms rather than the communication mechanisms provided by the interconnect and the OS. They do not hide the fact that communication takes place, and as such do not attempt to present the cluster as a single machine.[citation needed]

Unlike other process VMs, these systems do not provide a specific programming language, but are embedded in an existing language; typically such a system provides bindings for several languages (e.g., C and Fortran).[citation needed] Examples are Parallel Virtual Machine (PVM) and Message Passing Interface (MPI). They are not strictly virtual machines because the applications running on top still have access to all OS services and are therefore not confined to the system model.

History[edit]

Both system virtual machines and process virtual machines date to the 1960s and continue to be areas of active development.

System virtual machines grew out of time-sharing, as notably implemented in the Compatible Time-Sharing System (CTSS). Time-sharing allowed multiple users to use a computer concurrently: each program appeared to have full access to the machine, but only one program was executed at the time, with the system switching between programs in time slices, saving and restoring state each time. This evolved into virtual machines, notably via IBM's research systems: the M44/44X, which used partial virtualization, and the CP-40 and SIMMON, which used full virtualization, and were early examples of hypervisors. The first widely available virtual machine architecture was the CP-67/CMS (see History of CP/CMS for details). An important distinction was between using multiple virtual machines on one host system for time-sharing, as in M44/44X and CP-40, and using one virtual machine on a host system for prototyping, as in SIMMON. Emulators, with hardware emulation of earlier systems for compatibility, date back to the IBM System/360 in 1963,[6][7] while the software emulation (then-called 'simulation') predates it.

Process virtual machines arose originally as abstract platforms for an intermediate language used as the intermediate representation of a program by a compiler; early examples date to around 1966. An early 1966 example was the O-code machine, a virtual machine that executes O-code (object code) emitted by the front end of the BCPL compiler. This abstraction allowed the compiler to be easily ported to a new architecture by implementing a new back end that took the existing O-code and compiled it to machine code for the underlying physical machine. The Euler language used a similar design, with the intermediate language named P (portable).[8] This was popularized around 1970 by Pascal, notably in the Pascal-P system (1973) and Pascal-S compiler (1975), in which it was termed p-code and the resulting machine as a p-code machine. This has been influential, and virtual machines in this sense have been often generally called p-code machines. In addition to being an intermediate language, Pascal p-code was also executed directly by an interpreter implementing the virtual machine, notably in UCSD Pascal (1978); this influenced later interpreters, notably the Java virtual machine (JVM). Another early example was SNOBOL4 (1967), which was written in the SNOBOL Implementation Language (SIL), an assembly language for a virtual machine, which was then targeted to physical machines by transpiling to their native assembler via a macro assembler.[9] Macros have since fallen out of favor, however, so this approach has been less influential. Process virtual machines were a popular approach to implementing early microcomputer software, including Tiny BASIC and adventure games, from one-off implementations such as Pyramid 2000 to a general-purpose engine like Infocom's z-machine, which Graham Nelson argues is 'possibly the most portable virtual machine ever created'.[10]

Significant advances occurred in the implementation of Smalltalk-80,[11]particularly the Deutsch/Schiffmann implementation[12]which pushed just-in-time (JIT) compilation forward as an implementation approach that uses process virtual machine.[13]Later notable Smalltalk VMs were VisualWorks, the Squeak Virtual Machine,[14]and Strongtalk.[15]A related language that produced a lot of virtual machine innovation was the Self programming language,[16] which pioneered adaptive optimization[17] and generational garbage collection. These techniques proved commercially successful in 1999 in the HotSpot Java virtual machine.[18]Other innovations include having a register-based virtual machine, to better match the underlying hardware, rather than a stack-based virtual machine, which is a closer match for the programming language; in 1995, this was pioneered by the Dis virtual machine for the Limbo language. OpenJ9 is an alternative for HotSpot JVM in OpenJDK and is an open source eclipse project claiming better startup and less resource consumption compared to HotSpot.

Full virtualization[edit]

Logical diagram of full virtualization

In full virtualization, the virtual machine simulates enough hardware to allow an unmodified 'guest' OS (one designed for the same instruction set) to be run in isolation. This approach was pioneered in 1966 with the IBM CP-40 and CP-67, predecessors of the VM family.

Examples outside the mainframe field include Parallels Workstation, Parallels Desktop for Mac, VirtualBox, Virtual Iron, Oracle VM, Virtual PC, Virtual Server, Hyper-V, VMware Workstation, VMware Server (discontinued, formerly called GSX Server), VMware ESXi, QEMU, Adeos, Mac-on-Linux, Win4BSD, Win4Lin Pro, and Egenera vBlade technology.

Hardware-assisted virtualization[edit]

In hardware-assisted virtualization, the hardware provides architectural support that facilitates building a virtual machine monitor and allows guest OSes to be run in isolation.[19]Hardware-assisted virtualization was first introduced on the IBM System/370 in 1972,[citation needed] for use with VM/370, the first virtual machine operating system offered by IBM as an official product.

In 2005 and 2006, Intel and AMD provided additional hardware to support virtualization. Sun Microsystems (now Oracle Corporation) added similar features in their UltraSPARC T-Series processors in 2005. Examples of virtualization platforms adapted to such hardware include KVM, VMware Workstation, VMware Fusion, Hyper-V, Windows Virtual PC, Xen, Parallels Desktop for Mac, Oracle VM Server for SPARC, VirtualBox and Parallels Workstation.

In 2006, first-generation 32- and 64-bit x86 hardware support was found to rarely offer performance advantages over software virtualization.[20]

Operating-system-level virtualization[edit]

In operating-system-level virtualization, a physical server is virtualized at the operating system level, enabling multiple isolated and secure virtualized servers to run on a single physical server. The 'guest' operating system environments share the same running instance of the operating system as the host system. Thus, the same operating system kernel is also used to implement the 'guest' environments, and applications running in a given 'guest' environment view it as a stand-alone system. The pioneer implementation was FreeBSD jails; other examples include Docker, Solaris Containers, OpenVZ, Linux-VServer, LXC, AIX Workload Partitions, Parallels Virtuozzo Containers, and iCore Virtual Accounts.

See also[edit]

  • Virtual DOS machine (VDM)

References[edit]

  1. ^Popek, Gerald J.; Goldberg, Robert P. (1974). 'Formal requirements for virtualizable third generation architectures'(PDF). Communications of the ACM. 17 (7): 412–421. doi:10.1145/361011.361073.
  2. ^ abSmith, James E.; Nair, Ravi (2005). 'The Architecture of Virtual Machines'. Computer. 38 (5): 32–38, 395–396. doi:10.1109/MC.2005.173.
  3. ^Oliphant, Patrick. 'Virtual Machines'. VirtualComputing. Archived from the original on 2016-07-29. Retrieved 2015-09-23. Some people use that capability to set up a separate virtual machine running Windows on a Mac, giving them access to the full range of applications available for both platforms.Cite uses deprecated parameter |dead-url= (help); Cite web requires |website= (help)
  4. ^'Super Fast Server Reboots – Another reason Virtualization rocks'. vmwarez.com. 2006-05-09. Archived from the original on 2006-06-14. Retrieved 2013-06-14.Cite uses deprecated parameter |dead-url= (help)
  5. ^'Server Consolidation and Containment With Virtual Infrastructure'(PDF). VMware. 2007. Archived(PDF) from the original on 2013-12-28. Retrieved 2015-09-29.Cite uses deprecated parameter |dead-url= (help); Cite web requires |website= (help)
  6. ^Pugh, Emerson W. (1995). Building IBM: Shaping an Industry and Its Technology. MIT. p. 274. ISBN978-0-262-16147-3.
  7. ^Pugh, Emerson W.; et al. (1991). IBM's 360 and Early 370 Systems. MIT. pp. 160–161. ISBN978-0-262-16123-7.
  8. ^Wirth, Niklaus Emil; Weber, Helmut (1966). EULER: a generalization of ALGOL, and its formal definition: Part II, Communications of the Association for Computing Machinery. 9. New York: ACM. pp. 89–99.
  9. ^Griswold, Ralph E.The Macro Implementation of SNOBOL4. San Francisco, CA: W. H. Freeman and Company, 1972 (ISBN0-7167-0447-1), Chapter 1.
  10. ^Nelson, Graham A.'About Interpreters'. Inform website. Archived from the original on 2009-12-03. Retrieved 2009-11-07.Cite uses deprecated parameter |dead-url= (help)
  11. ^Goldberg, Adele; Robson, David (1983). Smalltalk-80: The Language and its Implementation. Addison-Wesley Series in Computer Science. Addison-Wesley. ISBN978-0-201-11371-6.
  12. ^Deutsch, L. Peter; Schiffman, Allan M. (1984). 'Efficient implementation of the Smalltalk-80 system'. POPL. Salt Lake City, Utah: ACM. doi:10.1145/800017.800542. ISBN0-89791-125-3.
  13. ^Aycock, John (2003). 'A brief history of just-in-time'. ACM Comput. Surv.35 (2): 97–113. doi:10.1145/857076.857077.
  14. ^Ingalls, Jr., Daniel 'Dan' Henry Holmes; Kaehler, Ted; Maloney, John; Wallace, Scott; Kay, Alan Curtis (1997). 'Back to the future: the story of Squeak, a practical Smalltalk written in itself'. OOPSLA '97: Proceedings of the 12th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications. New York, NY, USA: ACM Press. pp. 318–326. doi:10.1145/263698.263754. ISBN0-89791-908-4.
  15. ^Bracha, Gilad; Griswold, David (1993). 'Strongtalk: Typechecking Smalltalk in a Production Environment'. Proceedings of the Eighth Annual Conference on Object-oriented Programming Systems, Languages, and Applications. OOPSLA '93. New York, NY, USA: ACM. pp. 215–230. doi:10.1145/165854.165893. ISBN978-0-89791-587-8.
  16. ^Ungar, David Michael; Smith, Randall B. (December 1987). 'Self: The power of simplicity'. ACM SIGPLAN Notices. 22 (12): 227–242. doi:10.1145/38807.38828. ISSN0362-1340.
  17. ^Hölzle, Urs; Ungar, David Michael (1994). 'Optimizing dynamically-dispatched calls with run-time type feedback'. PLDI. Orlando, Florida, United States: ACM. pp. 326–336. doi:10.1145/178243.178478. ISBN0-89791-662-X.
  18. ^Paleczny, Michael; Vick, Christopher; Click, Cliff (2001). 'The Java HotSpot server compiler'. Proceedings of the Java Virtual Machine Research and Technology Symposium on Java Virtual Machine Research and Technology Symposium. 1. Monterey, California: USENIX Association.
  19. ^Uhlig, Rich; Neiger, Gil; Rodgers, Dion; Santoni, Amy L.; Martins, Fernando C. M.; Anderson, Andrew V.; Bennett, Steven M.; Kägi, Alain; Leung, Felix H.; Smith, Larry (May 2005). 'Intel virtualization technology'. Computer. 38 (5): 48–56. doi:10.1109/MC.2005.163.
  20. ^Adams, Keith; Agesen, Ole (2006-10-21). A Comparison of Software and Hardware Techniques for x86 Virtualization(PDF). ASPLOS’06 21–25 October 2006. San Jose, California, USA. Archived(PDF) from the original on 2010-08-20. Surprisingly, we find that the first-generation hardware support rarely offers performance advantages over existing software techniques. We ascribe this situation to high VMM/guest transition costs and a rigid programming model that leaves little room for software flexibility in managing either the frequency or cost of these transitions.Cite uses deprecated parameter |dead-url= (help)

Further reading[edit]

  • James E. Smith, Ravi Nair, Virtual Machines: Versatile Platforms For Systems And Processes, Morgan Kaufmann, May 2005, ISBN1-55860-910-5, 656 pages (covers both process and system virtual machines)
  • Craig, Iain D. Virtual Machines. Springer, 2006, ISBN1-85233-969-1, 269 pages (covers only process virtual machines)

External links[edit]

  • Mendel Rosenblum (2004-08-31). 'The Reincarnation of Virtual Machines'. ACM Queue. Vol. 2 no. 5.