I've been reading about it, and I don't know if there is anyway of doing it.
I want to create a Virtualbox virtual machine inside another virtual machine I created in azure, and I don't have Hyper-V activated.
My virtual machine doesn't have a BIOS to access and enable it, and I read that not all virtual machines in azure allow nested virtualization.
The virtual machine I have right now is a B1ms standard and what I read is that I need a V3 machine to virtualize a virtual machine inside the azure one. Is that true? I don't want to spend money just creating it and then not beeing able to do it.
Thanks :)
This can be done using Nested virtualization in Azure. And yes you heard it right that not all Azure Virtual Machines in Azure allow this and you would need V3 VMs. Make sure to choose a VM size large enough to support the demands of a guest virtual machine.
For costing, you can either create a trial Azure account that would give you a credit of $200. Or if you have got a Visual studio Pro or Enterprise license, you are eligible for free monthly credits that you can use for exploring Azure.
Although you can use Nested Virtualization it might be better to just convert your VirtualBox images to Azure VHDs. This is relatively straightforward:
vboxmanage clonehd SOMETHING.vdi SOMETHING.vhd --format VHD
Afterwards you can use Azure Storage Explorer (or the CLI) to upload the VHD and use this to deploy a Native Virtual Machine on Azure.
Related
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'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.
I need to install linux from existing VMware VMDK on EC2. For first time I can do this manually, later I will need to do this in automated way.
Could you please help me with link to relevant documentation. Also any tips and experiences are welcome.
Why do I need this?
At my company developers and QA are running our PHP apps on a virtual machine hosted on local machine. We want to move these virtual machines to the cloud, so each developer can easily set up a sandbox in simple web interface.
Amazon does not officially support importing Linux. However, an article from 2008 claims it can be done. If you try this, note this URL as well.
Finally, an AWS employee posted this too:
You can use ec2-import-volume to turn a local disk in a RAW, VMDK or VHD file format into an EBS volume in EC2. This turns a full disk, with MBR, into an EBS disk. If the guest is PV, with the Xen PV drivers installed, you could take a snapshot and create an AMI from that snapshot, inserting the correct AKI.
Follow the instructions of creating your own AMI. Also check out the following articles on EBS volumes: article1, article2. Here's some steps on how to create EBS-backed AMI instance.
You will have to manually create your own images. The ec2 api tools do not support linux/esxi 5 images. I just found out after spending 2 hours on a vmware linux to amazon port.
We are looking to move all of our systems to a virtualized env.
We will be going with EC2 and it appears that if we can install something like vmware or KVM on EC2 then create VMs as needed it would be the most cost effective solution for us.
Is this possible?
thanks!
EC2 is already a virtualized environment; it uses the Xen virtualization manager, which is an open source equivalent to VMWare server. You can create VMs with EC2, customize them and save them as Amazon Machine Images (AMIs).
See the Amazon documentation for a more comprehensive introduction.