Skip to content

OmacVM 3.5.1

Latest

Choose a tag to compare

@gillesgoetsch gillesgoetsch released this 19 Nov 03:00
7b9ce95

Fixes for the Bridge next to Karabiner-Elements and for llama.cpp with Vulkan, and a clearer Omanotch check line.

What to do:

  • The app update: OmacVM › Check for Updates…. The Bridge and Vulkan fixes come with it; the Vulkan one from the VM's next start.
  • Update VM afterwards for the clearer Omanotch line in omacvm check.

What changed

  • Bridge memory next to Karabiner-Elements (#813, reported by @ilyador): when another app held a keyboard for itself (Karabiner-Elements does), OmacVM Bridge tried to read the keyboards again every 2 seconds with a new reader, and each try kept about 0.4 MB that macOS never gave back. Over a few hours the Bridge grew to gigabytes. It now keeps one reader and tries again after 2 s, then waits twice as long each time, up to 5 minutes.
  • Vulkan apps that map large memory (#786): with Vulkan on KosmicKrisp, OmacVM told apps that mapped memory is aligned to 16 KiB, but the VM maps it on 4 KiB pages. llama.cpp then stopped while loading a model ("not enough space in the buffer") unless started with --no-host. The VM is now told 4 KiB, and llama.cpp runs with its default settings.
  • Omanotch's bar copy (seen in a report by @epicoun, #829): when Omarchy's omarchy plugin clone could not make the bar copy, omacvm check now says why instead of "made no copy ()".
  • Draw only what changed (Battery saver, experimental, off by default): now checked together with Copy only what changed (on by default), in a window and in full screen at 120 Hz, and on its own with HDR on: the same pixels. Its (i) gives the MacBook Air M2's figures for the two together: about 7 % less power with a chat's typing dots, about 3 % with the pointer moving over app windows.

Thanks to @ilyador and @epicoun for the reports.

Known issues

  • The Vulkan fix for llama.cpp works from the VM's next start after the update. Until then, start llama.cpp's tools with --no-host as before.
  • Prefer VP9 on YouTube (experimental): videos that YouTube offers only in AV1 are not offered. About 1 to 3 % of the frames of a 1080p60 video drop.
  • If the control centre is switched on while the VM's session is locked, its bar item shows up after the next unlock.
  • Pointer at the edges in full screen on a MacBook with a notch: pushing along the top edge or up a side edge does not reach the VM's top corners.
  • Under investigation: one VM moved to Omarchy 4.5 stopped responding once. If a VM stops responding, quit OmacVM and start the VM again.
  • New VMs from a prebuilt image use the 3.4.0 image (Omarchy 4.5.0). 3.5.1's OmacVM is put on top while the VM is made.

Tested

With the release build:

  • Built and notarized on the Mac mini (M4, macOS 27.0), its QEMU and GPU runtime built from source. Every runtime build check passed, including Vulkan in the VM on KosmicKrisp and MoltenVK and the screen copy checks.
  • On the Mac mini, hidden: a new VM from the prebuilt image by the release app: unpacked in 9 seconds (5.8 GB on disk), OmacVM 3.5.1 in the VM, Omarchy 4.5.0, no failed units, Mission Control off, a second update and a restart fine, the desktop session up.
  • On the MacBook Air, hidden: the app's own update from 3.5.0 to 3.5.1 in 5 seconds: settings, the control centre's settings file and the VM records kept.
  • The downloaded release checked in a fresh folder: checksum, feed and manifest signatures, the app's own update checks, code signature, notarization (stapled), Developer ID team.

With the release candidate (the same code as the release; the tested build differed only in one CHANGELOG paragraph):

  • CI green (check, app, guest) on the release candidate.
  • Built on the Mac mini (M4) with its QEMU and GPU runtime from source. Every runtime build check passed, including Vulkan in the VM on KosmicKrisp and MoltenVK.
  • Bridge: the keyboard reader was refused 200 times in a row, as when another app holds a keyboard. It kept one reader, its memory stayed flat at about 3.4 MB, and no permission prompt appeared.
  • Vulkan on a Mac mini M4 (Omarchy 4.5): the VM now reports 4 KiB map alignment, and 0 of 18 mappings were off it. llama.cpp's benchmark ran with its default settings. vkcube, vkmark and Zink (cold and warm start) ran with no GPU errors.
  • Omanotch: omacvm check says why the bar copy was not made (the VM-side tests).
  • Draw only what changed with Copy only what changed, both in a mode that compares every frame with a full one:
    • MacBook Pro M1 Max on screen, full screen with the notch at 120 Hz, with the pointer moving over windows and extra brightness on and off: no wrong pixels in 1995 and 265 checks.
    • The same Mac in a window: no wrong pixels in 96 and 247 checks.
    • A deliberately broken copy was caught.
    • With HDR on: no wrong pixels in 136 checks.
    • On the Mac mini at four Omarchy scales: no wrong pixels in 293 checks.
  • MacBook Air M2 on screen: Battery saver on and off turns Draw only what changed on and off from the next start.
  • Hidden end-to-end runs that update from 3.5.0 through the app's own updater:
    • Omarchy 4.0: 149 ok, 0 failed.
    • Omarchy 4.5: 151 ok, 2 failed. Both were the control centre's bar item waiting for an unlock, and it passed twice on its own.
  • Moving a VM's disk: nothing it touches changed since 3.5.0, so 3.5.0's 5 of 5 still holds.

Not tested yet:

  • Karabiner-Elements itself holding a keyboard while the Bridge runs.
  • The fast network.
  • The disk move window's lock shown on screen.