Example of how to use Set-VMFirmware to add an EFI shim path (VMBootSource) ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- documentation
Research direction
Start with docset/winserver2022-ps/hyper-v/Set-VMFirmware.md, linked in the issue, and review its existing parameter descriptions and examples. Add an example for setting a VMBootSource firmware path to a Debian EFI shim, using the issue's Gen2 VM and firmware-path context. Verify that the example matches the documented Set-VMFirmware syntax and formatting.
Written by the indexing model from the issue text.
Description
Prerequisites
- Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
- Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Typo in
Get-Foocmdlet" instead of "Typo." - Verify Version: If there is a mismatch between documentation and the behavior on your system, ensure that the version you are using is the same as the documentation. Check this box if they match or the issue you are reporting is not version specific.
Links
Summary
Could you please add an example showing how to use Set-VMFirmware to add a VMBootSource firmware path?
Details
For example, I have a bootable Gen2 (UEFI) VM where I installed Debian that has the firmware path pointing to the debian shimx64.efi:
PS C:\Windows\system32> (Get-VMFirmware -VMName gen2-debian-test).BootOrder | Where-Object { $_.BootType -eq 'File' } | Select-Object -ExpandProperty FirmwarePath
HD(1,GPT,FFB61BB9-ADBE-49BC-BCE8-22AF4F699210,0x800,0x100000)/\EFI\debian\shimx64.efi
PS C:\Windows\system32>
I want to add a similar setting to another new Gen2 VM, but I am having trouble figuring out how to do that.
I know the disk identifier, but I just can't figure out how to set the firmware path using Set-VMFirmware.
Suggested Fix
Add an example showing how to set firmware path to EFI shim, please.
- Dominant language
- Dockerfile
- Stars
- 504
- Forks
- 635
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MicrosoftDocs/windows-powershell-docs
-
issue-doc-bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
issue-doc-bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MicrosoftDocs/windows-powershell-docs#3861 · 1 comment ·
-
issue-doc-bug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
issue-doc-bug needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
issue-doc-bug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in MicrosoftDocs/windows-powershell-docs
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·