Skip to content

Latest commit

 

History

History
29 lines (16 loc) · 2.79 KB

NEWS.md

File metadata and controls

29 lines (16 loc) · 2.79 KB
Raw

NEWS

0.1-3 (under development)

  • guest serial console is now also enabled in macOS guests (in /dev/cu.virtio and /dev/tty.virtio). Previous versions enabled it only for Linux guests. It can be explicitly disabled using --no-serial option.

  • experimental --pty option allows the creation of pseudo-tty device for the guest serial console. Without this option the serial console is mapped to the stdin/out streams of the macosvm process. If the --pty option is specified then macosvm will create a new pty (typically in /dev/ptys.<n>) and map VM's serial port to it.

    Unfortuantely, Apple Virtialization Framework requires that the pty is connected before the VM is started. Therefore currently macosvm will print the pty path and wait for user input so that the user can connect to the newly created pty before starting the VM. Proceeding without connected pty leads to an error. This behavior may change in the future, which is why it is considered experimental.

0.1-2

  • added --ephemeral flag: when specified, all (read-write) disks (including auxiliary) will be cloned (see man clonefile) prior to starting the VM (by appending -clone-<pid> to their paths) and the clones are used instead of the original. Upon termination all clones are deleted. This is functionally similar to the --rm flag in Docker. IMPORTANT: you will lose any changes to the mounted disks made by the VM. This is intended for runners that pick up work, do something and then post the results somewhere, but don't keep them locally. macosvm attempts to clean up clones even on abnormal termination where possible. Individual disks can specify keep option which prevents them from being cloned in the ephemeral mode, e.g.: --disk results.img,keep will cause results.img to be used directly and modified by the VM even if --ephemeral is specified.

  • added heuristic to detect ECID from the auxiliary storage if it is not supplied by the configuration file

  • make the configuration file optional. It is now possible to start VMs simply by specifying the desired CPU/RAM and disk images and macosvm will try to infer all necessary settings automatically. I.e., if you have existing disk images aux.img and disk.img from previously restored/created VM, you can use the following to start it:

    macosvm -g --disk disk.img --aux aux.img -c 2 -r 4g

  • fixed a bug where the "readOnly" flag specified in the configuration file was not honored

  • added os and bootInfo entries in the configuration. Currently valid entries for os are "macos" (default) and "linux". The latter uses bootInfo dictionary with entries kernel (path, mandatory) and parameters (string, optional). Also a new storage type "initrd" has been added to support the Linux boot process (untested).

0.1-1

  • initial version