From: Gerald Brandt <gbr@majentis.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Migrating from oVirt to Proxmox
Date: Mon, 8 Feb 2021 06:17:15 -0600 [thread overview]
Message-ID: <29199880-8246-8125-60ef-1e71acd55b17@majentis.com> (raw)
In-Reply-To: <e48d9286-802c-99fd-d02d-0312c9691773@khm.de>
On 2021-02-08 5:59 a.m., Marc Sauer wrote:
> Hello,
>
> we would like to migrate our oVirt Cluster to Proxmox, because of the
> recent events regarding RedHat and CentOS. Also, we are getting new
> servers and have the one time oppurtinity to do a switch to another
> virtualization platform.
>
> Right now, We are using GlusterFS underneath the oVirt Cluster and
> would like to use it on Proxmox as well.
>
> It will be a 3 node cluster.
>
> My question to you all is: Has anyone on this list done a migration
> process from oVirt to Proxmox? Both systems are based on KVM, so a
> migration should not be that complicated.
>
> My main idea is the following:
>
> - Set up a Proxmox cluster with 3 nodes
> - Set up the Gluster storage on the new servers
> - Create VMs with the same name and copy the raw disk image from the
> old Gluster to the new one
> - Set the copied Raw disk image as bootfile for the created VM
> - Repeat the step for all VMs, one at a time
>
> Since we do not have thousands of VMs we can do this manually, so no
> need to set up a complicated migration pipeline. The main advantage of
> this is, that we can migrate a VM one at a time and not all at once.
>
> What are your thoughts on this? Will we get trouble with, for example,
> the drivers inside the VM?
>
> Thank you in advance and many greetings from Cologne,
>
> Marc Sauer
>
>
That is the exact process I used when moving from Proxmox to straight
KVM and virt-manager. It's a safe way to move. If a single VM has
issues, you can fall back to the original and figure out what went wrong
without long downtimes. I moved thirty VM's using this process.
I did have issues with Windows machines, and had to manually copy the
machine's GUID to the new virtual machine in order to keep Windows
activated.
Gerald
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2021-02-08 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 11:59 Marc Sauer
2021-02-08 12:17 ` Gerald Brandt [this message]
2021-02-08 12:22 ` Ronny Aasen
2021-02-08 12:54 ` Dominic Jäger
2021-02-08 13:42 ` Ronny Aasen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29199880-8246-8125-60ef-1e71acd55b17@majentis.com \
--to=gbr@majentis.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox