F5F Stay Refreshed Software Operating Systems Incorrect CPU data in QEMU/KVM setup

Incorrect CPU data in QEMU/KVM setup

Incorrect CPU data in QEMU/KVM setup

Pages (3): 1 2 3 Next
M
maxwell4947
Junior Member
29
11-16-2016, 09:06 PM
#1
I set up Windows 10 on KVM via virt-manager with host OS Arch Linux and integrated graphics pass-through. It worked initially, but the CPU performance is poor and it incorrectly reports the CPU model as AMD Opteron G5. In reality, I have an A10-7850K on a Kaveri architecture. The guest sees only one core, even though I selected four. The GPU looks close to native speed, but the CPU is extremely slow compared to VirtualBox or VMware. Please help with this confusing situation. My English is not great.
M
maxwell4947
11-16-2016, 09:06 PM #1

I set up Windows 10 on KVM via virt-manager with host OS Arch Linux and integrated graphics pass-through. It worked initially, but the CPU performance is poor and it incorrectly reports the CPU model as AMD Opteron G5. In reality, I have an A10-7850K on a Kaveri architecture. The guest sees only one core, even though I selected four. The GPU looks close to native speed, but the CPU is extremely slow compared to VirtualBox or VMware. Please help with this confusing situation. My English is not great.

B
Bear_Clawz
Junior Member
8
11-18-2016, 07:17 PM
#2
My comes up as opteron too, I never looked into it. It's likely the settings you have it as 4 sockets, not 4 cores. If this is correct it should not be difficult to correct it. If you are using windows Home it won't work on more than one socket, I dont know if pro or ent has a limit.
B
Bear_Clawz
11-18-2016, 07:17 PM #2

My comes up as opteron too, I never looked into it. It's likely the settings you have it as 4 sockets, not 4 cores. If this is correct it should not be difficult to correct it. If you are using windows Home it won't work on more than one socket, I dont know if pro or ent has a limit.

L
LadyBiscoito
Member
111
11-18-2016, 07:22 PM
#3
Windows 10 Home is being detected as a virtual machine in Task Manager under CPU. It lists one socket, one virtual processor, and the VM status is enabled.
L
LadyBiscoito
11-18-2016, 07:22 PM #3

Windows 10 Home is being detected as a virtual machine in Task Manager under CPU. It lists one socket, one virtual processor, and the VM status is enabled.

A
AlphaMale_
Member
62
11-27-2016, 12:01 AM
#4
theres your problem. change your settings so its 4 cores not 4 sockets. The windows Home license and technology restrictions dont give you much to play with, thats why its cheaper.
A
AlphaMale_
11-27-2016, 12:01 AM #4

theres your problem. change your settings so its 4 cores not 4 sockets. The windows Home license and technology restrictions dont give you much to play with, thats why its cheaper.

S
Superlettuce19
Senior Member
370
11-27-2016, 08:39 AM
#5
It uses four cores instead of four sockets. It was set by default, but I adjusted it to one socket with four cores, while keeping four cores active continuously. The issue remains—CPU usage stays near 100% and the system runs choppy.
S
Superlettuce19
11-27-2016, 08:39 AM #5

It uses four cores instead of four sockets. It was set by default, but I adjusted it to one socket with four cores, while keeping four cores active continuously. The issue remains—CPU usage stays near 100% and the system runs choppy.

L
lhpostal
Junior Member
11
11-27-2016, 03:35 PM
#6
drivers?
L
lhpostal
11-27-2016, 03:35 PM #6

drivers?

J
jordi1218
Member
105
11-28-2016, 04:07 AM
#7
Which distribution? GT210 with NVIDIA 340xx drivers for host and integrated R7 graphics. Works well with VM. All packages updated, kernel 4.10.13. Latest AMD drivers on Windows guest. Linux Radeon drivers are blocked, IOMMU is set up correctly.
J
jordi1218
11-28-2016, 04:07 AM #7

Which distribution? GT210 with NVIDIA 340xx drivers for host and integrated R7 graphics. Works well with VM. All packages updated, kernel 4.10.13. Latest AMD drivers on Windows guest. Linux Radeon drivers are blocked, IOMMU is set up correctly.

I
ImKilleR_
Junior Member
40
11-29-2016, 09:37 AM
#9
I set up most of them, but none relate to the CPU. What they list are: Spoiler NetKVM/: Virtio Network driver viostor/: Virtio Block driver vioscsi/: Virtio SCSI driver viorng/: Virtio RNG driver vioser/: Virtio serial driver Balloon/: Virtio Memory Balloon driver qxl/: QXL graphics driver for Windows 7 and earlier (build virtio-win-0.1.103-1 and later) qxldod/: QXL graphics driver for Windows 8 and later (build virtio-win-0.1.103-2 and later) pvpanic/: QEMU pvpanic device driver (build virtio-win-0.1.103-2 and later) guest-agent/: QEMU Guest Agent 32bit and 64bit MSI installers qemupciserial/: QEMU PCI serial device driver *.vfd: VFD floppy images for use during installation of Windows XP
I
ImKilleR_
11-29-2016, 09:37 AM #9

I set up most of them, but none relate to the CPU. What they list are: Spoiler NetKVM/: Virtio Network driver viostor/: Virtio Block driver vioscsi/: Virtio SCSI driver viorng/: Virtio RNG driver vioser/: Virtio serial driver Balloon/: Virtio Memory Balloon driver qxl/: QXL graphics driver for Windows 7 and earlier (build virtio-win-0.1.103-1 and later) qxldod/: QXL graphics driver for Windows 8 and later (build virtio-win-0.1.103-2 and later) pvpanic/: QEMU pvpanic device driver (build virtio-win-0.1.103-2 and later) guest-agent/: QEMU Guest Agent 32bit and 64bit MSI installers qemupciserial/: QEMU PCI serial device driver *.vfd: VFD floppy images for use during installation of Windows XP

T
Totomop
Junior Member
25
11-29-2016, 10:20 AM
#10
When using kvm, you cannot assign all your cores to a virtual machine— the host must have at least one core running. Try a setup with one socket and three cores.
T
Totomop
11-29-2016, 10:20 AM #10

When using kvm, you cannot assign all your cores to a virtual machine— the host must have at least one core running. Try a setup with one socket and three cores.

Pages (3): 1 2 3 Next