`tmux`-like (maybe `tmux` itself) manager for child VMs #28

New Issue

Open

opened 2025-02-05 20:04:05 +00:00 by ryan · 1 comment

ryan commented

2025-02-05 20:04:05 +00:00

Owner

As an example, let's take Icepick broadcasting.

Start one shell in tmux in bare metal. From that shell, run:

vm create --name icepick --kernel airgap --usb --mount /tmp/icepick:/tmp/icepick
vm create --name icepick-broadcast --kernel online --mount /tmp/icepick:/tmp/icepick
vm attach-usb --hub <hub> --target icepick

This spawns two new tmux windows. The first one is named "icepick" and is running with the offline kernel, and has a USB hub attached - the hub can then become accessible from within the VM. The second one is named "icepick" and is running a network-accessible kernel. You can then run icepick workflow <whatever> broadcast on the online system, and keyfork shard recover followed by icepick workflow <whatever> transfer in the other VM, and have the entire operation done on a single system.

As an example, let's take Icepick broadcasting. Start one shell in tmux in bare metal. From that shell, run: ``` vm create --name icepick --kernel airgap --usb --mount /tmp/icepick:/tmp/icepick vm create --name icepick-broadcast --kernel online --mount /tmp/icepick:/tmp/icepick vm attach-usb --hub <hub> --target icepick ``` This spawns two new `tmux` windows. The first one is named "icepick" and is running with the offline kernel, and has a USB hub attached - the hub can then become accessible from within the VM. The second one is named "icepick" and is running a network-accessible kernel. You can then run `icepick workflow <whatever> broadcast` on the online system, and `keyfork shard recover` followed by `icepick workflow <whatever> transfer` in the other VM, and have the entire operation done on a single system.

ryan commented

2025-06-25 04:14:13 +00:00

Author

Owner

tmux start-server \; new-session -d can create a new session inside the guest. If we can forward /tmp/tmux-0/default to the host in some manner, we can connect to it using tmux -S /tmp/tmux-guest-0/default attach. We just need to figure out how to actually forward it. It would likely involve socat on both sides of qemu, operating on the vsock.

`tmux start-server \; new-session -d` can create a new session inside the guest. If we can forward `/tmp/tmux-0/default` to the host in some manner, we can connect to it using `tmux -S /tmp/tmux-guest-0/default attach`. We just need to figure out how to actually forward it. It would likely involve `socat` on both sides of qemu, operating on the vsock.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/airgap#28

No description provided.

tmux-like (maybe tmux itself) manager for child VMs #28

`tmux`-like (maybe `tmux` itself) manager for child VMs #28