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.
Related
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.
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.
My question is: If you use Docker tool box (that is required for windows 10 home to run Docker) you are essentially using a virtual machine (vm)?
If you are using a vm already the only reason to use docker from that point is to save on many more multiple instances?
Meaning if you only want 1 extra (guest instance): you can have a vm. Though, with docker (toolbox on windows 10 home) you would have 1 vm and it runs docker?
The only way that is useful is if you want many more instances as in: 1 vm + 1 docker or + 1000 more dockers?
Or am I missing something?
Yes, docker toolbox uses Oracle VirtualBox cause Windows 7, 8, and Windows 10 home cannot use Hyper V. And yes, If you are using a VM already the only reason to use docker from that point is to save on many more multiple instances but it also allows easy backup and deployment. But you are losing a decent amount of memory when running a VM and then even more when you are running docker.
So although Docker CE will tell you your Windows doesn't support Hyper-V, this isn't always the case (if you check in System Info you might have Hyper-V enabled, if you're on an Insider build or many builds on GPU computers after Anniversary update then you probably have Hyper-V on Windows 10 Home). There are a few workarounds until the Docker team addresses this issue.
You could use Docker from inside WSL (Windows Subsystem for Linux). Microsoft claims WSL accesses everything directly without Hyper-V so this should be theoretically at the same speed. Of course you can't use your GPU at all because of limitations with GPU passthrough on WSL, which you can ask to be resolved here.
You can also use Docker Toolbox as the other answer stated with Virtualbox, but this will be inherently much slower as you're virtualizing a container inside a virtualized container. You should be able to theoretically get GPU support through this, as well as other features e.g. GUI that you wouldn't be able to with WSL.
To answer the "usefulness" portion of the question:
It's also useful if you run code on a server, but need to develop/debug/update it. You want to test it locally, but to make sure the environment in which it executes is the same (to avoid unexpected, environment specific behavior), you use Docker both locally and on the server. In such a case, even though it's slow, I'll spin up a VM on my W10 Home laptop and run Docker in it.
The greatest feature of the Windows 10 Home May 2020 Update is Windows Subsystem for Linus 2. You can docker in it without the need for a complete virtual machine as in Virtual Box.
Install Docker Desktop that it will automatically indentify WSL2.
I am trying to run mapr sandbox on a windows pc and with 8gb ram. But when I am trying to import the ovf its always saying ovf is corrupt while I have used multiple sources the ovf that is running on the other machine is not running in my one.I have tried to play with the configuration as well I also tried to extract and run the ovf as a vmdk but than there will be no config setup done for so that doesn't works as well. Now I have tried that on vmplayer it got install and said that the ovf format is unsupproted and when you try again it will not see the ovf file specification concern so it imported the file successfully but now its says that the vmx file is incompatible. I cannot find any way out?
I did the following for install it on Ubuntu 14.04 (being virtual machines the final destination, shouldn't be mayor problems):
On VirtualBox
Don't use the ovf file.
Create virtual machine (Machine -> New...)
On operating system, choose red hat 64 bits
On memory, you should asing 8 GB for the VM (or less, if you have an old computer like me :D)
Don't add virtual drives, you can't add both drives. Use the option "Do not add a Virtual Hard Drive"
After creation of the VM
Add both disks to the virtual machine, from settings
Configure the network of the machine as following
Attached to "Bridget Adapter"
Name: Eht0
Adapter Type: Intel PRO/1000 MT Desktop
Promiscuos mode: Deny
Cable Connected: yes
After this small steps, you should be capable of doing right click -> start, and start using MapR. Basically, we import the machine in a very complicated way, because the ovf file that is supposed to use for importing doesn't work!!
I was facing same issue on my Windows & machine. Here is what I did:
Again downloaded MapR sandbox for VMWare for windows.
Uninstalled previous version of VMWare which was giving this issue and downloaded VMWare Workstation Player for Windows 64 bit.
This time it worked.
As I had the chance to experiment with MapR recently-
MapR needs 6GB RAM
at least for the Virtual Box
(or the virtual machine you are using on windows)
if you don't grant the MapR these 6gb it is just not starting with some strange error saying nothing about that issue. You have 8gb ram on your windows machine so I recommend you to spend at least 6.2gb ram for the process.
p.s. Later I had other problems with the mapper as you can see with no support. (previous I found 1 more bug that they say will be fixed in MapR 6)
I am currently using MapR 5.2
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.