jamesstringer90 / jamesstringer90/appsandbox
Crash 0x80070005
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 704
- Forks
- 75
- Avg merge
- 9m
- Merged PRs (30d)
- 6
Description
trying to start a vm created:
HCS: Available
VMMS certificate found.
HCN: Available
GPUs: 1 found, 1 driver shares
[0] NVIDIA GeForce RTX 4080 SUPER (GPU-PV)
Loaded 1 VM(s) from config.
Starting VM "Win11Sandbox" (background)...
NAT subnet: 192.168.42.0/24 (gateway 192.168.42.1)
Allocated NAT IP 192.168.42.2 for "Win11Sandbox".
d3dlayers: using cached layers at D:\Software\FOSS_GitHub_Releases\AppSandbox-0.1.0-x64\d3dlayers
Re-creating HCS compute system for "Win11Sandbox"...
Plan9 share: AppSandbox.Drv.0 -> C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b26cc1edfbb8f4d0
Plan9 share: AppSandbox.GlLayers -> D:\Software\FOSS_GitHub_Releases\AppSandbox-0.1.0-x64\d3dlayers
HCS: {"Error":-2147024891,"ErrorMessage":"","Attribution":[{"OperationFailure":{"Detail":"Construct"}}]}
Error: Failed to create compute system (0x80070005)
HCN: Deleting endpoint {80C00B62-CDB1-45A2-8233-3B785279858D}...
HCN: Endpoint deleted.
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.
Research direction
Start by reproducing the failure during HCS compute-system creation for the "Win11Sandbox" VM, using the supplied startup log and 0x80070005 error as the starting point. Trace the Construct operation and its Plan9 shares, then confirm the cause and that the VM can start without the reported crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100