Antithesis CPUID info
These are the reported properties of the simulated CPU in the Antithesis environment. If your software assumes or requires a specific modern CPU feature, check the flags list by running the cpuid command in the Antithesis environment to see if we support it out of the box.
For convenience, here are the feature flags it will report:
processor : 0vendor_id : GenuineIntelcpu family : 6model : 85model name : Antithesis VM v1stepping : 7cpu MHz : [VARIES BASED ON ANTITHESIS CONFIGURATION]cache size : 33792 KBphysical id : 0siblings : 1core id : 0cpu cores : 1apicid : 0initial apicid : 0fpu : yesfpu_exception : yescpuid level : 22wp : yesflags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht pbe syscall nx pdpe1gb lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq dtes64 ds_cpl ssse3 sdbg fma cx16 xtpr pcid dca sse4_1 sse4_2 movbe popcnt aes xsave avx f16c hypervisor lahf_lm abm 3dnowprefetch cat_l3 cdp_l3 invpcid_single mba fsgsbase bmi1 avx2 bmi2 erms invpcid avx512f avx512cd xsaveopt aratbugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_stale_data retbleedbogomips : [VARIES BASED ON ANTITHESIS CONFIGURATION]clflush size : 64cache_alignment : 64address sizes : 46 bits physical, 48 bits virtualpower management:As noted in our security whitepaper every Antithesis customer runs on separate and dedicated physical infrastructure, so there is no risk of data exfiltration due to CPU vulnerabilities caused by shared microarchitectural state.