1 files changed, 22 insertions, 0 deletions

diff --git a/gitlab/issues/target_i386/host_missing/accel_missing/2008.toml b/gitlab/issues/target_i386/host_missing/accel_missing/2008.toml
new file mode 100644
index 000000000..d2c4f47d8
--- /dev/null
+++ b/gitlab/issues/target_i386/host_missing/accel_missing/2008.toml
@@ -0,0 +1,22 @@
+id = 2008
+title = "querying smbios type=1 UUID in Windows not possible when using SMBIOS 64 bit entry"
+state = "closed"
+created_at = "2023-11-28T14:44:32.801Z"
+closed_at = "2024-03-18T10:34:30.833Z"
+labels = ["guest: Windows", "target: i386"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/2008"
+host-os = "Proxmox VE 8 (but using upstream build of QEMU)"
+host-arch = "x86"
+qemu-version = "QEMU emulator version 8.1.0 (v8.1.0)"
+guest-os = "Windows Server 2022 (also affects Windows Server 2019 and Windows 10)"
+guest-arch = "x86"
+description = """Querying the UUID in Powershell with
+`get-wmiobject win32_computersystemproduct | Select-Object -expandProperty UUID`
+will return no value. When using `-machine 'pc-i440fx-8.1,smbios-entry-point-type=32'` or `-machine 'pc-i440fx-8.0'` the command works as expected. When using `-machine 'pc-i440fx-8.0,smbios-entry-point-type=64'` the issue is also present.
+
+Commit bf376f3020dfd7bcb2c4158b4ffa85c04d44f56d changed the default for machine version 8.1, so that explains that part.
+
+It's not clear to me if this is a bug in QEMU or a bug/limitation of the guest OS when 64 bit entry is used by SMBIOS."""
+reproduce = "n/a"
+additional = """Originally reported for Windows 10 in the Proxmox VE community forum (AFAIK the downstream build in Proxmox VE does not patch the relevant code paths):
+https://forum.proxmox.com/threads/136942/"""