I know that bitnami has moved all his images to the Azure Marketplace, but there was others VM on vmdepot. Now there is no simple way to share virtual machines on Azure.
As you mentioned, Microsoft Azure decide to removed their old VM Depot Marketplace and all the Bitnami Images have been moved to their new Marketplace:
https://azure.microsoft.com/en-us/marketplace/.
You can create your a virtual machine image for the Azure Marketplace and publish it following the guide below:
https://azure.microsoft.com/en-us/documentation/articles/marketplace-publishing-vm-image-creation/
Related
I have a requirement of Windows version 1809/build 17763 VM on azure for some task. I choked and was not able to find the VM on azure. How can I setup windows VM with above version/build
You can create a VHD with Windows OS version you need locally then upload this VHD to Azure and use this VHD to create a managed image so that you can create VMs by this managed image.
For detailed steps see this official doc.
Btw, I noticed that there is a VM image based on windows server 1809, you can find it while creating VMs => see all images:
I am trying to migrate Linux VM running on AWS to Azure but it has Kernel version (4.4.0-1088-AWS) which is not supported with Azure.
I tried to use Azure Site Recovery to replicate the Virtual machine directly to Azure but the mobility service agent is not installing there due to Kernel version not being supported.
Is there any way to migrate those VMs or Is there any way to clone the same VMs to Azure by creating a new instance and moving data and configuration.
Current OS Version is Ubuntu 14.04
You can create new instance as per requirement Ubuntu version and then copy manually data
You can treat the Linux VM as physical and migrate to Azure using Azure migrate or Azure Site Recovery.
For more details, see a similar discussion on the MSDN forum - https://social.msdn.microsoft.com/Forums/en-US/e542831d-a506-495f-8d4b-61e093c5345a/migrate-from-aws-to-azure?forum=hypervrecovmgr
We have a requirement to Migrate EC2 instance of AWS to Azure as VM, have been trying to implement the same from this source,
unable to complete the process. Tried and stuck on Protection Group.
I'm looking in these other links
Migrating a VM from EC2 to Azure at 300 Mbps For this I'm able to create VM in Classis portal but unable connect to it only port 80 is active all other ports are not working
Migrate virtual machines in Amazon Web Services (AWS) to Azure with Azure Site Recovery
https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-vmware-to-azure
https://aws.amazon.com/ec2/vm-import/ on trying this I'm getting this unresolved EC2 API export to S3 ACL issue
Can anyone suggest me a workflow on how to implement this?
I achieved this by downloading AWS EC2 VHD to an Hyper-V enabled machine on-premises.
Following are the steps.
Create VM from VHD and Remove AWS related software.
Open Hyper-V manager and create VM from the downloaded VHD.
Log in to the VM and uninstalled AWS related services from control panel (AWS Drivers, EC2configService, AWS Tools for Windows, AWS SSM Agent)
All these changes were affected on the VHD.
Upload the converted VHD to Azure Storage (using the Azure PowerShell cmdlets)
Create av Azure VM-Image from that VHD in Classic Azure Portal
Create an Azure VM using the new Image.
Created a classic VM in Azure portal.
For creating a VM under Resource manager, created VHD of newly migrated VM and using that created a new VM in azure portal.
Mention any workflow other than this.
There are multiple ways to migrate machines.
Azure Migrate: Server Migration is one tool that lets you do that and is the recommended way to rehost x86 machines to Azure. You can treat the EC2 instance (AWS VM) as though it were a Physical machine and migrate it to Azure as long as the Operating System on the machine is supported by the Physical Server Migration flow (also check the kernel version to ensure it is supported) https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-physical-virtual-machines
That being said, EC2 VMs may have some changes that you’ll need to make before migrating them, or it may cause issues once in Azure. For example if they are using cloudinit for VM provisioning, you may want to disable cloudinit on the VM before replicating it because the provisioning steps performed by cloudinit on the VM maybe AWS specific and wont be valid after the migration to Azure.
The other thing to note is if the VM is a PV VM (para-virtualized) and not a HVM VM you may not be able to run it as is because paravirtualized VMs use a custom boot sequence in AWS (you may be able to get over this challenge by installing GRUB 2 on the VM and building grub)
The recommendation, if you are using this approach, is to always perform a test migration first to test the process.
Is it possible to download a vhd (or vhdx) image of Windows Azure Cloud Service and run it locally on my computer in Hyper-V?
How to do that?
Thanks
For Cloud Services (web/worker roles), you cannot download a vhd. Remember that the running Windows image is created with a baseline image, then your deployment package is attached and your code is executed. If you spin up another instance, it results in the same starting point. There's no way to take the running machine and capture a vhd. VHD-based operation is all part of Virtual Machines. And with those, you can download the vhd.
So I am a little bit confused about the Azure feature to create virtual machines(i.e VMRoles).
When I do a quick create via the managment portal, I am not asked to specify nor a hosted service nor a storage account. After I click 'create' I see that a storage account is generated for me automatically with some unique name, but I don't see the same for a hosted service. Is a hosted service not needed to create a VM?
The thing that is confusing is that it seems like every other method for creating a VM does require me to specify a hosted service (Azure PowerShell, REST API). And indeed after I create the VM using one of these methods I see my VM inside the hosted service...
Anyone can explain this?
Thanks in advance
Please do not confuse Windows Azure Virtual Machines (IaaS, stateful) with Windows Azure VMRole (PaaS, stateless).
As for creation - the process behind the portal is automated. For me, I have a separate Cloud Service for each Virtual Machine I've created (along with the auto generated storage account). However as all operations are asyc, and I also guess the Microsoft teams are using some kind of CQRS pattern behind the portal, it might take some time for all the components behind a Virtual Machine to appear. While the API strictly requires everything to be ready set, before you actually create the Virtual Machine. My guess is that soon you will also see a cloud service created for your VM (it usually is with the name of the Virtual Machine you created). Also, if you have noticed, the public URI for accessing your Virtual Machine (be it RDP or SSH) has the format of [your_vm_name].cloudapp.net - so this is a Cloud Service (formerly known as Hosted Service).
First of all Windows Azure Virtual Machines and VM Role are two separate things. Based on what you have explained it seems you are trying to create a Windows Azure Virtual Machine so I will explain you in short how it works:
Very first: In order to create a Windows Azure Virtual Machine you need a VHD which has OS Image. You can use one from Gallery or you can upload one by yourself to your specific Blob Azure Storage.
When you use Quick create or create the process is exactly same in the background however during quick create lots of settings is already predefined as will quick create you will only get Windows OS VHD to choose. In both cases a storage account is used to copy the OS VHD (if it is not part of your OS image collection). In most of the cases a previously created storage account is used, so you may think in was not created but in fact the storage account was used to copy the VHD from repo. This may not be the case if you create a VM from an image which is already in your OS VHD collection.
With quick create the DNS name you set is become the VM name but with create you have option to create a different DNS name for your application but they needed in both cases. In any case the DNS name will bind to your VM, the same DNS name will distinguish your VM from others and a must to configure for any VM.
I believe that the cloud service is not surfaced for a single quick-create Virtual Machine. This is to make Virtual Machines as easy to use as possible. The cloud service would be created and be displayed on the portal were a second virtual machine to be added to the cloud service.