|# AWS P2 instance type has K80 GPUs, compute capability 3.7|
|# AWS P3 instance type has V100 GPUs, compute capability 7.0|
|# manually installed CUDA and cuDNN|
(I also reported this to AWS: https://github.com/awsdocs/amazon-ec2-user-guide/issues/123)
The "Running Amazon Linux 2 as a virtual machine onpremises" page describes a fairly cumbersome way of running Amazon Linux 2 in local virtual machines through using various tools to provision ISO9660
seed.iso files just to serve the VM instance two small data files.
It would be great it the documentation also pointed out that since the VM provisioning is being done with
cloud-init, and the image has configured a fairly extensive
datasource_list: [ NoCloud, AltCloud, ConfigDrive, OVF, None ] which starts with NoCloud, that NoCloud also allows you to serve these files over HTTP.
There are two easy ways of using network configuration instead of
seed.iso. Either you tell GRUB to add a parameter to the kernel boot configuration, or you tell KVM/VMWare/Virtualbox to set the virtual machine's SMBIOS value to something which
The documentation page https://cloudinit.readthedocs.
Proper CUDA and cuDNN installation
You're here, so you're probably already hurting because of CUDA and cuDNN compatibility, and I won't have to motivate you, or explain why you'd want to have standalone CUDA and cuDNN installations, if you're going to develop using Tensorflow in the long term.
1. Download your CUDA
runfile (local) packages
The Google official Java build in Maven Central is broken, and has been for quite a while.
Environment: AWS P2.xlarge instance with a K80 GPU and CUDA compute capability of 3.7.
Error: "Ignoring visible gpu device [...] The minimum required Cuda capability is 6.0."
Expected: The minimum CUDA compute capability is 3.5, like the documents state, and as the Python packages require.