V2V Conversion boot failures for CentOS 7, RHEL 7 and OpenSuse 13

Topic

This article contains instructions to address CentOS 7, RHEL 7 and OpenSuse 13 conversion boot failures.

 

Environment

  • 5nine V2V Converter 

Instructions

Generally this effect is due to the fact, that ram-disk image does not contain Hyper-V related modules, however it disables IDE adaptors once Hyper-V environment is detected. So, two steps needs to be done after conversion to make system bootable:

1) Force IDE usage for the first boot;
2) Update ramdisk image to include Hyper-V integration components.

=============
CentOS 7, RHEL 7

During the first boot, in the grub boot screen press e, then scroll down and add ata_piix.prefer_ms_hyperv=0 before root=... text

Once system boots type

dracut -f
reboot

Once rebooted it should work as usual with hyper-v integration services enabled

=================
OpenSuse 13

Suse: During the first boot, in the grub boot screen press e, then scroll down and add ata_piix.prefer_ms_hyperv=0 before root=... text

Once system boots type

mkinitrd
reboot

Once rebooted it should work as usual with hyper-v integration services enabled

Was this article helpful?
3 out of 3 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.