Startup issue with VEIN - GUID Crash

[John_Eastman]

Receiving the following when trying to start the server:

session crashguid > UECC-Windows-409FF0EE43352DDDF7AEC48DB7E2FA6B

OS Name/Version: Windows 10 Pro. Version 10.0.19045.6456

Virtualization: QEMU Virtual version 2.5+ with 13cores 13 threads and 16 GB ram allocated.

Application Name/Version: Vein 0.0.0.0:7777

Product: AMP ‘Phobos’ v2.6.3.2 (Mainline)

Running in container: no

Problem Description:

\LogAssetRegistry: Premade AssetRegistry loaded from '../../../Vein/AssetRegistry.bin'
\LogCsvProfiler: Display: Metadata set : platform="Windows"
\LogCsvProfiler: Display: Metadata set : config="Test"
\LogCsvProfiler: Display: Metadata set : buildversion="UE5-CL-0"
\LogCsvProfiler: Display: Metadata set : engineversion="5.4.4-0+UE5"
\LogCsvProfiler: Display: Metadata set : os="Windows 10 (22H2) [10.0.19045.6456] "
\LogCsvProfiler: Display: Metadata set : cpu="AuthenticAMD|QEMU Virtual CPU version 2.5+"
\LogCsvProfiler: Display: Metadata set : pgoenabled="0"
\LogCsvProfiler: Display: Metadata set : pgoprofilingenabled="0"
\LogCsvProfiler: Display: Metadata set : ltoenabled="0"
\LogCsvProfiler: Display: Metadata set : asan="0"
\LogCsvProfiler: Display: Metadata set : commandline=""-Port=7777 -QueryPort=27015 -stdout -FullStdOutLogOutput""
\LogCsvProfiler: Display: Metadata set : \loginid="removed for security"
\LogICUInternationalization: ICU TimeZone Detection - Raw Offset: -8:00, Platform Override: ''
\LogInit: Session CrashGUID >====================================================
         Session CrashGUID >   UECC-Windows-409FF0EE43352DDDF7AEC48DB7E2FA6B
         Session CrashGUID 

Steps to recreate:

1. Attempt to start instance and receive GUID crash in log.
2. Update instance then attempt to start instance results in same error.

Actions taken to resolve so far:

Reinstall server package via Windows and Docker. Other instances for servers are working perfectly. Only Vein is returning the GUID crash.

[Greelan]

VEIN is sensitive to the CPU type in VMs. Certain emulated CPUs don’t pass through all the flags needed. Best to run it in “host” mode so that all CPU flags are passed through

[John_Eastman]

Thank you for the quick response. I will try this solution out.