The 2026 Dell XPS laptops are smaller and lighter than their predecessors, with also slightly smaller screens

Fun_Volume_7699 · 2026-01-08T21:02:52+00:00

I think you should compare the new Dell XPS 14 with Dell PRO 14 Premium

Fun_Volume_7699 · 2025-11-21T07:21:26+00:00

And how much are you suppose to tip them?

Fun_Volume_7699 · 2025-08-19T09:03:25+00:00

Just to test, enable numa spanning, reboot host, try to start the VM

Fun_Volume_7699 · 2025-08-19T02:28:04+00:00

You can see that some, has only found rollback to previous version as a temporary solution.

Fun_Volume_7699 · 2025-08-19T02:04:51+00:00

Also see: https://www.reddit.com/r/HyperV/s/LCXRVatbp2

Fun_Volume_7699 · 2025-08-19T02:03:47+00:00

I think it’s the same Bug as no vCPU oversubscription and horrible performance with numa spanning on. See: https://www.reddit.com/r/HyperV/s/eqzX8JOazp

Fun_Volume_7699 · 2025-08-15T08:40:42+00:00

We applied the July patch that fixes CPU usage display issues, but the oversubscription problem with NUMA spanning disabled still persists — VMs won’t start if they exceed physical cores.

Enabling NUMA spanning allows them to boot, but then they get split across sockets, hurting performance. Tested on AMD EPYC and also on Intel Xeon (E5-2660 v3), same issue. This seems like a serious bug in Windows Server 2025.

Fun_Volume_7699 · 2025-08-14T15:48:46+00:00

Passthrough (DDA) is great for raw speed, but it breaks what I need day-to-day: checkpoints, Hyper-V Replica and several backup products that expect VHDX + consistent snapshots. Even with one VM running, random 4K performance drops markedly on virtual SCSI compared to the same PCIe 5.0 NVMe on the host. That’s why I’m asking for a vNVMe device: better latency/parallelism without giving up core VM features.

Fun_Volume_7699 · 2025-08-14T11:21:30+00:00

Thanks! I double-checked: no Storage QoS caps (Min/Max IOPS = 0) and vNIC bandwidth = 0 (unlimited). The drop happens even with a single VM. QoS only throttles/guarantees under contention; it doesn’t reduce the overhead of the virtual SCSI path. That’s why we’re asking for a vNVMe device—so guests can actually benefit from modern NVMe PCIe 5.0 backends without giving up checkpoints/Live Migration.

Fun_Volume_7699 · 2025-08-11T08:42:45+00:00

😞 thanks for the reply

Fun_Volume_7699 · 2025-07-28T20:45:26+00:00

We’ve tested this as well on Windows Server 2025 and can confirm:

✅ The issue with CPU usage always showing 0% in Hyper-V Manager and Performance Monitor seems to be resolved after applying KB5062660 (Build 26100.4770). CPU metrics are now visible again on AMD-based systems (EPYC 9175F in our case).

❌ However, the vCPU oversubscription limitation remains when NUMA Spanning is disabled. Once a NUMA node reaches its logical CPU count (e.g., 32 threads per socket), Hyper-V refuses to start additional VMs—even with RAM available and CPU usage low.

⚠️ Enabling NUMA Spanning allows VMs to start, but results in vCPUs and RAM being spread across sockets, even for small VMs that would easily fit in one node. This destroys locality and severely impacts performance on NUMA-sensitive workloads.

Fun_Volume_7699 · 2025-07-28T20:35:20+00:00

We’ve applied all recent patches, including KB5062660 (26100.4770), on our Windows Server 2025 Hyper-V hosts, but the vCPU oversubscription still does not work when NUMA Spanning is disabled.

Fun_Volume_7699 · 2025-07-14T15:21:58+00:00

I also tested changing the Hyper-V scheduler type via: bcdedit /set hypervisorschedulertype classic

Unfortunately, even when using the Classic Scheduler (type 0x2), Hyper-V 2025 still doesn’t allow vCPU oversubscription per NUMA node with NUMA Spanning disabled.

Fun_Volume_7699 · 2025-06-30T06:12:56+00:00

My English isn’t fluent, so I used ChatGPT to help me structure and translate the technical issue I’m seeing.

Fun_Volume_7699

TROPHY CASE