[SOLVED] Unable to run 3DMark in my VM

Operating Systems & Open Source Virtualization
1

I had 3DMark running flawlessly under my AM4 VM, and was able to run multiple benchmarks, before upgrading.

I upgraded to AM5, and again I was able to run 3DMark again, and compare my two systems.

However, when I started changing things to my XML, while trying to make PUBG run (Hyper-V, etc), I must have broken something that blocks 3DMark from running.

I have the Steam version (full) and when I click the “Timelapse” benchmark to runs, it “Collects system information” forever… I left it over 30 minutes in case it is just slow, but was still stuck there.

Anybody had similar issue and fixed it?

Anybody knows any setting that might prevent it from running?

Below are the things I changed while experimenting:

  <cpu mode="host-passthrough" check="none" migratable="off">
    <topology sockets="1" dies="1" cores="8" threads="2"/>
    <cache mode="passthrough"/>
    <feature policy="disable" name="x2apic"/>
    <feature policy="require" name="tsc-deadline"/>
    <feature policy="require" name="tsc_adjust"/>
    <feature policy="require" name="arch-capabilities"/>
    <feature policy="require" name="rdctl-no"/>
    <feature policy="require" name="skip-l1dfl-vmentry"/>
    <feature policy="require" name="mds-no"/>
    <feature policy="require" name="pschange-mc-no"/>
    <feature policy="require" name="topoext"/>
    <feature policy="disable" name="svm"/>
    <feature policy="require" name="hypervisor"/>
    <feature policy="require" name="amd-stibp"/>
    <feature policy="require" name="invtsc"/>
    <feature policy="require" name="ibpb"/>
    <feature policy="require" name="virt-ssbd"/>
    <feature policy="require" name="pdpe1gb"/>
    <feature policy="require" name="cmp_legacy"/>
    <feature policy="require" name="xsaves"/>
    <feature policy="require" name="perfctr_core"/>
    <feature policy="require" name="clzero"/>
    <feature policy="require" name="xsaveerptr"/>
  </cpu>
  <clock offset="timezone" timezone="Europe/Dublin">
    <timer name="rtc" present="no" tickpolicy="catchup"/>
    <timer name="pit" tickpolicy="discard"/>
    <timer name="hpet" present="no"/>
    <timer name="kvmclock" present="no"/>
    <timer name="hypervclock" present="yes"/>
    <timer name="tsc" present="yes" mode="native"/>
  </clock>
1 Like
2

I can not answer on this particular problem, which setting keeps it from running, but I can tell you that I have been having trouble with 3DMark in VMs for ages. For me it starts to run, but for example Time Spy crashes every single run, I have not been able to make it run properly for the last two years. Everything else is perfectly stable, the host runs fine and even the VMs can do anything else, Cinebench, Prime95, regular tasks like gaming, not problem at all. Only 3DMark crashes. So, what I am trying to say, if you can’t figure it out, don’t worry, use different benchmarks instead.

1 Like
3

I don’t mind the actual benchmark, I just want to compare with my previous setup, to see what I gained. The thing is it was working, I was able to run full suite, with a small delay on loading (compared to barebone).

4

I removed most entries, and also uninstalled Hyper-V. Still gets stuck while collecting system information…

  <cpu mode="host-passthrough" check="none" migratable="off">
    <topology sockets="1" dies="1" cores="8" threads="2"/>
    <cache mode="passthrough"/>
    <feature policy="disable" name="x2apic"/>
    <feature policy="require" name="topoext"/>
    <feature policy="require" name="svm"/>
    <feature policy="require" name="hypervisor"/>
    <feature policy="require" name="amd-stibp"/>
  </cpu>
5

Just noticed that AIDA64 also has problems… It reports “unknown” with no results in all CPU/Memory benchmarks… Also this was working before

6

Disable the system info in the settings. You won’t get valid score, but you can compare and tinker as you’ll know your own baseline.

Mind you, some virtual clock settings will skew the results, resulting in inaccurate FPS readings and higher scores.

1 Like
7

Tried that, doesn’t work either. Getting a prompt “Benchmark running” but stays there forever.

8

Eh, mine works but I’m on older AMD platform (Milan), my clocks are the same (kvmclock is not defined so it should be off like yours) and only following cpu features:

<feature policy='disable' name='x2apic'/>
<feature policy='require' name='topoext'/>
<feature policy='disable' name='svm'/>
<feature policy='disable' name='hypervisor'/>

HyperV options are

<hyperv mode='custom'>
  <relaxed state='on'/>
  <vapic state='on'/>
  <spinlocks state='on' retries='8191'/>
  <vpindex state='on'/>
  <synic state='on'/>
  <stimer state='on'>
    <direct state='on'/>
  </stimer>
  <reset state='on'/>
  <vendor_id state='on' value='1234567890ab'/>
  <frequencies state='on'/>
  <reenlightenment state='off'/>
  <tlbflush state='on'/>
  <ipi state='on'/>
  <evmcs state='off'/>
  <avic state='on'/>
</hyperv>

but tbh, I have no idea what those mean / do.

1 Like
9

Thanks for that!
I applied these setting, with mode “passthrough” instead of “custom” and now it works!

<hyperv mode='passthrough'>
  <relaxed state='on'/>
  <vapic state='on'/>
  <spinlocks state='on' retries='8191'/>
  <vpindex state='on'/>
  <synic state='on'/>
  <stimer state='on'>
    <direct state='on'/>
  </stimer>
  <reset state='on'/>
  <vendor_id state='on' value='OriginalAMD'/>
  <frequencies state='on'/>
  <reenlightenment state='off'/>
  <tlbflush state='on'/>
  <ipi state='on'/>
  <evmcs state='off'/>
  <avic state='on'/>
</hyperv>

Maybe, if I have time I will start removing one by one to find out which ones make a difference.

1 Like
10

Not re-opening, but it fails again…
Not changed anything on my XML, just regular update on my system, OSes and software.
Also, I noticed that AIDA64 fails to benchmark everything, while it was working before.

If anybody can shed some light I would appreciate it. In any other case, I won’t bother anymore.