Log Qubes libxenlight VM start blocker
This commit is contained in:
parent
8888601f69
commit
4f58b83842
3
Setup.md
3
Setup.md
|
|
@ -123,6 +123,7 @@ Thread-safety expectation:
|
|||
- missing: `mvp`, `setup`, `components`, `samples`
|
||||
- `CR_SDK_CK-main/scripts/build_flash_mvp.sh` exists, but it expects the above role directories.
|
||||
- Python helper scripts were intentionally moved out of `CR_SDK_CK-main/scripts` and are now maintained at workspace root.
|
||||
- Qubes VM provisioning is currently blocked: `libxenlight` failed to create domain `k_client`.
|
||||
|
||||
Implication:
|
||||
- We cannot currently confirm live FIDO2 connectivity from this host.
|
||||
|
|
@ -131,6 +132,7 @@ Implication:
|
|||
Session note (2026-04-24):
|
||||
- Markdown tracking was reviewed and normalized around `Setup.md` + `Workplan.md` as the active, continuously updated execution record.
|
||||
- AppVM template decision recorded: use `debian-13-xfce` for `k_client`, `k_proxy`, and `k_server`.
|
||||
- VM start attempt failed with Xen toolstack error: `libxenlight have failed to create new domain 'k_client'`.
|
||||
|
||||
## Known FIDO2 Transport Boundary
|
||||
|
||||
|
|
@ -185,6 +187,7 @@ SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="0005", MODE="06
|
|||
|
||||
## Open Gaps To Resolve
|
||||
|
||||
- Why Xen/libxenlight cannot create the `k_client` domain on this host (memory/pool, stale domain, template, storage, or hypervisor state).
|
||||
- Why no `/dev/hidraw*` device is visible despite USB connection.
|
||||
- Whether udev rule is missing or device VID/PID differs from expected.
|
||||
- Whether current firmware on card exposes the FIDO2 HID interface.
|
||||
|
|
|
|||
Loading…
Reference in New Issue