On vmware u would need als vcenter for this kind of features. And as u can easy deploy an empty xoa, why would this be an issue?

@olivierlambert nice catch It's following a dependencies update, removing an old one ( node-fetch ) . The fix should be merged this morning ( with the ability to resume an import ) https://github.com/vatesfr/xen-orchestra/pull/8440 fbeauchamp opened this pull request in vatesfr/xen-orchestra closed feat(v2v): resume an incomplete import #8440

@dinhngtu it still wouldn't boot with the correct template. That said, I have been testing other VMs which were created on xcp-ng, with the correct templates, and get better performance out of them when they are migrated to a hyper-v host. I believe that this is related to SMAPIv1 limitations - which are known and being actively worked on with SMAPIv3. Unfortunately for us at this point, xcp-ng may not fit our business - hopefully one day soon it will be, but until then, it is what it is.

@jcharles said in xo-cli vm.importFromEsxi give error: JsonRpcError: can't get runtime of object devtest1 (Type: VirtualMachine): ssword=XXXXX sr=2e9ff937-6c4c-86c5-81d2-18331c69bbe5 sslVerify=false stopSource=true user=root template=39f341be-b9aa-c7fd-33a9-355312c2246a vm=devtest1 vm should be an number it is the id in the URL in esxi

@Danp Ah yes, I hadn't taken a fresh snapshot. And per your recommendation restarting xo fixed the problem as well. Brilliant, thanks!

The problem has solved itself. XCP-ng installer can't even be run on my PC (with UEFI). Some core-dump pops up and resets. For a test, I tried the installation on an old but problem-free laptop (in BIOS mode). Installation without a problem, but does not boot (OS not found). I have to look for another hypervisor. If the installer is already causing problems, then I don't want to know what to expect next. So the topic can be closed and even deleted.

@ItsAlwaysDNS said in Migrated Linux machine won't start: @DustinB I can try to give that a go. Is there any particular reason as to why we think this will work? I'm totally fine with the thought of "its worth a try". I'm just curious if there is some known compatibility issue that is leading you to suggest trying this as a solution. Normally these older systems were required to use the ESXI drivers, these drivers are also normally very out of date and cause issues. Most of the time, when these issues occur, it's because of incompatible drivers. Cloning the VM and removing the drivers from the clone and then trying to migrate the VM is the safest way to confirm the issue is with the drivers without impacting your production system.

@psylo xensource.log and daemon.log will usually give more information about failed operations. It could also be an issue in XOA's warm migration code in specific cases.

I might have hard time to give you a confirmation, but worth checking on the VMware side, yes

@Cygace XO is not directly tied to XCP. So the versions have nothing to do with each other. You can look at the XO master commits and pick one that lists feat: release 5.xxx.x and that will line up with a XOA release. You can pick a version that is the same as the current XOA release and it will be the same tested base code.

Thanks, that's very useful info! @florent will take a look when he can!

I don't think that's going to be an issue with Vates, they have ppl in different parts of the world and they're very helpfull. Reach out to them and link this forum thread, im sure they will be able to get you going even tho you're in Australia.

@ph7 said in Error starting network UPS tools (NUT) driver for TrippLite USB-passthrough: @waveguide I used the PCI passthrough for my zigbee USB Dongle and it has been working perfectly since I installed it 2½ month ago [image: 1738063996972-c349c774-c4bb-4dde-97f9-887521e2a871-bild.png] Interesting idea. I am running on a Dell R710 and the USB controller is not listed as an available PCI device that I can passthrough to the guest VM. It does come up on the host as a PUSB device. The ESXi server was also an R710. [image: 1738113146366-525ece0c-93c4-4cd0-8ce5-c001961959c2-image.png]

@TheLastOtter Strange. I think you touch nothing on your side?

You can deploy multiple XOA if it's your question, one to export in OVA, one to import the OVA.

Not looking to revive this topic but wanted to post this documentation I found in case anyone else searching for answers stumbles here like I did. There are too links on this site that address some limitations that are not readily documented in the standard migration documentation. https://help.vates.tech/kb/en-us/37-import-export-migration

@Don-Gould-NZ I wonder if this system got cloned as intended. I see 2 devices in XO, that will be xvda and xvdb. Yet earlier you listed it was one device with two partitions. The 512M size of the 2nd device makes me wonder if the migration turned the disk partitions into devices with partition/swap signature and nothing else. As such since the system looks for xvda's 2nd partition for root, there's no partitions so naturally it fails. You could get SystemRescueCD, boot off that and investigate the devices.

@Andrew I did not see a serial port listed. I'll just get a USB version and plug in to server and see if I can pass thru it. If it works, I can get rid of another Destop server and be fully virtual. Thanks for your hellp.