@jsox79 No I did not.

Disclaimer - I inherited this FreePBX system and don't know a whole lot about it. Once I got it to boot, I tested by calling my cell from a desk phone and making a page, and both worked as expected so I'm considering everything to be working. Didn't realize re-registering modules was something I may have needed to do.

Old thread, but it still pops up in search engines.

I ran into the same issue - booting my freshly migrated FreePBX server dropped me into emergency mode with multiple warnings that various drives/partitions did not exist.

As I still had the VM on VMware, I booted it there, and per the suggestion by @Danp, ran
dracut --add-drivers "xen-blkfront xen-netfront" --force and re-migrated the VM. Once the migration completed, the VM happily booted as expected and prompted for credentials.

@dinhngtu That got my fresh install to boot as well. Thank you!

Sorry for the delayed response - I'm only at this location in the middle of the week.

I installed a handful of pending patches and updated my XO VM this afternoon. After doing so, I was prompted to install a couple of items on the Import from VMware screen, and then was able to start an import as expected. It's currently running the import.

Thanks for your help, everyone!

I have a new xcp-ng pool with two hosts using XO from sources . I went to import a VM from VMware and was prompted to upload a Broadcom VDDK archive. After uploading, the Import from VMware page just shows 'checking'. Past pools I've set up did not prompt for the VDDK, which makes this scenario seem odd to me. Any idea why this is happening and what I can do about it?