-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VMWare-Windows Migration: Booting from Hard Disk | No Bootable Device Found #9645
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Hi @kimchheng-dev Have you noticed any errors during virt-v2v conversion in the KVM host agent logs? Can you share the agent log. |
Hello, @sureshanaparti I got log like this in KVM Host. 2024-09-03 16:42:15,326 INFO [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) (100.00/100%) |
@kimchheng-dev Noticed below logs, can you try to boot with UEFI mode. Sometimes conversion is success, but maybe due to virt-v2v guest OS incompatibilty, will fail to boot.
|
Hello, I cannot find a way to modify boot option of CloudStack instance after imported? Look like this option available only in New VM deployment. |
Try after VM detail/setting update - UEFI: LEGACY. |
Hello this option is not working and I still got the same error. And here's the management log. 2024-09-06 13:18:10,384 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-20:ctx-8cc8fe02 job-27644/job-27646 ctx-eecd52ea) (logid:272b5ab1) Start completed for VM VM instance {"id":8911,"instanceName":"i-2-8910-VM","type":"User","uuid":"64b67f54-3fbf-4590-9d8b-368735134087"} |
Ok, Can you share the host details (OS, arch) used for conversion. Check the supported conversions list here: https://access.redhat.com/articles/1351473 |
My KVM host is: |
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: