In addition to the options listed here, a communicator can be configured for this builder. In addition to the options defined there, a private key file can also be supplied to override the typical auto-generated key:. Valid values are "win", "lin", "mac", "os2" and "other". The goal of these commands should be to type just enough to initialize the operating system installer. Special keys can be typed as well, and are covered in the section below on the boot command.
If this is not specified, it is assumed the installer will start itself. The value of this should be a duration. Examples are "5s" and "1m30s" which will cause Packer to wait five seconds and one minute 30 seconds, respectively. If this isn't specified, the default is 10 seconds. This is most useful for unattended Windows installs, which look for an Autounattend. By default, no floppy will be attached. All files listed in this setting get placed into the root directory of the floppy and the floppy is attached as the first floppy device.
Currently, no support exists for creating sub-directories on the floppy. Directory names are also allowed, which will add all the files found in the directory to the floppy. This is useful for when your floppy disk includes drivers or if you just want to organize it's contents as a hierarchy.
This is most useful for cloud-init, Kickstart or other early initialization tools, which can benefit from labelled floppy disks. By default, the floppy label will be 'packer'. This may be relative or absolute. Make sure to shutdown your VM and quit Parallels Desktop before! Now, that your Parallels Desktop is patched, you can install Parallels Tools as usual - even in newly created VMs - via the menu.
The following tests have been conducted with Parallels Desktop Nicolas Thumann. You can easily confirm whether Parallels Tools were installed. Start your virtual machine and look at the status bar of its window. When Parallels Tools are installed, you do not need to press any key to release the mouse and keyboard - they are released automatically.
Parallels Tools may fail to install because not all mandatory packages are available. You're prompted to choose the command to gain root privileges and enter the password if su - root password, if sudo - your user's password. After that, Parallels Tools update automatically. To reinstall Parallels Tools in Linux, first remove Parallels Tools and then install them once again. Parallels Tools for Linux To install Parallels Tools for Linux, you must have the following packages: gcc; make; kernel development package; and checkpolicy for SELinux-enabled systems.
Preparing for installation Before installing Parallels Tools in a Linux virtual machine, perform the following actions: Close all applications running on the virtual machine.
If you use a 3D accelerated window manager, disable it. Convert its system volume to a template image. You will need the volume ID that you can obtain with vinfra service compute volume list. For example, to use the win10 VM boot volume, run:. Create a new Windows VM from the template, attaching the guest tools image to it during creation. For example:. The size of volume to be created from a template image must be equal to or greater than the minimum volume size specified in the image metadata.
Once the image is mounted inside the Windows VM, launch the installer in the AutoPlay window if autorun is enabled. The steps you need to perform to remove guest tools depend on the guest OS and are described in the following sections.
To uninstall the guest tools from a Linux guest, log in to the virtual machine and do as follows:. If any of the packages listed above are not installed on your system, the command will fail.
0コメント