You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
shore(docs): update API Token auth section (#1991)
- Added MD059 rule to .markdownlint.json for better markdown formatting.
- Updated CODE_OF_CONDUCT.md to format email address as a link.
- Consolidated privilege descriptions in docs/index.md for clarity.
- Improved formatting in docs/resources/virtual_environment_vm.md for better readability.
* add `gh` to devcontainer
* remove wakatime
---------
Signed-off-by: Pavel Boldyrev <[email protected]>
Copy file name to clipboardExpand all lines: CODE_OF_CONDUCT.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
34
34
35
35
## Enforcement
36
36
37
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
37
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at <[email protected]>. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
38
39
39
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-`amd_sev` - (Optional) Secure Encrypted Virtualization (SEV) features by AMD CPUs.
138
-
-`type` - (Optional) Enable standard SEV with `std` or enable experimental
139
-
SEV-ES with the `es` option or enable experimental SEV-SNP with the `snp` option
140
-
(defaults to `std`).
138
+
-`type` - (Optional) Enable standard SEV with `std` or enable experimental SEV-ES with the `es` option or enable experimental SEV-SNP with the `snp` option (defaults to `std`).
141
139
-`allow_smt` - (Optional) Sets policy bit to allow Simultaneous Multi Threading (SMT)
142
140
(Ignored unless for SEV-SNP) (defaults to `true`).
143
-
-`kernel_hashes` - (Optional) Add kernel hashes to guest firmware for measured
144
-
linux kernel launch (defaults to `false`).
141
+
-`kernel_hashes` - (Optional) Add kernel hashes to guest firmware for measured linux kernel launch (defaults to `false`).
145
142
-`no_debug` - (Optional) Sets policy bit to disallow debugging of guest (defaults
146
143
to `false`).
147
-
-`no_key_sharing` - (Optional) Sets policy bit to disallow key sharing with
148
-
other guests (Ignored for SEV-SNP) (defaults to `false`).
144
+
-`no_key_sharing` - (Optional) Sets policy bit to disallow key sharing with other guests (Ignored for SEV-SNP) (defaults to `false`).
149
145
150
146
The `amd_sev` setting is only allowed for a `root@pam` authenticated user.
151
147
-`audio_device` - (Optional) An audio device.
@@ -657,6 +653,7 @@ trusts the user to set `agent.enabled` correctly and waits for
657
653
`qemu-guest-agent` to start.
658
654
659
655
## AMD SEV
656
+
660
657
AMD SEV (-ES, -SNP) are security features for AMD processors. SEV-SNP support
661
658
is included in Proxmox version **8.4**, see [Proxmox Wiki](
`amd-sev` requires root and therefore `root@pam` auth.
667
664
668
-
SEV-SNP requires `bios = OVMF` and a supported AMD CPU (`EPYC-v4` for instance),
669
-
`machine = q35` is also advised. No EFI disk is required since SEV-SNP uses
670
-
consolidated read-only firmware. A configured EFI will be ignored.
665
+
SEV-SNP requires `bios = OVMF` and a supported AMD CPU (`EPYC-v4` for instance), `machine = q35` is also advised. No EFI disk is required since SEV-SNP uses consolidated read-only firmware. A configured EFI will be ignored.
671
666
672
-
All changes made to `amd_sev` will trigger reboots. Removing or adding the
673
-
`amd_sev` block will force a replacement of the resource. Modifying the `amd_sev`
674
-
block will not trigger replacements.
667
+
All changes made to `amd_sev` will trigger reboots. Removing or adding the `amd_sev` block will force a replacement of the resource. Modifying the `amd_sev` block will not trigger replacements.
675
668
676
-
`allow_smt` is by default set to `true` even if `snp` is not the selected type.
677
-
Proxmox will ignore this value when `snp` is not in use. Likewise `no_key_sharing`
678
-
is `false` by default but ignored by Proxmox when `snp` is in use.
669
+
`allow_smt` is by default set to `true` even if `snp` is not the selected type. Proxmox will ignore this value when `snp` is not in use. Likewise `no_key_sharing` is `false` by default but ignored by Proxmox when `snp` is in use.
0 commit comments