this post was submitted on 11 Jul 2023
11 points (92.3% liked)

Sysadmin

7706 readers
25 users here now

A community dedicated to the profession of IT Systems Administration

No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
!lemmy@lemmy.ml
!lemmyworld@lemmy.world
!lemmy_support@lemmy.ml
!support@lemmy.world

founded 1 year ago
MODERATORS
 

I have seen the documentation saying to build an empty VM with slightly more space for each volume than was on the physical server, then use clonezilla to create an image of the server, then import it. That seems ok, but I'm hoping someone out there has more real-world experience in doing this and can share if they did it differently, or encountered any pitfalls.

As my environment matures, I am moving from "Hey I have 1 physical server with everything on it" to "Let's use a hypervisor and spin off services onto their own." When the base OS is P2V'd, I'll be able to have 2 hypervisors and start implementing HA. I've been using this system as a scratchpad and dev box for 10 years and would love to just migrate it over.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] SniperFred@feddit.de 1 points 1 year ago (1 children)

never done p2v but v2v before, using the starwind converter. it's a freeware and I just read it can also do p2v. proxmox itself is not available as a target, so you might have to convert your server to an esxi-vm, and then again from there to proxmox ๐Ÿค” that might be the slowest and one of the dirtiest ways to tackle this, but it might work

here's the link to the converter software: https://www.starwindsoftware.com/starwind-v2v-converter

starwind converter can export to a qemu image though, which can them import into proxmox.

I used the converter to move from hyper-v to proxmox just last month.