Last update: 02.02.2024

PPA VM Instalation guide

General information

The number of virtual machines you can have is essentially constrained by the available hard drive space.

{width="6.267716535433071in" height="4.888888888888889in"}

Let\'s consider a case where you have only one virtual machine from Probe Point Analytics. However, you should be aware of the possibility that simultaneously running multiple VMs is feasible, yet your system resources will pose certain constraints. Each VM consumes CPU time, RAM, and other resources, thereby limiting your capacity.

Within the framework of this guide, we will not specifically discuss why and why you need a virtual machine. The reasons can be very different. From a secure sandbox for accepting potentially compromised files to the obligation to provide, upon request of the court, the working environment that was used as part of the investigation process.

A virtual environment offers a means to execute software from another operating system. For instance, if you\'re a Linux or Mac user, you could utilize a VM to install Windows and access Windows-specific applications. Similarly, if you need to run older applications compatible only with Windows XP while preferring a newer version like Windows 10, you can install Windows XP within a VM.

There exist several main options for virtual machine applications:

• VirtualBox (Windows, Linux, Mac OS X): Renowned for its open-source > nature and free availability, VirtualBox stands out as a popular > choice. Its lack of a paid version eliminates the usual pressures > of upgrading for additional features, making it particularly > attractive for Windows and Linux users due to lesser competition > in this domain.

• VMware Player (Windows, Linux): VMware offers its own suite of > virtual machine programs. VMware Player serves as a free, basic > tool for both Windows and Linux. Advanced functionalities, akin to > those found in VirtualBox, necessitate upgrading to the paid > VMware Workstation. While VirtualBox is recommended as an initial > choice, VMware Player could be explored if VirtualBox doesn\'t > meet expectations.

• VMware Fusion (Mac OS X): For Mac users, VMware Fusion is the > preferred option as VMware Player isn\'t available for Mac. > Although a purchase is required for VMware Fusion, it offers a > more refined user experience tailored for Mac environments.

• Parallels Desktop (Mac OS X): Parallels Desktop caters to Mac users > seeking virtualization solutions. Both Parallels Desktop and > VMware Fusion for Mac boasts superior polish compared to their > counterparts on other platforms, targeting average Mac users > interested in running Windows software seamlessly.

The most common of them is the first option from Oracle. Therefore, we will consider the installation procedure and first launch using this particular solution.

Prerequisites

Installation

Launch the previously installed virtual machine environment program. And click the \"New\" button:

{width="6.267716535433071in" height="1.8333333333333333in"}

You will be led through the setup process by a wizard that initially prompts you to specify the operating system you intend to install. Typically, if you enter the name of the OS in the \"Name\" field, the application will likely auto-select the appropriate type and version for that OS. If this doesn\'t occur, or if the selection is incorrect, you can manually choose the correct options from the dropdown menus. Once completed, proceed by clicking \"Next.\"

{width="6.267716535433071in" height="3.736111111111111in"}

The wizard will initially preselect default settings for you, although you can customize them across subsequent screens. One of the prompts will inquire about the amount of memory to allocate to the virtual machine (VM). If you desire an allocation different from the default, you can adjust it at this stage. Otherwise, simply proceed by clicking \"Next.\" Rest assured, you will have the flexibility to modify this value later should the need arise.

{width="6.267716535433071in" height="3.7083333333333335in"}

Additionally, the wizard will generate the virtual hard disk file intended for use by the VM. Unless you possess an existing virtual hard disk file that you wish to utilize, simply opt to create a new one when prompted.

{width="6.267716535433071in" height="3.736111111111111in"}

You\'ll also encounter a query regarding whether to create a dynamically allocated or fixed-size disk. Opting for a dynamically allocated disk entails setting a maximum disk size, with the file expanding only as needed up to that limit. Conversely, selecting a fixed-size disk involves specifying a size, resulting in the creation of a file of that exact size from the outset.

Also, It is important to note that the disk size includes the entire operating system along with the space occupied by system files and pre-installed programs.

Both solutions are suitable for their purposes and can be represented as a set of pros and cons:

• Fixed Virtual Machine Disk Size:

  • Pros:

    • Predictable Performance: Since the disk size is fixed from > the outset, there are no fluctuations in disk space > allocation, which can lead to more consistent performance.

    • Immediate Space Reservation: The entire disk space is > allocated upfront, ensuring that the full capacity is > immediately available for use.

    • Prevents Fragmentation: Fixed-size disks generally > experience less fragmentation compared to dynamically > allocated ones since the space is already allocated > contiguously.

    • Security: Once allocated, the disk size cannot be modified, > providing a level of security against accidental or > unauthorized changes.

  • Cons:

    • Higher Initial Resource Consumption: Fixed-size disks occupy > their entire allocated space immediately upon creation, > potentially consuming more resources initially.

    • Wastage of Resources: If the allocated disk space is not > fully utilized, there may be wasted resources as the > allocated space cannot be reduced.

    • Lack of Flexibility: The fixed size cannot be adjusted > easily after creation, limiting flexibility in > accommodating changing storage requirements.

    • Greater Storage Overhead: Since the entire disk space is > reserved upfront, there may be wasted space if the VM does > not utilize the full capacity.

<!-- -->

• Dynamic Virtual Machine Disk Size:

  • Pros:

    • Resource Efficiency: Dynamically allocated disks consume > only the space required by the virtual machine, optimizing > resource utilization.

    • Flexibility: The disk size expands dynamically as the VM > requires more space, providing flexibility to adapt to > changing storage needs.

    • Space Conservation: Dynamic allocation minimizes wasted > space by allocating storage only as needed, which can be > particularly advantageous for VMs with varying storage > demands. Reduced Initial

    • Resource Consumption: Dynamic disks initially occupy minimal > space, conserving resources until additional storage is > required.

  • Cons:

    • Performance Overhead: Dynamic resizing of disk space can > introduce a performance overhead, particularly during > periods of heavy disk activity.

    • Fragmentation: As the disk expands dynamically, it may lead > to increased fragmentation, potentially impacting > performance over time.

    • Unpredictable Storage Growth: The dynamic allocation of disk > space can make it challenging to predict storage growth > accurately, potentially leading to unexpected capacity > issues. Potential for

    • Resource Contention: In environments with high disk I/O > activity, dynamically expanding disks may encounter > contention for resources, affecting overall VM > performance.

In summary, the choice between fixed and dynamic virtual machine disk sizes involves balancing factors such as performance, resource utilization, flexibility, and storage efficiency based on the specific requirements and constraints of your virtualization environment. It is important to note that when running a virtual machine on a VPS, it is better to use a fixed disk size. Whereas, if you intend to constantly work with media files in a sandbox format, then it is better to use the dynamic option. If you do not know or the range of tasks is not defined in advance, we advise you to enable the fixed option with a disk size of approximately 15GB.

Subsequently, you\'ll find yourself back in the main VM application window, where your newly created VM should be visible. Ensure that the installation media required is accessible to the VM, typically achieved by specifying an ISO file or a physical disc through the VM\'s settings. To commence operation of your new VM, simply select it and click \"Start.\"