Mycelium: background health check and reconnect logic #5
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
geomind_code/my_hypervisor#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The current implementation in
chvm-libprobes for the Mycelium IP once after boot but does not monitor the health of the connection thereafter. If themyceliumprocess inside the VM or on the host dies/stalls, the VM loses connectivity without notification.Proposed Changes:
VmManagerfor Mycelium enabled VMs.myceliumprocess via vsock or network probing.chvm-initto restart the mycelium service if it fails.Work completed in PR
Guest-side: Mycelium process supervision (chvm-init)
enabling restart
after delay , with up to 5 retry attempts on spawn failure
Host-side: On-demand health checks (chvm-lib)
CLI: Health in inspect (chvm-cli)
Tests (tests/13_mycelium.sh)
auto-restart after crash (new PID), IPv6 recovery after restart, health status healthy after recovery