Description: I set up an AWS EC2 Windows Server 2019 instance. The instance I used is g4dn GPU instance class
Purpose: I want to use this instance for 3d modeling
Problem: When I open the 3d software. It says opengl 2.0 not supported by your system
My failed "solutions":
Install Nvidia driver. As I initially thought it's because GPU is not present
Use teamviewer. Based on online tutorial. They say connecting to Windows instance via RDP, the default opengl is 1.1, and teamviewer will resolve that. However, when I connect using teamviewer and check, the opengl is still 1.1
I tried AWS AMI Windows server 2019 with driver installed. However, it has the same problem as the instance I manually setup
Related
I have laptop with NVIDIA Quadro T2000 GPU but this GPU is not support with the Omniverse.[see screenshot]
So I am trying with creating AWS EC2 Instance with G4dn.2xlarge instance type with windows server 2022.
Note: I want to Omniverse XR which only support Windows OS.
After creating EC2 instance in AWS, I have install NVIDIA driver from https://www.nvidia.com/Download/index.aspx .
Driver Details are as follows:
Product Type: Tesla
Product Series: T-series
Product: Tesla T4
Operating System: Windows 10
CUDA Toolkit:11.7
Driver is successfully installed I can see the status of installed, But still when I am trying to open any app in Omniverse, for ex. Omniverse create/XR, each and every app got crashed as soon as we launch.
I can see following logs in the terminal:
Image
I exported a custom VirtualBox (Ubuntu 12.04, 32bit)image and want to recreate this in Azure.
I converted the image to VHD and uploaded it to storage blobs. But when I want to create a new Azure Image from this blob, I get the error 'Only blobs formatted as VHDS are supported'
I also tried installing VirtualBox into an new Azure Vm and running the image there, but the VirtualBox seems to overtake the Network from the Azure VM and therefore disconnecting it.
I read that Azure VM doesn't even support Linux 32bit versions. https://support.microsoft.com/en-us/help/4021388/support-for-32-bit-operating-systems-in-azure-virtual-machines
Did anyone ever run into this problem and have a solution?
Yeah, Azure doesn't support 32 bit OSs so you'll need to do 64 bit, or, another option, you can run a VM that supports Nested Virtualization, in which case you can run a 32 bit VM on top of that.
I want a Windows 10 x64 Professional hosted on AWS, is that possible? And if so, how might one go about it?
To expound.
I just want a real windows 10 environment hosted remotely with static IP address so i can use it like a personal computer + server for some dev stuffs.
This is likely what you are looking for:
https://aws.amazon.com/workspaces/
Amazon WorkSpaces is a managed, secure cloud desktop service. You can
use Amazon WorkSpaces to provision either Windows or Linux desktops in
just a few minutes and quickly scale to provide thousands of desktops
to workers across the globe. You can pay either monthly or hourly,
just for the WorkSpaces you launch, which helps you save money when
compared to traditional desktops and on-premises VDI solutions. Amazon
WorkSpaces helps you eliminate the complexity in managing hardware
inventory, OS versions and patches, and Virtual Desktop Infrastructure
(VDI), which helps simplify your desktop delivery strategy. With
Amazon WorkSpaces, your users get a fast, responsive desktop of their
choice that they can access anywhere, anytime, from any supported
device.
and this is how you can give it a static ip:
https://aws.amazon.com/premiumsupport/knowledge-center/associate-elastic-ip-workspace/
Edit:
Amazon WorkSpaces now offers bundles that come with a Windows 10
desktop experience, powered by Windows Server 2016. Amazon WorkSpaces
Windows 10 bundles provides you an easy way to move users to a modern
operating system, while also simplifying licensing. Amazon WorkSpaces
continues to offer bundles that come with a Windows 7 desktop
experience, provided by Windows Server 2008 R2. You can also run
Windows 7 and Windows 10 Enterprise operating systems with Amazon
WorkSpaces if your organization meets the licensing requirements set
by Microsoft.
#BrownChiLD
You can create your own AMI on AWS. Steps are below:
1. create the machine on your system by using vmware wokrstation or hyper-v
2. Export the VM
3. Upload it to S3 bucket
once your vm is uploaded to S3, follow the steps on the below link
https://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-image-import.html#import-vm-image
At present time the only way to achieve what you want is by spinning your own Win10 instance assigning the static internal IP while creating it or by adding an Elastic IP if it's in an Internet Gateway enabled subnet.
It's not that convenient, you'll need to set up the environment yourself, including Security Groups, ACLs, etc to allow a bit of security and connecting using RDP will be a bit of a pain (beside doing so over internet isn't exactly advisable). You might start thinking about Chrome Remote Desktop or even Teamviewer.. and will be very pricey running it. First things first, apparently there's no Win10 available as AMI, so you'll need to deploy it yourself. Once running you'll need to license it. A type suitable for this could cost around 80$ per month.. unreserved.
Using AWS Workspaces isn't really an option: besides it is not "Windows 10" but Windows server 2016 (I needed WSL, which has been introduced with Server 2019 so, no joy), the only way to have a proper Win10 is using BYOL but... (cit from FAQ) :
You need to commit to running 200 Amazon WorkSpaces in a region per month on hardware that is dedicated to you. If you want to bring your own Windows desktop licenses for graphics use cases, you need to commit to at least 4 monthly or 20 hourly GPU-enabled WorkSpaces.
:-/
Amazon WorkSpaces is a virtual desktop that runs on AWS but you connect through an Amazon client software that acts a lot like virtualbox, except the OS that you're using is not on your local machine. So it's more like a Thin Client environment over the internet. I believe the OS through Workspaces is managed by AWS as far as patching and updates through a software called A.C.M.E. (Amazon Client Management Engine).
https://youtu.be/jsqI7KU3S8I
Amazon EC2 instances also provide Windows instances that you would connect through an RDP connection. You'll have to manage the patching and updates yourself though.
Here's a link for your reading pleasure
https://aws.amazon.com/windows/resources/licensing/
I am trying to execute a codebase (detect and track by facebook) inside the docker container that requires GPU access. My docker image is linux based with CUDA toolkit installed however I cannot see any GPU devices in proc filesystem.
The host machine is windows with CUDA 9 toolkit and drivers installed.
When I try to execute the code it says:
CUDA driver version is insufficient for CUDA runtime version
On searching, I realized, I can leverage nvidia-docker plugin to map the host nvidia drivers to container OS but by the looks of it, I couldn't find any support for windows.
Is there any other way around to execute the codebase inside docker container on my windows OS?
It seems that this is not possible on any Windows OS.
https://github.com/NVIDIA/nvidia-docker/wiki/Frequently-Asked-Questions#is-microsoft-windows-supported
I'm currently using a VM hosted on-site by the company I work for. The VM is pretty slow, and we're looking at doing something about it. The choices are to get people off of VMs and onto physical hardware, upgrade our VM host or potentially move to Amazon Workspaces.
One of the challenges we're hitting on our current host is that we're running into problems having nested virtualization to run Docker on our workspaces.
Obviously, if we were to move to physical hardware, we would not have the problem with nested virtualization. If we upgrade our current hardware to be faster/better, we may not solve the underlying issue with nested virtualization.
It would be ideal if Amazon Workspaces supported Windows 10 with Docker for Windows allowing nested virtualization.
Does anybody on here use AWS workspaces with Windows? Do you use Docker?
Any other alternatives(other than AWS workspaces) that can be used to run Docker on Windows VM?
The answer to this is now documented in the Amazon WorkSpaces troubleshooting guide. As of Jan, 2021 Docker is now supported on Linux but not supported on Windows.
Nested virtualization (including the use of Docker) is not supported on Windows WorkSpaces.
Not sure if you're still interested, but we hit the same issue. The Windows image for WorkSpaces is still Windows Server 2016, which does support Docker but only Windows containers unless you're willing to install an out-of-date project to convert. WS 2019 does support it, so whenever Amazon upgrades their images, Docker will be supported on Windows.
For now, we just use Amazon Linux 2 and Docker works.