|
Mike,
Florian,
A follow-up question if I might:
The version of Xen I'm running doesn't seem to store image files at all. The config file seems to identify a boot volume, a Linux boot file, and root & swap volumes. Xend seems to act as a boot loader rather than starting up an image file.
Which leads me to wonder what virt-v2v does do convert things (and now that I've discovered them they're my next stop). Any thoughts?
Thanks Again,
Miles
From: Mike <debian@xxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, April 7, 2026 2:01 PM
To: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxxx <xen-users@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: suggestions sought for migrating from Xen to K8
Miles Fidelman wrote:
> 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.
>
> Server and VM are running Linux 2.6.26-2-xen_686
> Root & swap are mounted on DRBD volumes (v 8.0.4)
>
> Looking for a simple way to convert the vm to an image that can run as a Kubelet, and for migrating the DRBD volume to a generic block storage service.
Kubelet is part of the Kubernetes software; one doesn't run an image "as a
kubelet", one runs it as a container.
An image typically contains just one main executable, which runs as PID 1.
As usual, the container dies when PID 1 dies. I suppose there may be a way
to convert a whole domU image into an OCI image and then run the initd as
PID 1, but that would be really weird. So you should instead be thinking
about decomposing your VM into an image per application.
|
