Upgrading (CLI)

How to upgrade the Anka Virtualization package

Upgrading the Build Cloud too? Check out our upgrade procedure for the Anka Build Cloud Controller & Registry

We do not follow strict semantic versioning; minor and major version increases can have significant changes

Pre-upgrade Considerations

Existing Version Target Version Recommendation

< 3.x

3.x

Existing Version	Target Version	Recommendation
< 3.x	3.x	External volumes must be mounted as APFS in order to use them for `img_lib_dir`, etc. \| < 3.x \| 3.x (intel) \| VMs suspended on Anka 2.x will need to be re-suspended on 3.x. The Controller Agent version that comes with Anka will start at 1.30.1. Older versions of the Controller do not support Anka 3. You will need to upgrade your controller to at least 1.30.1. Previously, `anka create` would create a suspended VM. Starting in this version, VMs are stopped. GUI (Anka.app) VM creation will produce a VM without macOS set up. `anka --machine-readable registry list` has a key name change from `id` to `uuid` `modify set` commands will continue to work, but not show in the `anka modify --help` output. Only macOS 10.15 and above are supported by Veertu. If you're using an older version, do not upgrade addons to 3.x and they should continue to function. Existing VM macOS Version \| Target Version \| Recommendation --- \| --- \| --- <= Big Sur \| Monterey \| You will need to change your VM template: `anka modify {vmName} set hard-drive -c sata`, `anka modify {vmName} set network-card -c virtio-net` <= Big Sur \| Ventura \| You will need to change your VM template: `anka modify {vmName} set hard-drive -c sata`, `anka modify {vmName} set network-card -c virtio-net`, and `anka modify {vmName} set custom-variable hw.x2apic 1` Monterey \| Ventura \| You will need to change your VM template: `anka modify {vmName} set custom-variable hw.x2apic 1` ### Upgrade Procedure #### [1. Download and install the latest version](/anka-virtualization-cli/getting-started/installing-the-anka-virtualization-package/) Upgrading the Build Cloud too? Check out our upgrade procedure for the Anka Build Cloud Controller & Registry We do not follow strict semantic versioning; minor and major version increases can have significant changes Upgrading Anka Virtualization software while VMs are running is typically safe. Please see the Pre-upgrade Considerations below to be sure. #### 2. Upgrade VM addons If your existing version is noted in the [Pre-Upgrade Considerations](/anka-virtualization-cli/upgrading/#pre-upgrade-considerations) as requiring an addons upgrade, or, if you're going between major/minor versions of Anka: 1. Upgrade the guest addons inside existing VM Templates `anka start -u`. 2. Push the newly upgraded VM templates to registry with `anka registry push {vmNameOrUUID} --tag `

External volumes must be mounted as APFS in order to use them for `img_lib_dir`, etc.

| < 3.x | 3.x (intel) |

VMs suspended on Anka 2.x will need to be re-suspended on 3.x.
The Controller Agent version that comes with Anka will start at 1.30.1. Older versions of the Controller do not support Anka 3. You will need to upgrade your controller to at least 1.30.1.
Previously, anka create would create a suspended VM. Starting in this version, VMs are stopped.
GUI (Anka.app) VM creation will produce a VM without macOS set up.
anka --machine-readable registry list has a key name change from id to uuid
modify set commands will continue to work, but not show in the anka modify --help output.
Only macOS 10.15 and above are supported by Veertu. If you're using an older version, do not upgrade addons to 3.x and they should continue to function.

Existing VM macOS Version | Target Version | Recommendation --- | --- | --- <= Big Sur | Monterey | You will need to change your VM template: `anka modify {vmName} set hard-drive -c sata`, `anka modify {vmName} set network-card -c virtio-net` <= Big Sur | Ventura | You will need to change your VM template: `anka modify {vmName} set hard-drive -c sata`, `anka modify {vmName} set network-card -c virtio-net`, and `anka modify {vmName} set custom-variable hw.x2apic 1` Monterey | Ventura | You will need to change your VM template: `anka modify {vmName} set custom-variable hw.x2apic 1` ### Upgrade Procedure #### [1. Download and install the latest version](/anka-virtualization-cli/getting-started/installing-the-anka-virtualization-package/)

Upgrading the Build Cloud too? Check out our upgrade procedure for the Anka Build Cloud Controller & Registry

We do not follow strict semantic versioning; minor and major version increases can have significant changes

Upgrading Anka Virtualization software while VMs are running is typically safe. Please see the Pre-upgrade Considerations below to be sure.

#### 2. Upgrade VM addons If your existing version is noted in the [Pre-Upgrade Considerations](/anka-virtualization-cli/upgrading/#pre-upgrade-considerations) as requiring an addons upgrade, or, if you're going between major/minor versions of Anka: 1. Upgrade the guest addons inside existing VM Templates `anka start -u`. 2. Push the newly upgraded VM templates to registry with `anka registry push {vmNameOrUUID} --tag `