Skip to content
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.

Sign up for GitHub

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

Jump to bottom

VMWare-Windows Migration: Booting from Hard Disk | No Bootable Device Found #9645

Open
kimchheng-dev opened this issue Sep 6, 2024 · 9 comments
Open

VMWare-Windows Migration: Booting from Hard Disk | No Bootable Device Found #9645

kimchheng-dev opened this issue Sep 6, 2024 · 9 comments

Comments

@kimchheng-dev
Copy link

ISSUE TYPE
  • Bug Report
  • Improvement Request
  • Enhancement Request
  • Feature Idea
  • Documentation Report
  • Other
COMPONENT NAME
[Import-Export Instances]
CLOUDSTACK VERSION
CloudStack 4.19.1.1
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
STEPS TO REPRODUCE
Attempt to import Windows VM from VMWare
EXPECTED RESULTS
Import succeed and can run VM in KVM host normally.
ACTUAL RESULTS
Import Succeed, but when start VM and stuck at "Booting from Hard Disk | No Bootable Device Found"

Windows VM stuck at booting
@boring-cyborg boring-cyborg
Copy link

boring-cyborg bot commented Sep 6, 2024

Thanks for opening your first issue here! Be sure to follow the issue template!

@sureshanaparti
Copy link
Contributor

Hi @kimchheng-dev Have you noticed any errors during virt-v2v conversion in the KVM host agent logs? Can you share the agent log.

@kimchheng-dev
Copy link
Author

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%)
2024-09-03 16:42:15,400 INFO [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) [6823.0] Creating output metadata
2024-09-03 16:42:15,445 INFO [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) [6823.0] Finishing off
agent.log.2024-09-03.log

@sureshanaparti
Copy link
Contributor

@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.

2024-09-03 14:48:50,286 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) [  17.9] Converting Windows Server 2022 Standard to run on KVM
2024-09-03 14:49:20,434 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) virt-v2v: This guest has virtio drivers installed.
2024-09-03 14:49:21,088 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) [  48.7] Mapping filesystem data to avoid copying unused and blank areas
2024-09-03 14:49:23,684 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) virt-v2v: warning: fstrim on guest filesystem /dev/sda1 failed.  Usually 
2024-09-03 14:49:23,684 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) you can ignore this message.  To find out more read "Trimming" in 
2024-09-03 14:49:23,684 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) virt-v2v(1).
2024-09-03 14:49:23,684 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) 
2024-09-03 14:49:23,685 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) Original message: fstrim: fstrim: /sysroot/: the discard operation is not 
2024-09-03 14:49:23,685 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) supported
2024-09-03 14:49:23,685 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) [  51.3] Closing the overlay
2024-09-03 14:49:24,304 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) [  51.9] Assigning disks to buses
2024-09-03 14:49:24,305 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) [  51.9] Checking if the guest needs BIOS or UEFI to boot
2024-09-03 14:49:24,305 INFO  [resource.wrapper.LibvirtConvertInstanceCommandWrapper] (Script-1:null) (logid:) (virt-v2v ovf source: /mnt/8d264c68-af57-3a0e-a12d-eef6dedbf890/4b3ab6fb-416b-41af-a947-d6a5f8a79be2/ progress) virt-v2v: This guest requires UEFI on the target to boot.

@kimchheng-dev
Copy link
Author

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.

@sureshanaparti
Copy link
Contributor

Try after VM detail/setting update - UEFI: LEGACY.

@kimchheng-dev
Copy link
Author

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"}
2024-09-06 13:18:10,391 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-20:ctx-8cc8fe02 job-27644/job-27646 ctx-eecd52ea) (logid:272b5ab1) Done executing VM work job: com.cloud.vm.VmWorkStart{"accountId":2,"dcId":0,"vmId":8911,"handlerName":"VirtualMachineManagerImpl","userId":2,"rawParams":{"ConsiderLastHost":"rO0ABXQABHRydWU","BootMode":"rO0ABXQABkxFR0FDWQ","BootType":"rO0ABXQABFVFRkk","UefiFlag":"rO0ABXQAA1llcw"}}
2024-09-06 13:18:10,393 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-20:ctx-8cc8fe02 job-27644/job-27646 ctx-eecd52ea) (logid:272b5ab1) Complete async job-27646, jobStatus: SUCCEEDED, resultCode: 0, result: null
2024-09-06 13:18:10,395 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-20:ctx-8cc8fe02 job-27644/job-27646 ctx-eecd52ea) (logid:272b5ab1) Publish async job-27646 complete on message bus
2024-09-06 13:18:10,395 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-20:ctx-8cc8fe02 job-27644/job-27646 ctx-eecd52ea) (logid:272b5ab1) Wake up jobs related to job-27646
2024-09-06 13:18:10,396 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-20:ctx-8cc8fe02 job-27644/job-27646 ctx-eecd52ea) (logid:272b5ab1) Update db status for job-27646
2024-09-06 13:18:10,398 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-20:ctx-8cc8fe02 job-27644/job-27646 ctx-eecd52ea) (logid:272b5ab1) Wake up jobs joined with job-27646 and disjoin all subjobs created from job- 27646

management-server.log

@sureshanaparti
Copy link
Contributor

Ok, Can you share the host details (OS, arch) used for conversion. Check the supported conversions list here: https://access.redhat.com/articles/1351473

@kimchheng-dev
Copy link
Author

My KVM host is:
NAME="Rocky Linux"
VERSION="8.10 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.10"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.10 (Green Obsidian)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:8:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2029-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8"
ROCKY_SUPPORT_PRODUCT_VERSION="8.10"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.10"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sureshanaparti @kimchheng-dev