It can run everywhere from small embedded systems or desktop class machines all the way up to datacenter deployments and even Cloud environments. The following screenshot shows how Oracle VM VirtualBox, installed on an Apple Mac OS X computer, is running Windows Server in a virtual machine window. (High Sierra) (Mojave) Parallels Desktop® 11 for Mac: Recommended-Level Configuration; Host Operating System: macOS (“High Sierra”) or newer: Memory: 16 GB: CPU Type: GHz quad-core Intel® Core i7™ or newer: Virtualization Software: Parallels Desktop® 15 for Mac or newer: Virtual Machine Operating System¹: bit Microsoft Windows 10 Microsoft. Latest breaking news, including politics, crime and celebrity. Find stories, updates and expert opinion.
 
 

Parallels Desktop for Mac Free Download – All Mac World

Models created in previous versions of Revit software products may require more available memory for the one-time upgrade process. NET Framework.

NET Framework Version 4. Browser Microsoft Internet Explorer 10 or higher Connectivity Internet connection for license registration and prerequisite component download Return to Top Revit Cloud Worksharing Disk Space Three times 3X the total disk space consumed by equivalent RVT files for all cloud workshared projects accessed by the user. Minimum Value Performance Connectivity Internet connection able to deliver symmetrical 5 Mbps connection for each machine on burst transfers.

Internet connection able to deliver symmetrical 10 Mbps connection for each machine on burst transfers. Internet connection able to deliver symmetrical 25 Mbps connection for each machine on burst transfers. Each client computer should have either the full Citrix or web client plug-in installed.

Users should use their domain logins to access both the Citrix web console and the LAN. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. All rights reserved. Four slots attached to the traditional IDE controller, which are always present.

Up to slots attached to the virtio-scsi controller, if enabled and supported by the guest OS. Given this large choice of storage controllers, you may not know which one to choose. In general, you should avoid IDE unless it is the only controller supported by your guest. The variety of controllers is only supplied by Oracle VM VirtualBox for compatibility with existing hardware and other hypervisors.

Disk image files reside on the host system and are seen by the guest systems as hard disks of a certain geometry. Like a physical disk, a virtual disk has a size, or capacity, which must be specified when the image file is created. As opposed to a physical disk however, Oracle VM VirtualBox enables you to expand an image file after creation, even if it has data already. See Section 8. This format is used when you create a new virtual machine with a new disk. Image files of Parallels version 2 HDD format are also supported.

Due to lack of documentation of the format, newer versions such as 3 and 4 are not supported. You can however convert such image files to version 2 format using tools provided by Parallels. Irrespective of the disk capacity and format, as mentioned in Section 1. If you create a fixed-size image, an image file will be created on your host system which has roughly the same size as the virtual disk’s capacity.

So, for a 10 GB disk, you will have a 10 GB file. Note that the creation of a fixed-size image can take a long time depending on the size of the image and the write performance of your hard disk. Dynamically allocated. For more flexible storage management, use a dynamically allocated image. This will initially be very small and not occupy any space for unused virtual disk sectors, but will grow every time a disk sector is written to for the first time, until the drive reaches the maximum capacity chosen when the drive was created.

While this format takes less space initially, the fact that Oracle VM VirtualBox needs to expand the image file consumes additional computing resources, so until the disk file size has stabilized, write operations may be slower than with fixed size disks.

However, after a time the rate of growth will slow and the average penalty for write operations will be negligible. These are often referred to as known media and come from two sources:.

The known media can be viewed and changed using the Virtual Media Manager , which you can access from the File menu in the VirtualBox Manager window. The known media are conveniently grouped in separate tabs for the supported formats. These formats are:. For each image, the Virtual Media Manager shows you the full path of the image file and other information, such as the virtual machine the image is currently attached to.

For virtual hard disks, the Create Virtual Hard Disk wizard is shown. This enables you to create a virtual ISO from selected files on the host. For floppy disks, the Floppy Disk Creator screen is shown. Copy an image to create another one. Move an image to another location. If you use a file management feature of the host OS to move a disk image to a new location, run the VBoxManage modifymedium –setlocation command to configure the new path of the disk image on the host file system.

Remove an image from the known media. You can optionally delete the image file when removing the image. Release an image to detach it from a VM. This action only applies if the image is currently attached to a VM as a virtual hard disk. Search for an image by name or UUID. View and edit the Properties of a disk image. Type: Specifies the snapshot behavior of the disk. See Section 5. Location: Specifies the location of the disk image file on the host system. You can use a file dialog to browse for the disk image location.

Description: Specifies a short description of the disk image. Size: Specifies the size of the disk image. You can use the slider to increase or decrease the disk image size. Information: Specifies detailed information about the disk image. Refresh the property values of the selected disk image.

To perform these actions, highlight the medium in the Virtual Media Manager and then do one of the following:. Use the Storage page in a VM’s Settings dialog to create a new disk image. By default, disk images are stored in the VM’s folder. You can copy hard disk image files to other host systems and then import them in to VMs from the host system. However, some Windows guest OSes may require that you configure the new VM in a similar way to the old one.

Do not simply make copies of virtual disk images. See Section 1. For each virtual disk image supported by Oracle VM VirtualBox, you can determine separately how it should be affected by write operations from a virtual machine and snapshot operations. By default, images are in normal mode. To mark an existing image with one of the non-standard modes listed below, use VBoxManage modifymedium. Alternatively, use VBoxManage storageattach to attach the image to a VM and specify the –mtype argument.

Normal images have no restrictions on how guests can read from and write to the disk. This is the default image mode. When you take a snapshot of your virtual machine as described in Section 1. The image file itself is not reset. Instead, when a snapshot is taken, Oracle VM VirtualBox freezes the image file and no longer writes to it.

For the write operations from the VM, a second, differencing image file is created which receives only the changes to the original image. While you can attach the same normal image to more than one virtual machine, only one of these virtual machines attached to the same image file can be executed simultaneously, as otherwise there would be conflicts if several machines write to the same image file.

Write-through hard disks are completely unaffected by snapshots. Their state is not saved when a snapshot is taken, and not restored when a snapshot is restored. Shareable hard disks are a variant of write-through hard disks. In principle they behave exactly the same. The difference only shows if you attach such disks to several VMs. Shareable disks may be attached to several VMs which may run concurrently.

This makes them suitable for use by cluster filesystems between VMs and similar applications which are explicitly prepared to access a disk concurrently. Only fixed size images can be used in this way, and dynamically allocated images are rejected. This is an expert feature, and misuse can lead to data loss, as regular filesystems are not prepared to handle simultaneous changes by several parties.

Immutable images only remember write accesses temporarily while the virtual machine is running. All changes are lost when the virtual machine is powered on the next time. As a result, as opposed to Normal images, the same immutable image can be used with several virtual machines without restrictions. Creating an immutable image makes little sense since it would be initially empty and lose its contents with every machine restart. You would have a disk that is always unformatted when the machine starts up.

Instead, you can first create a normal image and then later mark it as immutable when you decide that the contents are useful. If you take a snapshot of a machine with immutable images, then on every machine power-up, those images are reset to the state of the last current snapshot, instead of the state of the original immutable image. As a special exception, immutable images are not reset if they are attached to a machine in a saved state or whose last snapshot was taken while the machine was running.

This is called an online snapshot. As a result, if the machine’s current snapshot is an online snapshot, its immutable images behave exactly like the a normal image. To reenable the automatic resetting of such images, delete the current snapshot of the machine. Oracle VM VirtualBox never writes to an immutable image directly at all.

All write operations from the machine are directed to a differencing image. The next time the VM is powered on, the differencing image is reset so that every time the VM starts, its immutable images have exactly the same content. The differencing image is only reset when the machine is powered on from within Oracle VM VirtualBox, not when you reboot by requesting a reboot from within the machine.

This is also why immutable images behave as described above when snapshots are also present, which use differencing images as well. If the automatic discarding of the differencing image on VM startup does not fit your needs, you can turn it off using the autoreset parameter of VBoxManage modifymedium.

Multiattach mode images can be attached to more than one virtual machine at the same time, even if these machines are running simultaneously. For each virtual machine to which such an image is attached, a differencing image is created. As a result, data that is written to such a virtual disk by one machine is not seen by the other machines to which the image is attached. Each machine creates its own write history of the multiattach image.

Technically, a multiattach image behaves identically to an immutable image except the differencing image is not reset every time the machine starts. Parallels Desktop for Mac is able to virtualize a full set of standard PC hardware, including [5]. Version 2. This version also allowed users to boot their existing Boot Camp Windows XP partitions, which eliminated the need to have multiple Windows installations on their Mac. Additionally, the lawsuit claimed that Parallels Desktop 2.

Version 3. Support for DirectX 8. Parallels Explorer was introduced, which allows the user to browse their Windows system files in Mac OS X without actually launching Windows.

A new snapshot feature was included, allowing one to restore their virtual machine environment to a previous state in case of issues. Further, Parallels added a security manager to limit the amount of interaction between the Windows and Mac OS X installations. Despite the addition of numerous new features, tools and added functionality, the first iteration of Parallels Desktop for Mac 3.

A Parallels, Inc. Also, SCSI support has not been implemented. It is currently unknown if these features have been abandoned altogether, or if they will show up in a later build of version 3. Build , released on July 17, , [14] added an imaging tool which allowed users to add capacity to their virtual disks. Build , released on September 11, , [15] added some new features and updated some current features. Further, Parallels’ Image Tool was updated to allow one to change their virtual hard disk format between plain and expanding.

Parallels Explorer was updated to allow for one to automatically mount an offline VM hard drive to the Mac desktop. Some new features added are iPhone support in Windows, allowing iTunes in Windows to sync with it.

According to Parallels’ Licensing page, Desktop for Mac version 3. Parallels released the modified source code on July 2, , about 2 weeks after the promised release date.

Version 4. Parallels Desktop 4. Starting with the Version 4. Build , released January 9, , [27] includes performance enhancements and features, such as DirectX 9. Also included are usability features such as the ability to share Windows files by dragging them directly to a Mac application in the Mac Dock. Windows can now also automatically start in the background when a user opens a Windows application on the Mac desktop.

Officially released on November 4, , Parallels Desktop 5 adds several new features, mainly to improve integration with the host OS. Build , released on December 21, , added some new features. Officially announced on September 9, and launched on September 14, , Parallel 6 has full bit support for the first time.

Officially announced on September 1, and released on September 6, , Parallels Desktop 7 adds many new features. These include:. Officially announced August 22, and released September 4, , Parallels Desktop 8 adds many new features:.

Chapter 5. Virtual Storage.Parallels Desktop download | macOS

As the virtual machine will most probably expect to see a hard disk built into its virtual computer, Oracle VM VirtualBox must be able to present real storage to the guest as a virtual hard disk. There are presently three methods by which to achieve this:. Oracle VM VirtualBox can use large image files on a real hard disk and present them to a guest as a virtual hard disk. This is the most common method, described in Section 5.

This is described in Section 5. You can allow a virtual machine to access one of your host disks directly. This is an advanced feature, described in Section 9.

Each such virtual storage device, such as an image file, iSCSI target, or physical hard disk, needs to be connected to the virtual hard disk controller that Oracle VM VirtualBox presents to a virtual machine.

This is explained in the next section. Initially, this interface worked only with hard disks, but was later extended to also support CD-ROM drives and other types of removable media. In physical PCs, this standard uses flat ribbon parallel cables with 40 or 80 wires. Each such cable can connect two devices, called device 0 and device 1, to a controller.

Typical PCs had two connectors for such cables. As a result, support for up to four IDE devices was most common: primary device 0, primary device 1, secondary device 0, and secondary device 1. In Oracle VM VirtualBox, each virtual machine may have one IDE controller enabled, which gives you up to four virtual storage devices that you can attach to the machine. However, you can change the default setting. This makes no difference in terms of performance, but if you import a virtual machine from another virtualization product, the OS in that machine may expect a particular controller type and crash if it is not found.

Compared to IDE, it supports both much higher speeds and more devices per controller. Also, with physical hardware, devices can be added and removed while the system is running.

One virtual SATA controller is created by default, and the default disk that is created with a new VM is attached to this controller. Legacy Windows versions such as Windows XP, even with SP3 installed, will not see such disks unless you install additional drivers. The new controller appears as a separate PCI device in the virtual machine, and you can add virtual disks to it. SCSI is as a generic interface for data transfer between all kinds of devices, including storage devices.

SCSI is still used for connecting some hard disks and tape devices, but it has mostly been displaced in commodity hardware. It is still in common use in high-performance workstations and servers. The new controller appears as a separate PCI device in the virtual machine. Windows XP ships with drivers for neither. As opposed to SCSI physical devices, serial cables are used instead of parallel cables. This simplifies physical device connections. At this time, up to devices can be connected to the SAS controller.

The USB mass storage device class is a standard to connect external storage devices like hard disks or flash drives to a host through USB. All major OSes support these devices and ship generic drivers making third-party drivers superfluous. While most storage controllers appear as a single PCI device to the guest with multiple disks attached to it, the USB-based storage controller does not appear as virtual storage controller.

Each disk attached to the controller appears as a dedicated USB device to the guest. OSes need to support NVMe devices to make use of them. For example, Windows 8. For Windows 7, native support was added with an update. Recent Linux and Windows versions support these devices, but Windows needs additional drivers. Currently virtio-scsi controller support is experimental. The virtio-scsi controller will only be seen by OSes with device support for it.

In particular, there is no built-in support in Windows. So Windows will not see such disks unless you install additional drivers. Four slots attached to the traditional IDE controller, which are always present. Up to slots attached to the virtio-scsi controller, if enabled and supported by the guest OS.

Given this large choice of storage controllers, you may not know which one to choose. In general, you should avoid IDE unless it is the only controller supported by your guest. The variety of controllers is only supplied by Oracle VM VirtualBox for compatibility with existing hardware and other hypervisors. Disk image files reside on the host system and are seen by the guest systems as hard disks of a certain geometry.

Like a physical disk, a virtual disk has a size, or capacity, which must be specified when the image file is created. As opposed to a physical disk however, Oracle VM VirtualBox enables you to expand an image file after creation, even if it has data already. See Section 8. This format is used when you create a new virtual machine with a new disk. Image files of Parallels version 2 HDD format are also supported. Due to lack of documentation of the format, newer versions such as 3 and 4 are not supported.

You can however convert such image files to version 2 format using tools provided by Parallels. Irrespective of the disk capacity and format, as mentioned in Section 1. If you create a fixed-size image, an image file will be created on your host system which has roughly the same size as the virtual disk’s capacity. So, for a 10 GB disk, you will have a 10 GB file. Note that the creation of a fixed-size image can take a long time depending on the size of the image and the write performance of your hard disk.

Dynamically allocated. For more flexible storage management, use a dynamically allocated image. This will initially be very small and not occupy any space for unused virtual disk sectors, but will grow every time a disk sector is written to for the first time, until the drive reaches the maximum capacity chosen when the drive was created.

While this format takes less space initially, the fact that Oracle VM VirtualBox needs to expand the image file consumes additional computing resources, so until the disk file size has stabilized, write operations may be slower than with fixed size disks.

However, after a time the rate of growth will slow and the average penalty for write operations will be negligible. These are often referred to as known media and come from two sources:. The known media can be viewed and changed using the Virtual Media Manager , which you can access from the File menu in the VirtualBox Manager window. The known media are conveniently grouped in separate tabs for the supported formats. These formats are:.

For each image, the Virtual Media Manager shows you the full path of the image file and other information, such as the virtual machine the image is currently attached to. For virtual hard disks, the Create Virtual Hard Disk wizard is shown. This enables you to create a virtual ISO from selected files on the host. For floppy disks, the Floppy Disk Creator screen is shown. Copy an image to create another one.

Move an image to another location. If you use a file management feature of the host OS to move a disk image to a new location, run the VBoxManage modifymedium –setlocation command to configure the new path of the disk image on the host file system. Remove an image from the known media. You can optionally delete the image file when removing the image. Release an image to detach it from a VM. This action only applies if the image is currently attached to a VM as a virtual hard disk.

Search for an image by name or UUID. View and edit the Properties of a disk image. Type: Specifies the snapshot behavior of the disk. See Section 5. Location: Specifies the location of the disk image file on the host system. You can use a file dialog to browse for the disk image location. Description: Specifies a short description of the disk image. Size: Specifies the size of the disk image. You can use the slider to increase or decrease the disk image size.

Information: Specifies detailed information about the disk image. Refresh the property values of the selected disk image. To perform these actions, highlight the medium in the Virtual Media Manager and then do one of the following:. Use the Storage page in a VM’s Settings dialog to create a new disk image.

By default, disk images are stored in the VM’s folder. You can copy hard disk image files to other host systems and then import them in to VMs from the host system. However, some Windows guest OSes may require that you configure the new VM in a similar way to the old one.

Do not simply make copies of virtual disk images. See Section 1. For each virtual disk image supported by Oracle VM VirtualBox, you can determine separately how it should be affected by write operations from a virtual machine and snapshot operations. By default, images are in normal mode.