Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WAMR failed to create compilation context: Error: SIMD compatibility check failed, try adding --cpu=<cpu> to specify a cpu or adding --disable-simd to disable SIMD #787

Open
WhaleSpring opened this issue Aug 25, 2023 · 4 comments

Comments

@WhaleSpring
Copy link

When I try to upload a function's .wasm file to k8s faasm cluster,I get response value 500 . And the logs of pod upload are as follows:
image
image
Using "faaasmctl upload.wasm" order has the same mistake.

@csegarragonz
Copy link
Collaborator

Hi @github-jyq thanks for using Faasm!

How have you generated the WASM file? This is, what compilation toolchain have you used?

Have you used Faasm's C++ toolchain?

Otherwise, it is unlikely that Faasm will be able to run arbitrary WASM.

@WhaleSpring
Copy link
Author

WhaleSpring commented Aug 27, 2023

Thank you for your answer @csegarragonz . Ofcourse I used the toolchain provided by faasm, for the reason that I just run the orders in Quick start document except that I use "faasmctl deploy.k8s" instead compose.

@csegarragonz
Copy link
Collaborator

I see, could you please paste here the exact commands that you use to get to the error?

Bear in mind that faasmctl deploy.k8s assumes that a k8s cluster already exists somewhere and the KUBECONFIG env. variable is set (see here).

@WhaleSpring
Copy link
Author

WhaleSpring commented Aug 29, 2023

My detailed and complete process for obtaining the above errors is as follows:
Before deploying faasm on my k8s cluster, I first deployed metallb, the implementation of the load balancer, on my cluster to support for load balancing components of faasm.
At first, I deploy faasm in k8s cluster:
faasmctl deploy.k8s
image
And the output indicates that the deployment is correct:
image
Then I set the environment variable to make the faasmctl tool recognize the initialization file of the faasm service
export FAASM_INI_FILE=./faasm.ini
After that, I run the cpp-cli container:
faasmctl cli.cpp
image
Compile the func hello:
inv func demo hello
image
At last, I try to upload the func hello, and get wrong response:
inv func.upload demo hello
image
Viewing the logs of the pod upload , I will see the wrong message mentioned above:
kubectl logs -n faasm upload
image

It's worth mentioned that if I copy the hello.wasm file from cpp-cli container to the master host, and use order faasmctl upload.wasm user hello /root/demo/hello.wasm to upload , I will get the same response 500 in cmd and simd mistake in upload pod's logs.

The system of my servers is Ubuntu 22.04.3 LTS with architecture x86_64.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants