starting with the last one (Intel Core i7-6700K) and working your way to the first one (Intel Xeon X5482 3.20GHz). For reference, here are some more information about the CPU profile chosen:
CPU Date Class Family
--------------------------------------------------------
Xeon X5482 3.20GHz Q4'07 Server Harpertown
Core i7-2635QM Q1'11 Mobile Sandy Bridge
Core i7-3960X Q4'11 Desktop Sandy Bridge E
Core i5-3570 Q2'12 Desktop Ivy Bridge
Core i7-5600U Q1'15 Mobile Broadwell
Core i7-6700K Q3'15 Desktop Skylake
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
I'm on the market for a workstation, and it seems that all the CPUs offered have the same problem reported here.
Since I did not see any replies after socratis', can anybody confirm that the --cpu-profile command works with the following configurations?
1. Host running Ubuntu, guest running Win 7 Pro
2. Host running Windows 10 Pro, guest running Win 7 Pro
Also, does this work independently of the host CPU architecture, such as when the host is running i7, i9, or newer AMDs like the RYZEN?
shortpasta wrote:I'm on the market for a workstation, and it seems that all the CPUs offered have the same problem reported here.
Since I did not see any replies after socratis', can anybody confirm that the --cpu-profile command works with the following configurations?
1. Host running Ubuntu, guest running Win 7 Pro
2. Host running Windows 10 Pro, guest running Win 7 Pro
Also, does this work independently of the host CPU architecture, such as when the host is running i7, i9, or newer AMDs like the RYZEN?
But there should be nothing special about Win 7 Pro + i5, so why did you have to do this?
And which cpu profile did you use?