jamesstringer90 / jamesstringer90/appsandbox
Black screen after VM Boot
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 704
- Forks
- 75
- Avg merge
- 9m
- Merged PRs (30d)
- 6
Description
Vm seems to have successfully booting, was able to use normally untill black screen. Also have to force shutdown as normal shutdown does not work.
WebView2 Runtime: 149.0.4022.69
HCS: Available
VMMS certificate found.
HCN: Available
GPUs: 2 found, 2 driver shares
[0] NVIDIA GeForce RTX 4090 Laptop GPU (GPU-PV)
[1] Intel(R) UHD Graphics (GPU-PV)
Loaded 1 VM(s) from config.
Starting VM "CFDSandbox" (background)...
d3dlayers: could not resolve WuCategoryId from displaycatalog
Re-creating HCS compute system for "CFDSandbox"...
Plan9 share: AppSandbox.Drv.0 -> C:\Windows\System32\DriverStore\FileRepository\nvltsi.inf_amd64_2ce37f1bf94224ed
Plan9 share: AppSandbox.Drv.1 -> C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_5bc67ef17169627e
Nested virt: host supported (ProcessorCapabilities probed).
HCS callback registered [V2] for "CFDSandbox".
Starting VM "CFDSandbox"...
Applying GPU-PV...
GPU-PV applied successfully.
VM "CFDSandbox" started.
HCS enumerate: [{"Id":"922fcfeb-f923-4a8a-a2a2-ab0fd9a18285","SystemType":"VirtualMachine","RuntimeOsType":"Windows","Owner":"CmService","RuntimeId":"922fcfeb-f923-4a8a-a2a2-ab0fd9a18285","State":"SavedAsTemplate"},{"Id":"A16D551D-9A56-4967-AD9C-819839EFAFB7","SystemType":"VirtualMachine","Name":"CFDSandbox","Owner":"VMMS","RuntimeId":"a16d551d-9a56-4967-ad9c-819839efafb7","MemoryTopology":{"AccessTrackingEnabled":false,"HardwareAccessTrackingSupported":false,"DeviceAccessTrackingSupported":false,"AccessTrackingRangeSizeInPages":0,"AccessTrackingBitmapSizeInBits":0,"GpaMappingSizeInPages":0}},{"Id":"CFDSandbox","SystemType":"VirtualMachine","Owner":"CFDSandbox","RuntimeId":"00fb72c2-8bc6-56c4-aa74-97013bbd5c0b","State":"Running"}]
hcs_find_runtime_id: found a16d551d-9a56-4967-...
Opening IDD display for "CFDSandbox"
display logs
IDD display started.
Hotkey capture enabled.
Clipboard module created.
Audio: Started recv thread (will connect when helper is available).
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
CLIP: Window focused — clipboard sync ON.
Connection failed, retrying in 3s.
CLIP: Window unfocused — clipboard sync OFF.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
CLIP: Window focused — clipboard sync ON.
Connection failed, retrying in 3s.
CLIP: Window unfocused — clipboard sync OFF.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
Connecting to frame service...
Connection failed, retrying in 3s.
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 with the VM boot log and the IDD display log, focusing on the repeated frame service connection failures after the VM starts and the display is opened. Reproduce the black screen and verify that the display remains usable and the VM can shut down normally without a forced shutdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- computer-graphics, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100