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

pulled cudaQ docker but porblem with cuda. #1681

Open
3 of 4 tasks
giladqm opened this issue May 15, 2024 · 7 comments
Open
3 of 4 tasks

pulled cudaQ docker but porblem with cuda. #1681

giladqm opened this issue May 15, 2024 · 7 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@giladqm
Copy link

giladqm commented May 15, 2024

Required prerequisites

  • Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
  • Make sure you've read the documentation. Your issue may be addressed there.
  • Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
  • If possible, make a PR with a failing test to give us a starting point to work on!

Describe the bug

I'm using a GraceHopper with aarch64.
I pulled the docker:
docker pull nvcr.io/nvidia/nightly/cuda-quantum:latest
Then ran the container:
docker run --gpus all -it nvcr.io/nvidia/nightly/cuda-quantum:latest
I tried to run one one of the notebooks (deutschs_algorithm.ipynb) and got the error:
ImportError: [custatevec] %the operation cannot be performed in the present state in CuStateVecCircuitSimulator (line 334)

while trying to "import cudaq"

Steps to reproduce the bug

I pulled the docker:
docker pull nvcr.io/nvidia/nightly/cuda-quantum:latest
Then ran the container:
docker run --gpus all -it nvcr.io/nvidia/nightly/cuda-quantum:latest
I tried to run one one of the notebooks (deutschs_algorithm.ipynb) and got the error:
ImportError: [custatevec] %the operation cannot be performed in the present state in CuStateVecCircuitSimulator (line 334)

while trying to "import cudaq"

Expected behavior

I expected the code to run smoothly.

Is this a regression? If it is, put the last known working version (or commit) here.

Not a regression

Environment

  • CUDA Quantum version:
  • Python version:
  • C++ compiler:
  • Operating system:

Suggestions

No response

@bmhowe23
Copy link
Collaborator

Hi @giladqm - can you please run the nvidia-smi command from within the Docker container and paste the results here?

@giladqm
Copy link
Author

giladqm commented May 15, 2024 via email

@bmhowe23
Copy link
Collaborator

That image did not come through. You may have to post it directly on the GitHub website rather than via email.

@giladqm
Copy link
Author

giladqm commented May 15, 2024

nvidia-smi

@bmhowe23
Copy link
Collaborator

I verified that I can run the latest container on our GH200. (One possible difference is that we don't have MIG enabled, and it looks like maybe you do?) In any case, would it be possible to test with another NVIDIA container from https://catalog.ngc.nvidia.com/orgs/nvidia/teams/k8s/containers/cuda-sample? It should run like this:

$ docker pull nvcr.io/nvidia/k8s/cuda-sample:vectoradd-cuda11.7.1
$ docker run --rm --gpus all nvcr.io/nvidia/k8s/cuda-sample:vectoradd-cuda11.7.1
[Vector addition of 50000 elements]
Copy input data from the host memory to the CUDA device
CUDA kernel launch with 196 blocks of 256 threads
Copy output data from the CUDA device to the host memory
Test PASSED
Done

@giladqm
Copy link
Author

giladqm commented May 15, 2024 via email

@giladqm
Copy link
Author

giladqm commented May 15, 2024

image

@schweitzpgi schweitzpgi added bug Something isn't working documentation Improvements or additions to documentation labels Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants