# Migrating Suse 12 server from VMware to Hyper-v

**URL:** <https://forums.suse.com/t/migrating-suse-12-server-from-vmware-to-hyper-v/46281>\
**Category:** SUSE Linux Enterprise Server\
**Created:** [April 22, 2026, 10:31am UTC](https://forums.suse.com/t/migrating-suse-12-server-from-vmware-to-hyper-v/46281 "2026-04-22T10:31:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bongokong](https://avatars.discourse-cdn.com/v4/letter/b/a9adbd/32.png) [@bongokong](https://forums.suse.com/u/bongokong)\
**Post date:** [April 22, 2026, 10:31am UTC](https://forums.suse.com/t/migrating-suse-12-server-from-vmware-to-hyper-v/46281/1 "2026-04-22T10:31:28Z")

</div>

Hi all,

we are currently trying to migrate a Suse 12 vm from VMware vsphere 8 to Hyper-v 2022 server.

We tried a simple lift & shift migration (vm was configured as bios legacy on vmware) but it fails.

The vm is actually correctly migrated and able to start, but it is stuck during the boot phase at this stage:

 ![Senza titolo](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/8/8b3cc94e0a9d174d7f235b2adef21230cded842f.jpeg)

looks like it is not able to do something or to map correctly the disks on the vm started on hyper-v but seems to be stuck here forever.

Any ideas on how to troubleshoot or proceed , maybe coming from similar experiences? It seems that is not even possible to reach any console or start in emergency mode.

We’ve tried to leave it there but it seems to never end this step?

Thanks a lot

---

<div class="post-metadata">

**Author:** ![Greg\_E](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@Greg\_E](https://forums.suse.com/u/Greg_E)\
**Post date:** [April 23, 2026, 12:05am UTC](https://forums.suse.com/t/migrating-suse-12-server-from-vmware-to-hyper-v/46281/2 "2026-04-23T00:05:18Z")

</div>

Can you remove the cdrom, and can you change the disk type from scsi to sata? Only two things I can think of trying, not too experienced with Hyper-v.

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [April 23, 2026, 1:24pm UTC](https://forums.suse.com/t/migrating-suse-12-server-from-vmware-to-hyper-v/46281/3 "2026-04-23T13:24:00Z")

</div>

@bongokong Hi and welcome to the Forum 😄

Also worth checking the grub options for disk references, likewise your `/etc/fstab` entries likely don’t match the new device ID’s (blkid command) boot into rescue mode and check…

---

<div class="post-metadata">

**Author:** ![aalzayed](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/aalzayed/32/12344_2.png) [@aalzayed](https://forums.suse.com/u/aalzayed)\
**Post date:** [April 27, 2026, 9:40am UTC](https://forums.suse.com/t/migrating-suse-12-server-from-vmware-to-hyper-v/46281/4 "2026-04-27T09:40:29Z")

</div>

Try this TID: [https://support.scc.suse.com/s/kb/Cloned-OS-LUN-Fail-to-Boot?language=en\_US](https://support.scc.suse.com/s/kb/Cloned-OS-LUN-Fail-to-Boot?language=en_US)