We have a PROXMOX hypervisor with 5 VMs that need to be migrated to Azure.
I have already created a new VM in Azure that will serve as Master Target and Process Server. Upon installing the replication software on our machines, I can successfully initiate the replication, and the status changes to 'Protected' on the replicating machine.
Before migrating, I'd like to do a test migration of our Ubuntu 14.04 but here is where I encounter an error.
The procedure errors on the second step - Initiating test failover which results as Failed. Errors include:
Failover failed because of an unsupported configuration.
If this is a Windows virtual machine, then the operating system disk might be encrypted. If this is a Linux virtual machine, then /boot and root (/) partitions might be on different disks.
This is not a supported configuration. Read more at http://aka.ms/ASRErrorCode-170049
The requested action couldn't be performed by the 'InMageAzureV2' Replication Provider.
The Provider action failed. Check other errors for more information.
Resolve the issue and retry the operation.
The logs are generic and I cannot find any solution/similar error online.
The link provided by Azure doesen't even contain those error IDs.
Root and /boot partition are on the same disk (dev/sda)
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 31459327 15728640 83 Linux
root@SRV-vm:~# lsblk -l
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
sda1 8:1 0 15G 0 part /
sda2 8:2 0 1K 0 part
sda5 8:5 0 5G 0 part [SWAP]
sdb 8:16 0 280G 0 disk
sdb1 8:17 0 280G 0 part /home
sr0 11:0 1 1024M 0 rom
In the docs its stated that paravirtualisation storage drivers are not supported, therefore I changed in Proxmox the Device/Bus for the HDD from VIRTIO (paravirtualised storage driver) to IDE.
I have re-red multiple times the supported configurations for migrating physical servers (debian8,ubuntu14,windows server 2012 R2) and there isn't anything controversial.
Any suggestion is greatly welcomed..
EDIT: I'm attempting to test migrate a Windows Server 2012 R2 to see if I will encounter the same issue.