Azure → Zadara · Linux
Moving a Linux VM from Azure to Zadara: what has to change inside it
Z-Move, the agentless VM migration platform, copies Azure VMs to Zadara block by block. A Linux VM copied that way boots, but it is still configured for Azure: it waits for Azure, comes up without network and keeps calling the Azure agent's endpoint. These are the four settings behind it, what Z-Move changes, and how to do the same by hand.
It boots, but it is still configured for Azure
A disk copied from Azure to Zadara block by block carries its operating system as it is. The kernel and systemd come up on Zadara without help. In our first Azure → Zadara run, with no changes inside the VM, the image booted on Zadara, but its Azure configuration slowed the boot and left the VM without network.
Nothing was broken in the disk. The system was doing what Azure had set it up to do: look for Azure. Four settings are responsible.
Four settings that only work in Azure
- cloud-init. An Azure image lists only the Azure datasource, so cloud-init reads its configuration from Azure. On Zadara it keeps looking: it waits for the Azure provisioning ISO on /dev/sr0 and for the Azure wireserver, and the boot slows down. Z-Move adds /etc/cloud/cloud.cfg.d/99_zmove-migrated.cfg with a generic list, NoCloud, ConfigDrive, OpenStack, Ec2 and None (Ec2 with strict_id: false), so cloud-init detects the platform it lands on.
- The network. netplan matches the Azure network card: the hv_netvsc driver and the Azure MAC address. On Zadara the VM gets a VirtIO card with another address, nothing matches, and the VM comes up without network. Z-Move adds /etc/netplan/90-zmove-dhcp.yaml (permissions 0600): DHCP on any Ethernet interface (e*), marked optional. On distributions without netplan it adds a lowest-priority NetworkManager profile instead.
- The Azure agent. walinuxagent (waagent on some distributions) talks to the Azure wireserver, and outside Azure it keeps trying. Z-Move takes it out of the boot by removing its links in the systemd *.wants folders; systemctl enable brings it back.
- The temporary disk. An Azure VM mounts a temporary disk from /etc/fstab (azure_resource). Zadara has no such disk. Z-Move comments that line out and keeps a copy of the file as fstab.zmove-bak.
Where and how Z-Move makes the changes
On the copy, never on your VM in Azure. The import worker makes the changes on the system disk in Zadara, after the transfer and before the image is registered, so the source VM keeps running unchanged.
- It mounts each Linux partition read-only, largest first (with nosuid, nodev and noexec, plus nouuid for XFS), until it finds /etc/os-release, and only then remounts that partition read-write.
- It does not edit the original files: the new cloud-init and network files take precedence by their names, and the original fstab is kept as a copy.
- It never follows a symbolic link that points out of the mounted disk.
- It is best-effort: if a change fails, the failure goes to the session log and the migration continues with the disk as it came.

What it costs in time
In the measured run, an Ubuntu 24.04 VM with a 30 GiB disk moved from Azure East US to Zadara in 19m 40s. The four changes took 3 seconds of that. The boot test then started a VM from the new image, and SSH answered on port 22 after 2m 28s.
The transfer itself does not go through a middle server: on this route one worker in Zadara reads the Azure snapshot directly, in parallel streams. See Azure → Zadara for the whole route.
What is left as it is
Disks without a Linux system Z-Move can recognise are copied without changes: Windows disks, a root file system on LVM, and data disks. Windows needs the VirtIO drivers that Zadara uses before the switch, and the pre-checks warn about it.
How to know it worked
The session log shows the result of the adaptation: the system found, the partition and each change made, or the reason it was skipped.
The boot test is the proof. Z-Move starts a temporary VM from the new image in Zadara and, for up to 8 minutes, tries SSH, RDP, HTTPS and HTTP. It passes when a port accepts a connection, which means the system started and its network works. On Zadara this is the check that counts, because the platform exposes no console through its EC2 API.
If the VM stays running and no port answers, the result is inconclusive, not failed: the system may have booted without network, have a firewall of its own, or still be booting. After a migration from Azure, that is the first sign to look at the four settings above.
Doing it by hand
The same four changes can be made by hand, on a copy of the system disk, before it boots on Zadara. Do not make them in the VM while it still runs in Azure: the Azure agent and the Azure datasource are what it needs there.
To see what a VM carries, these read-only commands work on Ubuntu and Debian-style systems:
# Read-only checks, Ubuntu/Debian-style systems
grep -rs datasource_list /etc/cloud/cloud.cfg /etc/cloud/cloud.cfg.d/
grep -rs -e hv_netvsc -e macaddress /etc/netplan/
systemctl list-unit-files | grep -Ei 'walinuxagent|waagent'
grep -n azure_resource /etc/fstab
The checklist
It is manual work for every VM. On the Azure → Zadara route, Z-Move does it on every Linux system disk and checks the boot. How it stays out of your VMs is on the agentless migration and security pages.
- Add a cloud-init file with a datasource list without Azure.
- Add a network configuration with DHCP on any Ethernet interface.
- Disable walinuxagent or waagent on the copy.
- Comment out the azure_resource line in /etc/fstab, keeping a copy.
- Boot the copy on Zadara and check that SSH or RDP answers.
The other way: Zadara to Azure
VMs going to Azure get the opposite change: cloud-init with the Azure datasource first in the list (Azure, NoCloud, ConfigDrive, OpenStack, Ec2, None) and the same DHCP network configuration. Z-Move also checks that the newest kernel has the Hyper-V drivers hv_vmbus and hv_storvsc; without them the disk will not boot on Azure, so the session log warns you. More on Zadara → Azure.
FAQ
Linux from Azure to Zadara: questions
Something else? Write to hello [at] zmove.click
Does Z-Move change my VM in Azure?
No. The changes are made on the copy, in Zadara, after the transfer. The source VM keeps running unchanged.
Can I undo the changes on Zadara?
Yes. The original files stay in place: delete 99_zmove-migrated.cfg and 90-zmove-dhcp.yaml, restore /etc/fstab from fstab.zmove-bak, and systemctl enable brings the Azure agent back.
Which Linux systems does it cover?
Systems with /etc/os-release on a plain partition, with netplan or NetworkManager. It was tested on Ubuntu with ext4 and a separate /boot and on RHEL with XFS, and run live on Ubuntu 24.04. A root file system on LVM is left as it is.
What if a change fails?
The failure is written to the session log and the migration continues with the disk as it came. The boot test then shows whether the VM starts with network.
How much time does it add?
In the measured run, 3 seconds for the four changes, in a migration of 19m 40s.
Demo
See a full run, from wizard to boot test.
Book a demo and follow a complete migration: wizard, pre-checks, live session, boot test and cleanup.
Or write to hello [at] zmove.click