12代酷睿关闭小核心究竟能不能正常用vmware？

[quote][tid=31700053]Topic[/tid] Post by [uid=60366520]浅唱离歌笑[/uid] (2022-04-30 08:46):

大不了不用小核心了，这样行不行呢？
用vmware workstation嵌套ESXi呢？[/quote]不行[s:ac:吻]

不关小核都可以，电源模式开高性能就会跑到大核上，关小核肯定更没问题了。

[quote][pid=607098130,31700053,1]Reply[/pid] Post by [uid=37544749]datasone[/uid] (2022-04-30 08:59):

不关小核都可以，电源模式开高性能就会跑到大核上，关小核肯定更没问题了。[/quote]你试过了吗？楼上说不行？

[quote][pid=607097058,31700053,1]Reply[/pid] Post by [uid=63001228]wuzijq[/uid] (2022-04-30 08:52):

不行[s:ac:吻][/quote]不是，兄dei你正经点

[quote][pid=607109395,31700053,1]Reply[/pid] Post by [uid=60366520]浅唱离歌笑[/uid] (2022-04-30 10:04):

你试过了吗？楼上说不行？[/quote]泥潭云玩家多不是常识嘛[s:ac:哭笑]

不过刚好测试了一下，找了个 XP 虚拟机出来给了四核跑 P95，后台开了些程序所以小核占用一直在跳，12700H 是六大核，也就是前十二个框框。

总之：
虚拟机调度完全没问题，平衡模式可能会调度到小核，高性能模式什么时候都是大核；
虚拟机系统不影响调度，XP 这么老的玩意都没问题；
优先调度到不同的大核而不是超线程，并且会在一个核的两个超线程之间切换(后面这个不知道为啥了，不过反正对性能没有影响)。

12700K一直正常使用

[quote][pid=607116105,31700053,1]Reply[/pid] Post by [uid=37544749]datasone[/uid] (2022-04-30 10:39):

泥潭云玩家多不是常识嘛[s:ac:哭笑]

不过刚好测试了一下，找了个 XP 虚拟机出来给了四核跑 P95，后台开了些程序所以小核占用一直在跳，12700H 是六大核，也就是前十二个框框。

[collapse=最小化 VMWare 窗口后的占用]
[img]./mon_202204/30/9aQ17q-ix4uZeT3cS[/quote]主要是比较在意跑esxi....

vmware workstation嵌套ESXi是啥骚操作？

vmware workstation在windows11、Intel的12代CPU上使用没啥问题啊

[quote][pid=607502880,31700053,1]Reply[/pid] Post by [uid=603241]screamking[/uid] (2022-05-02 02:52):

vmware workstation嵌套ESXi是啥骚操作？

vmware workstation在windows11、Intel的12代CPU上使用没啥问题啊[/quote]实验环境要用到

ESXi
Let me start off by answering the question that I had posed at the beginning of this article on whether the ESXi CPU Scheduler understands the new Intel Alder Lake hybrid CPU architecture? The short answer is no, ESXi is currently not aware of this new architecture and it currently expects all cores within a CPU package to have uniform characteristics.

In fact, if you attempt to boot ESXi on an Alder Lake CPU, it will actually PSOD (Purple Screen of Death) and you will see a message about "Fatal CPU mismatch on feature" which is due to the different CPU properties across both the P-Cores and E-Cores. Luckily, there is a workaround to disable the CPU uniformity check that ESXi performs as part of its boot up and the following kernel option cpuUniformityHardCheckPanic=FALSE can be added during the boot up (SHIFT+O during boot up or simply add it to boot.cfg when creating your ESXi bootable installer).

Note: Once ESXi has been successfully installed, you can permanently set the kernel option by running the following ESXCLI command: esxcli system settings kernel set -s cpuUniformityHardCheckPanic -v FALSE

Below is a screenshot running the latest ESXi 7.0 Update 3 release on the Intel NUC 12 Extreme, which does require the Community Networking Driver for ESXi Fling (at least v.1.2.5) for proper networking functionality.


Although we can workaround the PSOD, this is more of a hack since we really do not know what the behavior will be, since the ESXi CPU Scheduler was never designed to work with this new CPU architecture. From my very limited amount of testing, running a Windows VM and other basic workloads, I have not seen any significant difference, but it may vary based on the type and number of workloads. One thing I did notice was that ESXi was using the P-Core base frequency which in my setup was 2.40Ghz where as the E-Core base frequency is 1.80Ghz. With more workloads running, in theory you could see mixed performance if a single workload is getting scheduled between the two different types cores.

Although it is unclear whether this new type of CPU architecture will get adopted in the Enterprise datacenter, but we can certainly expect to see this trend continue in the consumer space which also includes Apple's recent Apple Silicon processors. I can definitely see the benefits of this type of hybrid CPU architecture benefiting Edge deployments and perhaps that is the next logical segment to see some form of Enterprise support?

[quote][pid=607117261,31700053,1]Reply[/pid] Post by [uid=1509129]缠绕指[/uid] (2022-04-30 10:45):

12700K一直正常使用[/quote]12700k跑esxi没有问题吗？