{"componentChunkName":"component---src-templates-post-template-js","path":"/note-hyper-v-2-proxmox-en","result":{"data":{"markdownRemark":{"id":"1514937e-2d74-5ed6-8589-f0021d99d7c7","html":"
\n

This page has been machine-translated from the original page.

\n
\n

I decided to rebuild the analysis environment running on Proxmox, but setting up a machine from scratch was far too much hassle, so I tried migrating a Hyper-V virtual machine from another test machine instead.

\n

I am using Proxmox version 8.2.7.

\n\n

Table of Contents

\n\n

Export the Hyper-V machine

\n

According to the following article, it seems that if you have a virtual disk in vhdx format, you can migrate a virtual machine to Proxmox.

\n

Reference: Trying to migrate VMs for various virtualization platforms to a Proxmox environment | Back of a flyer

\n

So I decided to export the existing machine in Hyper-V Manager, extract the virtual disk from it, and copy it to the Proxmox server via USB.

\n

\n \n \n \n \n \n \n \n \n

\n

\n \n \n \n \n \n \n \n \n

\n

Copy the files to Proxmox

\n

First, confirm that the media containing the copied virtual disk file is connected to the server as /dev/sdb1. (This time I used an external M.2 SSD, so it seems to have been identified as an SSD.)

\n

\n \n \n \n \n \n \n \n \n

\n

Once the import is complete, you can confirm that a disk for the specified ID (100) has been added to local-lvm.

\n

\n \n \n \n \n \n \n \n \n

\n

Next, open the virtual machine with ID 100 that you created, and confirm that the imported virtual disk is displayed as [Unused Disk 0].

\n

\n \n \n \n \n \n \n \n \n

\n

Then attach this disk from the [Edit] button, and from [Options] -> [Boot Order], enable the attached disk as the boot disk.

\n

\n \n \n \n \n \n \n \n \n

\n

If you start the virtual machine now, you can confirm that the machine created in Hyper-V boots on Proxmox.

\n

Summary

\n

I wrote this up because it seems like the kind of procedure I might need again once I’ve forgotten it.

\n

Note: among the machines migrated this time using the method above, the virtual machine with xface installed on a minimal Ubuntu Server displayed its GUI on the noVNC console after migration, but keyboard input stopped working.

","fields":{"slug":"/note-hyper-v-2-proxmox-en","tagSlugs":["/tag/notes/","/tag/windows/","/tag/proxmox/","/tag/english/"]},"frontmatter":{"date":"2024-11-04","description":"I summarized how to migrate a Hyper-V virtual machine to Proxmox.","tags":["Notes","Windows","Proxmox","English"],"title":"How to Migrate a Hyper-V Virtual Machine to Proxmox","socialImage":{"publicURL":"/static/7a639a5b0abaa68650963d4babed09f8/note-hyper-v-2-proxmox.png"}}}},"pageContext":{"slug":"/note-hyper-v-2-proxmox-en"}},"staticQueryHashes":["251939775","401334301","825871152"]}