How do I migrate an old Xen DomU VM, backed by a DRBD volume, to Digital Ocean?

Question

Hi Folks,

I’m about to migrate a VM from Xen, running on our own server, to K8 - probably running on Digital Ocean. Any hints on how to do this as easily as possible would be much appreciated.

Basic setup:

A legacy system that we’re retiring
Xen 3.0
Server and VM are running Linux 2.6.26-2-xen_686
Root & swap are mounted on DRBD volumes (v 8.0.4)
Yes - it’s all ancient, and temporary while we update things.

Looking for a simple way to convert the vm to an image that can run as a container on Digital Ocean, and for migrating the DRBD volume to a generic block storage service.

Any suggestions?

Thanks very much,

Miles Fidelman

Bobby · Answer

Hey! That’s quite a legacy setup, nice one keeping it alive this long 🙂 I don’t think there is a direct path from a Xen VM like that to a container on DigitalOcean. Containers are a different model, so you usually don’t “convert” a full VM into a container image. What people normally do is: First migrate the VM as a VM Then modernize it into a container later For DigitalOcean, the simplest path would be: Create a disk image from your Xen VM (raw or qcow2 if possible) Spin up a Droplet and manually move the data over (rsync or similar) Recreate the environment on the Droplet For the DRBD volume, you can treat it like a normal disk and copy the data to a Droplet or to a Block Storage volume on DigitalOcean. There is no direct DRBD import, so it is more of a data migration than a lift and shift. Once it is running on a Droplet, you can then slowly refactor it into containers and move to Kubernetes if that is your goal. If you want less ops work, you could also look at DigitalOcean App Platform later instead of managing K8s directly. I am not 100% sure if DO support can help with this kind of legacy migration, but it might still be worth asking here:https://do.co/support Main idea is do it in steps, VM first, containers after, trying to jump directly will be very hard. Good luck!

alexdo · Answer

Heya, @milesrfidelman Containerizing an old Xen DomU directly is usually more pain than it’s worth. You’d be ripping out the kernel, init system, hardware assumptions, etc. For a temporary “keep it limping along while we modernize” situation, I’d honestly skip the container path entirely and just move it to a Droplet as a VM. Way fewer surprises. You can always containerize the actual application later when you have time to do it properly. If the goal really is K8s eventually, I’d treat it as two separate projects: 1) get the thing running on a Droplet first so it’s off the legacy hardware,2) then properly containerize the application later when you understand what it actually needs. Regards

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today

Report this

How do I migrate an old Xen DomU VM, backed by a DRBD volume, to Digital Ocean?

Related questions

Switch hostinger to digitalocean?

how to migrate my droplet from Ubuntu 24.10 x64 TO 24.04(LTS)*64

Move DigitalOcean WP site to another DigitalOcean WP site

AWS EFS migration to Digitalocean Spaces

Migrate proxmox vm to digitalocean

Report this

How do I migrate an old Xen DomU VM, backed by a DRBD volume, to Digital Ocean?

Related questions

Switch hostinger to digitalocean?

how to migrate my droplet from Ubuntu 24.10 x64 TO 24.04(LTS)*64

Move DigitalOcean WP site to another DigitalOcean WP site

AWS EFS migration to Digitalocean Spaces

Migrate proxmox vm to digitalocean