A virtual machine (VM) is a 'completely isolated guest operating system installation within a normal host operating system'.^[1] Modern virtual machines are implemented with either software emulation or hardware virtualization or (in the most cases) both together.

• Download VirtualBox on your Mac machine, and then set it up with the necessary ISO image from Android-x86.org. You’ll be able to create an efficient emulator that allows you to play almost any game.
• Running Android on Mac using VirtualBox is best when you need better control over the process. As a virtual machine, you can customize performance too. However, in the long run, you will have to compromise overall performance and gaming controls. Check Out VirtualBox and Android x86 #3 Nox Player Mac — Best Optimized for Gaming.

Jun 18, 2018 Nox is a simple Android emulator to set up (download the installer, double-click it, drag the app icon into Applications and you're good to go), works fine on Mac, doesn't cost anything and has a. Jul 22, 2021 Download Android x86 virtual machine (VDI and VMDK) for VirtualBox and VMware. Run android inside your Windows, Linux, and Mac OS X. After installing Mac OS X Mojave on a virtual machine, straight away you will notice that you are not able to get a full resolution for Mac OS inside the virtual machine. Even though you toggle the VM to full screen. VMOS is an APP software based on Virtual Machine (VM). VMOS Virtual Machine With Root Android - Double System.

VM Definitions

A virtual machine (VM) is a software implementation of a machine (i.e. a computer) that executes programs like a physical machine. Virtual machines are separated into two major categories, based on their use and degree of correspondence to any real machine. A system virtual machine provides a complete system platform which supports the execution of a complete operating system (OS). In contrast, a process virtual machine is designed to run a single program, which means that it supports a single process. An essential characteristic of a virtual machine is that the software running inside is limited to the resources and abstractions provided by the virtual machine—it cannot break out of its virtual world.

A virtual machine was originally defined by Popek and Goldberg as 'an efficient, isolated duplicate of a real machine'. Current use includes virtual machines which have no direct correspondence to any real hardware.^[2]

System virtual machines

System virtual machines

• multiple OS environments can co-exist on the same computer, in strong isolation from each other
• the virtual machine can provide an instruction set architecture (ISA) that is somewhat different from that of the real machine
• application provisioning, maintenance, high availability and disaster recovery^[3]

The main disadvantages of VMs are:

• a virtual machine is less efficient than a real machine when it accesses the hardware indirectly
• when multiple VMs are concurrently running on the same physical host, each VM may exhibit a varying and unstable performance (Speed of Execution, and not results), which highly depends on the workload imposed on the system by other VMs, unless proper techniques are used for temporal isolation among virtual machines.

Multiple VMs each running their own operating system (called guest operating system) are frequently used in server consolidation, where different services that used to run on individual machines to avoid interference are instead run in separate VMs on the same physical machine.

The desire to run multiple operating systems was the original motivation for virtual machines, as it allowed time-sharing a single computer between several single-tasking Operation 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 CMS. Unlike virtual memory, a system virtual machine allowed the user to use privileged instructions in their code. This approach had certain advantages, for instance it allowed users to add input/output devices not allowed by the standard system.^[4]

The guest OSes do not have to be compliant with the hardware making it possible to run different OSes on the same computer (e.g., Microsoft Windows and Linux, or older versions of an OS to support software that has not yet been ported to the latest version). The use of virtual machines to support different guest OSes is becoming popular in embedded systems; a typical use is to support a real-time operating system at the same time as a high-level OS such as Linux or Windows.

Another use is to sandbox an OS that is not trusted, possibly because it is a system under development. Virtual machines have other advantages for OS development, including better debugging access and faster reboots.^[5]

Process virtual machines

A process VM, sometimes called an application virtual machine, 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 is achieved by the use of just-in-time compilation.

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, which serves as an abstraction layer for several interpreted languages, and the .NET Framework, which runs on a VM called the Common Language Runtime.

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 parallel 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 parallel machine.

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). Examples are PVM (Parallel Virtual Machine) and MPI (Message Passing Interface). They are not strictly virtual machines, as the applications running on top still have access to all OS services, and are therefore not confined to the system model provided by the 'VM'.

Techniques

Emulation of the underlying raw hardware (native execution)

This approach is described as full virtualization of the hardware, and can be implemented using a Type 1 or Type 2 hypervisor. (A Type 1 hypervisor runs directly on the hardware; a Type 2 hypervisor runs on another operating system, such as Linux). Each virtual machine can run any operating system supported by the underlying hardware. Users can thus run two or more different 'guest' operating systems simultaneously, in separate 'private' virtual computers.

The pioneer system using this concept was IBM's CP-40, the first (1967) version of IBM's CP/CMS (1967–1972) and the precursor to IBM's VM family (1972–present). With the VM architecture, most users run a relatively simple interactive computing single-user operating system, CMS, as a 'guest' on top of the VM control program (VM-CP). This approach kept the CMS design simple, as if it were running alone; the control program quietly provides multitasking and resource management services 'behind the scenes'. In addition to CMS, VM users can run any of the other IBM operating systems, such as MVS or z/OS. z/VM is the current version of VM, and is used to support hundreds or thousands of virtual machines on a given mainframe. Some installations use Linux for zSeries to run Web servers, where Linux runs as the operating system within many virtual machines.

Full virtualization is particularly helpful in operating system development, when experimental new code can be run at the same time as older, more stable, versions, each in a separate virtual machine. The process can even be recursive: IBM debugged new versions of its virtual machine operating system, VM, in a virtual machine running under an older version of VM, and even used this technique to simulate new hardware.^[6]

The standard x86 processor architecture as used in the modern PCs does not actually meet the Popek and Goldberg virtualization requirements. Notably, there is no execution mode where all sensitive machine instructions always trap, which would allow per-instruction virtualization.

Despite these limitations, several software packages have managed to provide virtualization on the x86 architecture, even though dynamic recompilation of privileged code, as first implemented by VMware, incurs some performance overhead as compared to a VM running on a natively virtualizable architecture such as the IBM System/370 or Motorola MC68020. By now, several other software packages such as Virtual PC, VirtualBox, Parallels Workstation and Virtual Iron manage to implement virtualization on x86 hardware.

Intel and AMD have introduced features to their x86 processors to enable virtualization in hardware.

As well as virtualization of the resources of a single machine, multiple independent nodes in a cluster can be combined and accessed as a single virtual NUMA machine ^[7].

Emulation of a non-native system

Virtual machines can also perform the role of an emulator, allowing software applications and operating systems written for another computer processor architecture to be run.

Some virtual machines emulate hardware that only exists as a detailed specification. For example:

• One of the first was the p-code machine specification, which allowed programmers to write Pascal programs that would run on any computer running virtual machine software that correctly implemented the specification.
• The specification of the Java virtual machine.
• The Common Language Infrastructure virtual machine at the heart of the Microsoft .NET initiative.
• Open Firmware allows plug-in hardware to include boot-time diagnostics, configuration code, and device drivers that will run on any kind of CPU.

This technique allows diverse computers to run any software written to that specification; only the virtual machine software itself must be written separately for each type of computer on which it runs.

Operating system-level virtualization

Operating system-level virtualization is a server virtualization technology which virtualizes servers on an operating system (kernel) layer. It can be thought of as partitioning: a single physical server is sliced into multiple small partitions (otherwise called virtual environments (VE), virtual private servers (VPS), guests, zones, etc.); each such partition looks and feels like a real server, from the point of view of its users.

For example, Solaris Zones supports multiple guest OSes running under the same OS (such as Solaris 10). All guest OSes have to use the same kernel level and cannot run as different OS versions. Solaris native Zones also requires that the host OS be a version of Solaris; other OSes from other manufacturers are not supported.^{[citation needed]},however you need to use Solaris Branded zones to use another OSes as zones.

Another example is System Workload Partitions (WPARs), introduced in the IBM AIX 6.1 operating system. System WPARs are software partitions running under one instance of the global AIX OS environment.

The operating system level architecture has low overhead that helps to maximize efficient use of server resources. The virtualization introduces only a negligible overhead and allows running hundreds of virtual private servers on a single physical server. In contrast, approaches such as full virtualization (like VMware) and paravirtualization (like Xen or UML) cannot achieve such level of density, due to overhead of running multiple kernels. From the other side, operating system-level virtualization does not allow running different operating systems (i.e. different kernels), although different libraries, distributions etc. are possible.

List of hardware with virtual machine support

• Alcatel-Lucent 3B20D/3B21D emulated on commercial off-the-shelf computers with 3B2OE or 3B21E system
• AMD-V (formerly code-named Pacifica)
• Boston Circuits gCore (grid-on-chip) with 16 ARC 750D cores and Time-machine hardware virtualization module.
• Freescale PowerPC MPC8572 and MPC8641D
• IBM System/370, System/390, and zSeries mainframes
• Intel VT-x (formerly code-named Vanderpool)
• Sun Microsystems sun4v (UltraSPARC T1 and T2) – utilized by Logical Domains

• HP vPAR and cell based nPAR
• GE Project MAC then
• Honeywell Multics systems
• Honeywell 200/2000 systems Liberator replacing IBM 14xx systems, Level 62/64/66 GCOS
• IBM System/360 Model 145 Hardware emulator for Honeywell 200/2000 systems
• RCA Spectra/70 Series emulated IBM System/360
• NAS CPUs emulated IBM and Amdahl machines
• Honeywell Level 6 minicomputers emulated predecessor 316/516/716 minis
• Xerox Sigma 6 CPUs were modified to emulate GE/Honeywell 600/6000 systems

List of virtual machine software

Extended descriptions of selected virtualization software

The following software products can virtualize hardware so that several operating systems can share it.

• Windows 2008 R2 Hyper-V provides x64 type 1 virtualization.
• Adeos is a hardware abstraction layer that can be loaded as a Kernel Module in Linux. It allows the loading of a real-time kernel as a module, at the same time as Linux but with higher priority.
• Denali uses paravirtualisation to provide high-performance virtual machines on x86 computers. Denali's virtual machines support specialised minimal OSs for Internet services. The system can scale to thousands of virtual machines. Denali does not preserve the application binary interface (ABI), and so applications must be recompiled to run within a library operating system; in this sense it is similar to the Exokernel.
• OKL4 from Open Kernel Labs is designed for use in embedded systems and is primarily deployed in mobile phones. It is the only commercial hypervisor employing capability-based security.
• OpenVZ provides operating system level server virtualization, built on Linux.
• Parallels virtualizes x86 to run unmodified PC operating systems, and uses a lightweight hypervisor technology to improve security and to increase the efficiency. Parallels has become popular for its ability to run Windows as a guest under Mac OS X on the Apple–Intel architecture.
• QEMU is a simulator based on a virtual machine, which gives it the ability to emulate a variety of guest CPU architectures on many different host platforms.
• Returnil Virtual System can virtualize Windows based systems, needs only a restart to rebuild the virtual machine.
• VirtualBox is an open source (GPL)/proprietary virtual machine developed by Sun Microsystems (originally developed by Innotek GmbH and now owned by Oracle Corporation). It allows virtualization of x86 and supports various host operating systems including Windows, Linux, BSD and Solaris. It also supports VMware, Parallels and Microsoft Virtual Machine Disk Formats.
• Virtual Iron provides virtual machines for x86 that run unmodified operating systems, such as Windows, Red Hat and SUSE; open source, implements native virtualization, which delivers near-native performance for x86 operating systems. Virtual Iron provides full OS compatibility for existing or new OSes with near-native performance without the performance trade-offs between paravirualization and binary translation.

• VMware provides virtual machines for x86 that can run unmodified PC operating systems. The technology involved in doing this is complex and also incurs (sometimes significant) performance overheads with hosted VMware products (VM Server and Workstation). ESX server provides near-native performance and a fully virtualized option (along with para-virtualization of some hardware components).
• Xen trades running of existing operating systems for running modified (paravirtualized) operating systems with improved performance. Xen Virtualization system's motivation differs from that of Denali in that it is intended to run a moderate number of full-featured operating systems, rather than a large number of specialised, lightweight ones.
• KVM is a Linux kernel module that enables a modified QEMU program to use hardware virtualization.
• libJIT Just-In-Time Compilation library is a library for development of advanced Just-in-time compilation (JIT) in Virtual Machine implementations, Dynamic programming languages, and Scripting languages. Currently it is used for Common Intermediate Language, Ruby, Java, Domain-specific programming languages.

See also

• Storage hypervisor
• ICL's VME operating system
• Amazon Machine Image
• Virtual backup appliance
• Virtual disk image

References

1. ^'Virtual Machines: Virtualization vs. Emulation'. http://www.griffincaprio.com/blog/2006/08/virtual-machines-virtualization-vs-emulation.html. Retrieved 2011-03-11.
2. ^Smith, James E.; Nair, Ravi (2005). 'The Architecture of Virtual Machines'. Computer (IEEE Computer Society) 38 (5): 32–38. doi:10.1109/MC.2005.173.
3. ^http://www.vmware.com/solutions/business-critical-apps/
4. ^ Smith and Nair, pp. 395–396
5. ^http://www.vmwarez.com/2006/05/super-fast-server-reboots-another.html
6. ^ See History of CP/CMS for IBM's use of virtual machines for operating system development and simulation of new hardware
7. ^ Matthew Chapman and Gernot Heiser. vNUMA: A virtual shared-memory multiprocessor. Proceedings of the 2009 USENIX Annual Technical Conference, San Diego, CA, USA, June, 2009 [1]

Further reading

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

External links

Wikimedia Foundation. 2010.

Look at other dictionaries:

• Virtual Machine — Machine virtuelle Pour les articles homonymes, voir VM. VirtualBox Le sens originel de machine virtuelle (ou Virtual Machine (VM) en anglais) e … Wikipédia en Français

• virtual machine — noun (computing) A cross platform environment for the consistent execution of a program or application • • • Main Entry: ↑virtual … Useful english dictionary

• Virtual Machine — Virtual Machine, virtuelle Maschine … Universal-Lexikon

• Virtual Machine — virtuelle Maschine in VirtualBox Eine virtuelle Maschine, kurz VM, ist ein virtueller Computer. Auf einem realen Computer können gleichzeitig mehrere virtuelle Maschinen betrieben werden. Virtuelle Maschinen werden als Betriebssystem ausgeführt,… … Deutsch Wikipedia

• virtual machine — An environment created by the operating system that gives each executing application the illusion that it has complete control of an independent computer and can access all the system resources that it needs. For example, the Intel 80386… … Dictionary of networking

• virtual machine — virtualioji mašina statusas T sritis automatika atitikmenys: angl. virtual machine vok. virtuelle Maschine, f rus. виртуальная машина, f pranc. ordinateur virtuel, m … Automatikos terminų žodynas

• virtual machine — virtualioji mašina statusas T sritis informatika apibrėžtis Hipotetinės mašinos (kompiuterio) programinis modelis. Žodis „mašina“ čia vartojamas istoriškai, nuo tų laikų, kai kompiuteriai buvo vadinami elektroninėmis skaičiavimo mašinomis.… … Enciklopedinis kompiuterijos žodynas

• virtual machine — ● ►en loc. f. ►EXEC Version anglaise de machine virtuelle … Dictionnaire d'informatique francophone

• virtual machine — noun a) A software emulation of a computer that runs in an isolated partition of a real computer. b) A computer system that is implemented in software rather than hardware and that runs bytecode … Wiktionary

• Virtual Machine — area of protected memory on which a program runs during multi tasking while working in protected mode, VM … English contemporary dictionary

To install and experience the Android x86 on PC you nee two things VirtualBox or Vmware software and Android x86 ISO image or Android x86 VM image.

Android, the most popular operating system, now not only just limited to your smartphones. If you have the curiosity to use it on your personal computer (PC) then you can do it. Now, the users those have a spare machine to test the Android operating system on PC can use the Android ISO image. You just need to make a bootable USB drive using the downloaded ISO images of Android 7.0, 8.0, 9.0 or whatever the version you want. However, if you don’t have the extra system to test the Android then another option which available is Virtualization. The most popular Virtualization software are VirtualBox and Vmware. The VirtualBox is an open source tool and available for Linux, Windows, and Mac. While the other one Vmware is also available for the OS mentioned but it is proprietary software.

You can either use the Android ISO image to install the Android OS on VirtualBox / VMware or simply download the pre-configured Android x86 Virtual machine image (VM). The benefit of using Virtual Image is, you don’t need to configure storage, Ram, other hardware configuration for the OS on Virtualization software. Just download the Android VM image and it simply boots as a preinstalled machine. It saves a lot of time.

Android Virtual Machine Mac

Prerequisites to install Android x86

To install and experience the Android on PC you nee two things VirtualBox or Vmware software and Android x86 ISO image or Android x86 VM image. Here in this tutorial, we are going to use the VirtualBox and to save time and make it easy to install the Android on PC, the Android x86 VM image.

Here are the Links to download the above-mentioned prerequisites software.

VirtualBox: Link

Android X86 VM image: Link( VM image available while writing the article are: Android-x86 8.1-RC2 Oreo, Nougat, Marshmallow (R3), 5.1 (RC1), Android x86 4.4 r1 and more)

Android x86 ISO image: Link(For those don’t want to use the Andriod VM image)

Install Android OS on VirtualBox and VMware

Note: It doesn’t matter which operating system you are using it could be Linux, Windows or Mac because the process of working with Virtual or Vmware is the same for all of them. While writing article Android OReo was the latest build.

Android Virtual Machine For Android

Step 1: Download VirtualBox or VMware player

First of all, download and install the VirtualBox on your PC machine ( Linux, Windows or Mac).

Step 2: Get Android Oreo OS VM image

After the installation of the Virtualbox, you need to download the VM image from the link given above given in this article. On the website, you will find two images one is for VirtualBox and other is meant for Vmware. According to your software select that. As we are using the VirtualBox, so we downloaded the VirtualBox image. While writing this the article the latest Android VM image available on the website was Android-x86 8.1-RC1 Oreo.

Step 3: Extract Android X86 VM image file

The downloaded the Android X86 VM image file will be in a 7z archive format. After downloading you need to extract the Android VM image from using the normal Winrar or 7zip or any other archive/ compression software.

Step 4: Run the VirtualBox.

1. Click on the NEW button from the VirtualBox menu.
2. Give some name to your Android virtual machine, like we have given Android test H2s.
3. From Type’s drop-down select the Other and Version = other/unknown.
4. Select the size of memory you want to provide your operating system. We have assigned 2GB for fluid functions.
5. From the Hard disk section, select the option- Use an existing virtual hard disk file.
6. Click on the Folder icon.

Step 5: Select the extracted Android X86 VDI image which you downloaded above.

Step 6: Click on the Create button.

Step 7: Select the created Android x86 Virtual machine from the left panel of VirtualBox.

Step 8: Now Click on the START button given on the VirtualBox menu.

Step 9: The Android Virtual Machine will start.

Step 10: Select the normal mode- Android X86 8.1-rc1

Step 11: Android x86 is installed

The OS has been installed and it will boot to provide you with a familiar screen like your smartphone.

We tried to install the PUBG on the Android x86 Virtual Machine on Linux PC and it worked…

Android Virtual Machine Download

Other Useful Resources: