[Bug]:

未關閉
#983 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 6 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
15/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
c, cpp
領域
desktop

研究方向

The report only says the Intel VT engine shows as enabled in the VM UI while the checkbox in the VM settings dialog is greyed out; it names no component, file or log, and the reproduction section contradicts itself ("it works"). A starter would first need to reproduce on a Windows 11 x86 host with VirtualBox 7.2.22 and identify which GUI dialog and which setting controls the greyed-out state, then trace where its enabled/disabled state is computed for the settings page. Done means the settings control reflects the same state the VM UI reports, with a note in the issue about which component was responsible.

由索引模型根據 Issue 內容生成。

描述

bug
Version

7.2.22

Host OS Type

Windows

Host OS name + version

Windows 11 Build 26300.9168

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

No response

Component

Unspecified

What happened?

in the latest client, the Intel VT engine is shown as enabled in the virtual machine UI, yet the corresponding option remains grayed out in the virtual machine settings.

How can we reproduce this?

In the latest client, it works.

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
主要語言
C
星號
1.4k
分支
219
PR 合併指標
30 天內沒有已合併 PR

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

VirtualBox/virtualbox 的其他 Issue

查看 VirtualBox/virtualbox 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。