Skip to content

Commit ac64705

Browse files
committed
docs(amdsev): add control channel startup steps
1 parent eef905e commit ac64705

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

misc/AMDSEV/README.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,30 @@ The script:
124124
- Forwards RPC port 5050 to host port 15051
125125
- Outputs serial log to a temp file and follows it
126126

127+
### Start Katana via Control Channel
128+
129+
To start Katana manually over the control channel:
130+
131+
```sh
132+
# 1) Boot VM without auto-starting Katana
133+
sudo ./misc/AMDSEV/start-vm.sh --no-start
134+
135+
# 2) Use the control socket printed by start-vm.sh (example path below)
136+
CONTROL_SOCKET=/tmp/katana-tee-vm-control.12345.sock
137+
138+
# 3) Start Katana with comma-separated CLI args
139+
printf 'start --http.addr,0.0.0.0,--http.port,5050,--tee.provider,sev-snp\n' \
140+
| socat - UNIX-CONNECT:"$CONTROL_SOCKET"
141+
142+
# 4) Check launcher status
143+
printf 'status\n' | socat - UNIX-CONNECT:"$CONTROL_SOCKET"
144+
```
145+
146+
Control responses:
147+
- `ok started pid=...` means Katana was launched.
148+
- `running pid=...` means Katana is still running.
149+
- `stopped exit=...` means Katana is not running.
150+
127151
### Launch Measurement Verification
128152

129153
To verify a TEE VM's integrity, compute the expected launch measurement using `snp-digest`:

0 commit comments

Comments
 (0)