Files
obsidian-vault/personal/projects/virfield.md
T

53 lines
3.1 KiB
Markdown
Executable File
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: Virfield
namespace: personal
updated: '2026-10-03'
status: candidate-not-release-ready-monterey-plan-recorded
tags:
- virfield
- macos
- vm
- go
- infrastructure
---
# Virfield — актуальный статус 2026-10-03
**Следующее действие:** остановить разработку в этой сессии после commit/push. Не объявлять релиз готовым.
## Текущий ответ по релизу
- Репозиторий: рабочая ветка `codex/versioned-images` должна быть запушена после финального cleanup/commit этой сессии.
- Release-ready: нет. `make check` прошел, live runtime обновлялся, но Monterey + Xcode acceptance не закрыта.
- Monterey 12.6 + Xcode 13.4.1: не верифицировано как `image_ready`.
- Default Xcode install: код мигрирован на VirtioFS для macOS 13+ guests, но Monterey 12.x не поддерживает Apple VZ shared directories.
## Факты по Monterey
- Lume VM стартует.
- SSH в Monterey guest работает.
- `lume run --shared-dir` на Monterey 12.6 не дает `/Volumes/My Shared Files`.
- В guest нет `/sbin/mount_virtiofs` и `/usr/sbin/mount_virtiofs`.
- Live retry для `job-057b0898f3746df8b12fb8b5c4c34c1c` теперь завершается `virtiofs_unsupported`, VM остается stopped, host-side `cp`/`ditto`/`tar`/`scp`/`rsync` процессов нет.
## Что уже сделано в кандидате
- Legacy identity mode: `legacy_uuid`, один активный worker на UUID, registry publish для legacy запрещен.
- Xcode download/cache: Apple auth/browser path, XIP SHA/signature/cache validation, host `codesign --deep` убран из cached/downloaded hot path.
- Lume service: stable `virfield-lume -config`, patched Lume `0.5.3-virfield6` required.
- Developer provisioning: macOS 13+ uses native `lume run --shared-dir <verified Xcode cache parent>` and guest-side `ditto` from `/Volumes/My Shared Files`.
- Monterey guard: macOS < 13 fails fast with `virtiofs_unsupported` before VM mutation.
## Monterey plan
1. Add a separate Monterey transport path; do not weaken the macOS 13+ VirtioFS path.
2. First probe NFS live on the existing Monterey VM: host export, guest `mount_nfs`, small file roundtrip, cleanup.
3. If NFS passes, implement bounded host export lifecycle: create private export dir, mount in guest, copy Xcode with `ditto`, unmount, remove export.
4. If NFS fails, implement explicit SSH-copy fallback as a separate Monterey-only contract with progress, cancellation, logs, and cleanup.
5. Run full Monterey 12.6 + Xcode 13.4.1 image build to `image_ready`, then ordinary clone/workload/artifact/cleanup before claiming support.
## Verification now
- `make check` passed on 2026-10-03 after the VirtioFS guard and docs updates.
- Repo docs updated: `docs/IMAGE-PIPELINE.md`, `docs/VERIFICATION.md`.
- This note is intentionally current-only; historical details live in Git/docs, not here.