解决了

移动3.6.2 - EFI启动管理器按F2

  • 2020年12月1日
  • 2回答
  • 568的浏览量
MarcelVenema

我正在使用Move 3.6.2将虚拟机从Hyper-V迁移到AHV CE集群。一切都很顺利，但割接后，AHV虚拟机卡在“按F2 EFI启动管理器”屏幕，cpu使用率约52%。按FN+F2、F2、CTRL+F2、ALT+F2或其他组合无效。请建议。Hyper-V主机为Win2019，虚拟机为2019，从bootgfw启动。Efi和安全启动禁用。在Edge、Chrome和IE浏览器上也尝试过，同样的结果，停留在“按F2 EFI启动管理器”屏幕上。

图标

最佳答案如果郝2020年12月24日，12:29

Hi, we have done multiple migrating of VMs from Hyper-V to AHV, first is to have VirtIO installed. It would be good to have it pre-installed before you perform the migration, however, it is still possible to inject the driver after the VM has been migrated. Your symptoms seems to suggest\u00a0UEFI was not chosen as the boot device, can you give this a try? Can you also check if the windows partition is MBR or GPT? We have encountered that servers with MBR windows partition can only boot on legacy, and GPT UEFI. If you as mentioned above that you do not have VirtIO installed after being migrated, and am able to hit the page where you can open a CMD (either by mounting an windows ISO or booting in recovery), follow this link to perform the injection. How to inject storage VirtIO driver if it was not installed before migration to AHV<\/a><\/p>","className":"post__content__best_answer"}">
查看原始
I am moving\u00a0virtual machines with Move 3.6.2\u00a0from Hyper-V to an AHV CE cluster. Everything goes well, but after the cutover the AHV VM is stuck at the \u2018Press F2 for EFI boot manager\u2019 screen and cpu usage around 52%. Pressing FN+F2, F2, CTRL+F2, ALT+F2 or\u00a0other combinations have no effect. Please advise. Hyper-V host is Win2019, VM is 2019 with boot from bootmgfw.efi and secure boot disabled. Also tried with Edge, Chrome and IE, same result, stuck at \u2018Press F2 for EFI boot manager\u2019 screen.<\/p>","quoteUsername":"MarcelVenema","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
本主题已关闭供评论

2回答

jonas.hogman
Userlevel 1
徽章 ＋２

是否尝试以旧模式启动虚拟机?这有其他结果吗?这是一段时间以来，我运行从hyper-v移动，但我记得我有一些问题，然后iscsi virtio驱动程序安装自动。所以想知道如果你在迁移前手动安装Nutanix VirtIO驱动程序包可以帮助?这里有一个类似的线程，可能会有帮助:UEFI服务器不引导后V2V到AHV使用移动3.3.1

//Jonas Hogman - NTC 2021
Have you tried to boot the VM in legacy mode? Does that give you any other results? It\u2019s been a while since i ran Move from\u00a0hyper-v but i remember i had some problems with getting then iscsi virtio drivers to install automatically. So wondering if you pre migration manually install the Nutanix VirtIO driver package could help? There is a similar Thread here, that might help: UEFI Servers do not boot after V2V to AHV using Move 3.3.1<\/a><\/p>","quoteUsername":"jonas.hogman","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
年代

Hi，我们已经完成了从Hyper-V到AHV的多次虚拟机迁移，首先是安装了VirtIO。最好在执行迁移之前将其预安装，但是，仍然可以在迁移VM之后注入驱动程序。您的症状似乎表明UEFI没有被选择为引导设备，您可以尝试一下吗?你能检查一下windows分区是MBR还是GPT吗?我们已经遇到了使用MBR windows分区的服务器只能在遗留系统上引导，并且GPT UEFI。如果您如上所述，在迁移后没有安装VirtIO，并且能够点击可以打开CMD的页面(通过挂载windows ISO或在恢复中启动)，请按此链接执行注入。如何注入存储VirtIO驱动程序，如果它没有安装之前迁移到AHV

Hi, we have done multiple migrating of VMs from Hyper-V to AHV, first is to have VirtIO installed. It would be good to have it pre-installed before you perform the migration, however, it is still possible to inject the driver after the VM has been migrated. Your symptoms seems to suggest\u00a0UEFI was not chosen as the boot device, can you give this a try? Can you also check if the windows partition is MBR or GPT? We have encountered that servers with MBR windows partition can only boot on legacy, and GPT UEFI. If you as mentioned above that you do not have VirtIO installed after being migrated, and am able to hit the page where you can open a CMD (either by mounting an windows ISO or booting in recovery), follow this link to perform the injection. How to inject storage VirtIO driver if it was not installed before migration to AHV<\/a><\/p>","quoteUsername":"Si Hao","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
Baidu