Windows 10 VM only showing 1 Socket and 4 cores.

[sirtcp]

Dear All,

Hope you guys are doing good. i have been trying to setup a windows 10 VM on Proxmox. This proxmox box is also hosting other Windows Server VMs all other VMs are working perfectly fine base on Server 2016 OS. but 1 recently migrated Windows 10 VM showing only 1 socket and 4 cores no matter how much cores i assigned to it.
i tried every combination of socket and cores but no luck.
I tried changing the core in msconfig but no luck.
Would you guys please help why only this Windows 10 is showing this 4 core limits? am i doing something wrong. Default CPU type is KVM.

thanks,
Yousuf

 

[dcsapak]

did you stop + start the vm after the config change?

on a running vm you can edit the config but it is pending so long as the vm is running (note that a restart from within the vm is not enought to apply those changes, either a reboot from outside or a stop/start cycle)

 

[sirtcp]

Hi,
Yes i did that already, even i tried this mutiple time with multiple Core, socket and vcpu change. every time i change in CPU settings i stop/shutdown the VM, then started it again.

Thanks,

 

[oguz]

hi,

can you post your vm config: qm config VMID

and the output of get-wmiobject win32_processor on powershell?

also on powershell:

wmic cpu get deviceid,numberofcores,numberoflogicalprocessors

 

[sirtcp]

Thanks for the input, there is the output as requested.

 

[oguz]

can you post your vm config too?

 

[sirtcp]

Hi,

Here is the detail.

bootdisk: scsi0
cores: 4
ide2: none,media=cdrom
memory: 45000
name: MSTR-Prd-47
net2: rtl8139=8E:B2:52:18:BB:A0,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
parent: workin
sata0: mstr:vm-1001-disk-0,size=270G
sata1: mstr:vm-1001-disk-1,size=65G
scsihw: virtio-scsi-pci
smbios1: uuid=d9bda9a5-7aa2-49eb-831b-33ceedb31bd9
sockets: 4
vcpus: 16
vmgenid: e1792007-ea95-4252-90e8-f9b1ccd23774

Sorry for the extra details in config file share in the trail. i just edited the response and giving you the actual output of the requested command.

 

[sirtcp]

Hi,

Just to add some more information, you will see the number of Processors in left hand side from device manager output. but task manager is only showing 4. any help will be highly appreciated.

 

[oguz]

could you try 2 sockets and 8 cores?

also which version of windows 10 is this? home/pro etc.

 

[wigor]

silly question, did you use your right mouse button on the graphics and choose "show logical" cpu?

 

[dcsapak]

it seems that windows 10 home only supports 1 socket https://en.wikipedia.org/wiki/Windows_10_editions

 

[zepcs]

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: virtio=4A:34:72:F7A:34,bridge=vmbr0,tag=10
numa: 1
ostype: win10
scsi0: local-lvm:vm-106-disk-0,cache=writeback,discard=on,size=100G
scsi1: local-lvm:vm-106-disk-1,cache=writeback,discard=on,size=500G
scsihw: virtio-scsi-pci
smbios1: uuid=bfff21da-d337-499c-8f49-01584ac316b8
sockets: 2
vga: qxl
vmgenid: ee71994e-93b2-4221-bdf3-77cd7b34bcc0


get-wmiobject win32_processor
Caption : Intel64 Family 15 Model 6 Stepping 1
DeviceID : CPU0
Manufacturer : GenuineIntel
MaxClockSpeed : 2195
Name : Common KVM processor
SocketDesignation : CPU 0

wmic cpu get deviceid,numberofcores,numberoflogicalprocessors
DeviceID NumberOfCores NumberOfLogicalProcessors
CPU0 4 4

 

[sirtcp]

Hi,
@oguz, I change the settings to 2 CPU and 8 cores no luck. but the version i am using is Windows 10 Ent. this
@wigor, Yes i change it already, therefore its showing 4 graphs in the image
@dcsapak, Windows version is 10 enterprise.

Please note that after playing around with the machine even it get more worst. now it is showing two cores instead of 4. . it never happend to me before i dont know why it is happening this time. even on the same server there is server 2016 running with same CPUs i see no issues in core display. it is showing everything fine even load is also good.

Thanks,
Yousuf

 

[oguz]

here it works with windows 10 pro:



vm settings:

boot: cdn
bootdisk: sata0
sockets: 2
cores: 8
vcpus: 16
machine: q35
memory: 2048
name: win10
net0: e1000=D2:20:A1:E6:22:77,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
sata0: local-zfs:vm-2000-disk-0,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=46550eb5-1607-4e4d-a345-e767a9a24c8e
vmgenid: de882222-77b4-40db-bb49-9cd553716f0a

 

[sirtcp]

Thank for sharing, I think Enterprise is more higher version then Pro. It should have detected the correct configuration, though in my case it is not.

 

[oguz]

you can try setting the ostype variable to win10 and add machine: q35 then reboot the VM.

if that doesn't change anything please post pveversion -v output

also i noticed in your VM config you have bootdisk: scsi0 but you have sata0 and sata1 ? could you post the full config file with the snapshots as well?

 

[sirtcp]

Hi oguz,
Thanks for update, i did the changes you mentioned, unfortunately no luck.
regarding bootdisk: i did it on purpose i was doing some testing.

here is the output of pveversion - v
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

 

[zepcs]

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: 6.0-11
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.34-1-pve: 5.4.34-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.10-1-pve: 5.3.10-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-5
libpve-guest-common-perl: 3.1-2
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-9
pve-cluster: 6.1-8
pve-container: 3.1-12
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-11
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-11
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1

Previous Host:
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.34-1-pve: 5.4.34-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

My win10 instance was installed with the latest windows installer iso from the media creation tool, as welll as virtio-win-0.1.189.iso for drivers and agent.

 

[oguz]

honestly i have no idea, whichever configuration i try here worked normally...

you can try booting the VM with a linux live CD (just add any linux distro ISO as CD-ROM and change the boot order). then check if it recognizes the correct amount of CPU cores.

if it works on linux, then it's some windows specific setting/issue.

 

[zepcs]

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 120.2202.130.0