Commit 5ff7bcc
committed
libvirt: Fix custom secure boot logic
- The nvram path needs to be absolute (would be nice if we could
pass this as a file descriptor instead, but hard to do AFAIK
with libvirt today)
- When a custom nvram is specified, we need to avoid using firmware="efi"
as it's mutually exclusive with explicit <loader> paths
- Also need to explicitly specify `raw` format for nvram
No tests yet, but I did test this locally as part of updating
bootc's composefs+UKI integration test suite.
Signed-off-by: Colin Walters <[email protected]>1 parent 92cc086 commit 5ff7bcc
2 files changed
+18
-8
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
209 | 209 | | |
210 | 210 | | |
211 | 211 | | |
212 | | - | |
213 | | - | |
214 | | - | |
215 | | - | |
216 | | - | |
| 212 | + | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
217 | 218 | | |
218 | 219 | | |
219 | 220 | | |
| |||
231 | 232 | | |
232 | 233 | | |
233 | 234 | | |
234 | | - | |
| 235 | + | |
| 236 | + | |
235 | 237 | | |
236 | 238 | | |
237 | 239 | | |
| |||
242 | 244 | | |
243 | 245 | | |
244 | 246 | | |
245 | | - | |
| 247 | + | |
| 248 | + | |
| 249 | + | |
| 250 | + | |
| 251 | + | |
246 | 252 | | |
247 | 253 | | |
248 | 254 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1131 | 1131 | | |
1132 | 1132 | | |
1133 | 1133 | | |
| 1134 | + | |
| 1135 | + | |
| 1136 | + | |
| 1137 | + | |
1134 | 1138 | | |
1135 | 1139 | | |
1136 | | - | |
| 1140 | + | |
1137 | 1141 | | |
1138 | 1142 | | |
1139 | 1143 | | |
| |||
0 commit comments