After getting it to finally boot, it shows 1 socket and 2 cores but finally shows Sandy Bridge as the model. Going to revert the change and see what happens.
There was no core options, only number of processors which I set to 2 since I have 2 sockets currently configured. It is unable to boot currently, trying to get in with the iso to reset that back. This was only a temporary vm while I wait on a replacement system and it has been a pain from the...
Here is what the Boot Advanced shows currently, have not made changes to it.
lscpu on the host:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 46 bits physical, 48 bits virtual
CPU(s): 32
On-line CPU(s)...
I just booted an 18.04 iso and indeed saw the correct cpu model as well as core count. Something windows related for sure, here is the versions I see in my win10
Edition: Windows 10 Pro
Version: 2004
Installed on: 8/12/2020
OS Build: 19041.388
Experience: Windows Feature Experience Pack...
Here is mine as well, I even updated and rebooted one of my hosts to see if it would change.
Current Host:
proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve)
pve-manager: 6.2-10 (running version: 6.2-10/a20769ed)
pve-kernel-5.4: 6.2-4
pve-kernel-helper: 6.2-4
pve-kernel-5.3: 6.1-6
pve-kernel-5.0...
Having the same issue here as well. Windows 10 Pro. The cpu model also is not changing from Common KVM in my case. I have tried 1 socket and 8 cores with the same result.
agent: 0
boot: cdn
bootdisk: scsi0
cores: 4
cpu: SandyBridge
memory: 8192
name: bi
net0...
We recently had this same "problem", glad to see it was only a problem in status display. We couldn't figure it out, even went as far as to start looking for alternatives.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.