Aleksandr Lykhouzov (Oct 20 2022 at 20:51): Aleksandr Lykhouzov (Oct 20 2022 at 20:51):I am using wasamtime-cpp version, with azerothcore c++ project. I finally was able to compile it, but now when I run the server on ovh server(dedicated) i am getting following error
wow-worldserver-1 | thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Unsupported feature: SIMD support requires SSE3, SSSE3, SSE4.1, and SSE4.2 on x86_64.', crates/wasmtime/src/engine.rs:538:41
wow-worldserver-1 | stack backtrace:
wow-worldserver-1 | 0: 0x7f9fb31331ad - std::backtrace_rs::backtrace::libunwind::trace::h9135f25bc195152c
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
wow-worldserver-1 | 1: 0x7f9fb31331ad - std::backtrace_rs::backtrace::trace_unsynchronized::h015ee85be510df51
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
wow-worldserver-1 | 2: 0x7f9fb31331ad - std::sys_common::backtrace::_print_fmt::h5fad03caa9652a2c
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/sys_common/backtrace.rs:66:5
wow-worldserver-1 | 3: 0x7f9fb31331ad - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h2b42ca28d244e5c7
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/sys_common/backtrace.rs:45:22
wow-worldserver-1 | 4: 0x7f9fb31571dc - core::fmt::write::h401e827d053130ed
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/fmt/mod.rs:1198:17
wow-worldserver-1 | 5: 0x7f9fb312fe71 - std::io::Write::write_fmt::hffec93268f5cde32
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/io/mod.rs:1672:15
wow-worldserver-1 | 6: 0x7f9fb31349a5 - std::sys_common::backtrace::_print::h180c4c706ee1d3fb
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/sys_common/backtrace.rs:48:5
wow-worldserver-1 | 7: 0x7f9fb31349a5 - std::sys_common::backtrace::print::hd0c35d18765761c9
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/sys_common/backtrace.rs:35:9
wow-worldserver-1 | 8: 0x7f9fb31349a5 - std::panicking::default_hook::{{closure}}::h1f023310983bc730
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:295:22
wow-worldserver-1 | 9: 0x7f9fb31346c1 - std::panicking::default_hook::h188fec3334afd5be
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:314:9
wow-worldserver-1 | 10: 0x7f9fb3134f36 - std::panicking::rust_panic_with_hook::hf26e9d4f97b40096
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:698:17
wow-worldserver-1 | 11: 0x7f9fb3134e27 - std::panicking::begin_panic_handler::{{closure}}::hfab912107608087a
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:588:13
wow-worldserver-1 | 12: 0x7f9fb31336a4 - std::sys_common::backtrace::__rust_end_short_backtrace::h434b685ce8d9965b
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/sys_common/backtrace.rs:138:18
wow-worldserver-1 | 13: 0x7f9fb3134b59 - rust_begin_unwind
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:584:5
wow-worldserver-1 | 14: 0x7f9fb2aaa123 - core::panicking::panic_fmt::ha6dc7f2ab2479463
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/panicking.rs:142:14
wow-worldserver-1 | 15: 0x7f9fb2aaa273 - core::result::unwrap_failed::h42ad8e915aa0a906
wow-worldserver-1 | at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/result.rs:1814:5
wow-worldserver-1 | 16: 0x7f9fb2cc1607 - <wasmtime::engine::Engine as core::default::Default>::default::h1320f23871b82310
wow-worldserver-1 | 17: 0x7f9fb2b6e6b1 - wasm_engine_new
wow-worldserver-1 | 18: 0x46f9da - _ZN10WASMPlayerC2Ev
wow-worldserver-1 | 19: 0x46f989 - _Z20AddWASMPlayerScriptsv
wow-worldserver-1 | 20: 0xf076ed - _ZN9ScriptMgr10InitializeEv
wow-worldserver-1 | 21: 0x43c064 - main
wow-worldserver-1 | 22: 0x7f9fb1f24d0a - __libc_start_main
wow-worldserver-1 | 23: 0x43b28a - _start
wow-worldserver-1 | 24: 0x0 - <unknown>
wow-worldserver-1 | fatal runtime error: failed to initiate panic, error 5
wow-worldserver-1 | Caught signal 6
on my mac or pc it works correctly, I mean, the server does not throw the error.
To run the server, i built it in docker, so I would say the only cpu is different
Could you give a hit is it possible to fix it? maybe some config or so?
PS: CPU model on server
debian@wow:~/wow$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 54
model name : Intel(R) Atom(TM) CPU N2800 @ 1.86GHz
stepping : 1
microcode : 0x10d
cpu MHz : 800.028
cache size : 512 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm arat
bugs :
bogomips : 3733.50
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
It looks like at least sse4.1 is missing on the server, and I believe you can fix this by using .wasm_simd(false) on Config
Aleksandr Lykhouzov (Oct 20 2022 at 21:10):Thanks, @Alex Crichton I will try that config.
Chris Fallin (Oct 20 2022 at 21:18):to add a little more detail here: our eventual goal is to be able to support Wasm-SIMD on all x86-64 cores, where the only guarantee is SSE2. This hasn't taken a very high priority so far (in the abstract we'd like to have everything, but we have way too much work to do so stuff needs concrete motivation). I'm actually kind of surprised to see a machine in the wild in the cloud somewhere without SSE4, but that's good to know, thanks! (cc @Andrew Brown as we've talked about this previously)
Andrew Brown (Oct 20 2022 at 21:32):Yeah, interesting... looks like that is an 11-year old machine. Sort of surprised OVH is hosting with that kind of chip?
Aleksandr Lykhouzov (Oct 20 2022 at 21:37):@Andrew Brown exactly, that is hosted as a cheap dedicated server. a friend of mine found it, I am not sure how :)
Aleksandr Lykhouzov (Oct 20 2022 at 22:12):So, FYI, that config fixed my issue. so thank you @Alex Crichton for the help
Notification Bot (Oct 20 2022 at 22:12):Aleksandr Lykhouzov has marked this topic as resolved.
Last updated: Oct 23 2024 at 20:03 UTC