Skip to content

kvm-it 0.4.8: polish, licences, Secure Boot boot drive (VM-verified)

Latest

Choose a tag to compare

@spilloid spilloid released this 09 Oct 04:04
744c214

kvm-it 0.4.8: polish ahead of 1.0. Desktop, CI and docs, plus a new boot-drive image; no protocol change. Reflash the adapter (Flash adapter…) to get the new boot drive; the pairing is kept.

What's new

  • Windows: a real icon and version information on kvmit.exe and kvmit-gui.exe, so Explorer, the taskbar, the Start menu and Properties > Details show kvm-it and its version; the installer shows the icon in Settings > Apps.
  • Bluetooth errors that say why: Bluetooth turned off, blocked (rfkill or airplane mode, or a hardware switch), no adapter at all (or one not passed through to a VM), or the bluetoothd service not running, each with what to do.
  • Licences in every package: THIRD_PARTY_LICENSES.html (every Rust crate in the app, with its licence text) and THIRD_PARTY_FIRMWARE_LICENSES.txt (everything the adapter firmware links, down to the headers of individual third-party source files). Both are generated and checked in CI.
  • Secure Boot for the boot drive: the drive now carries the iPXE project's signed pair (a Microsoft-signed shim and iPXE signed by the iPXE CA), so firmware that trusts Microsoft's third-party UEFI CA can start it with Secure Boot on.
  • Road to 1.0: docs/roadmap.md now has the plan and a 1.0 checklist.

Verified, and what is not

  • Windows (real hardware, no Bluetooth adapter): the icon and every version field read correctly in Explorer; kvmit scan names the missing adapter.
  • Linux: the CI-built app scans and finds a real adapter, and explains an absent one. The off/blocked/no-daemon messages are unit-tested, not yet provoked on real hardware; the same goes for macOS.
  • Secure Boot: virtual machine only (OVMF with the stock Microsoft keys, Secure Boot on and off). No real PC with Secure Boot on has been tried, and the new image has not yet been flashed to a real adapter: tracked in #40. PCs that turn Microsoft's third-party CA off will refuse it; with Secure Boot off it works as before.
  • Still open from earlier: capture-card unplug/no-signal (#31), recording with sound (#32), YUYV colour range (#33), wheel/touchpad on a target (#34).

Downloads and signing

  • Windows: .msi and .zip, code-signed in CI by Azure Artifact Signing (see SIGNATURES.txt).
  • Linux: kvm-it-0.4.8-x86_64.AppImage, not code-signed (check its .sha256).
  • macOS: kvm-it-0.4.8-macos-arm64.dmg, ad-hoc signed and not notarized: the first time, allow it in System Settings > Privacy & Security > Open Anyway.
  • The boot drive's iPXE source archive is attached as usual.

Full details: CHANGELOG. Review log: rounds 31-35 in docs/dev-process.md.