@jiri.hadamek Yes, it's a driver bug. I'll plan for a fix.

Hello, We've added a card to our backlog to investigate this topic.

@afk said in What is the status/roadmap of V2V (Migrating from VMware to XCPng/XO) ?: Great news ! Thanks @olivierlambert and @florent and let me know if you need some information on the vmware side. yes we are prototyping with vddk , it should open some interesting possibilities. stay tuned, hopefully by the end of the summer (I am saying it again : for a prototype) as a shameless plug, we are looking for users with VSAN to ensure we don't break thing for it

I probably would have just bought a cheap mini PC and used Virtual Box for this, which is something I did do in the past for an old XP machine when the hardware started to fail. Grabbed a disk to vhd of it before the final failure and loaded it into Vbox. Might be able to do this in nested virtualization in XCP-ng.

@iLix The sizing of the VM in XCP-NG was bigger compared to the source

@bpsingh76 said in xen 7.2 vm to xcpng 8.2: We have a VM on Xen server 7.2 and due to some reason we cant migrate it to xcpng. So, we exported xva of the VM, restored it on another xcpng 8.2, restore was successful but when we tried to start, it said no VM. we checked with another it was same. Can someone please suggest solution urgently. Setup Xen Orchestra and use the live migration feature. I have a link in my BIO or you can follow the from sources documentation.

@AlbertK said in MS SQL 2016 migration Question: @DustinB , I am also looking for what are the gotcha or limitation that one have to look out for and plan before even looking at migration. So as @tjkreidl said, use the same considerations that you would use for Hyper-V or VMware, those same considerations were completed by someone, at some point. There are a few assumptions we can make though: You're either planning to reuse your existing VMWare hosts OR are getting new hardware This hardware is going to be able to support everything you have today +20% increase in workload over 5 years Things to do ahead of a migration, assuming you're migrating an existing VM from VMWare to XCP-ng. Uninstall the VMWare drivers from the guest ahead of time If you aren't licensed by VMWare for Hot-Migration, plan downtime to shut the guest off as you will not be able to migrate it live from VMWare (VMWare restriction). Setup your XCP-ng host with all networking ahead of any migration, VLAN configurations, Management interface statically assigned, PIFs bonded ahead of adding any VMs etc. Create your pool with all hosts first - ideally each host will be identical (same hardware configuration) Install XCP-ng on each host Setup Xen Orchestra and connect to each host to XCP that will be in the pool Select a host to be your pool master (this can be changed later) Add the remaining pool members to the pool Shared Storage for your VMs is configured and attached to your XCP-ng Pool for both ISO's and VMs Use an SSD array if you can for the best performance Use a Standing Spinning array for the "C" drive Everything else is pretty straight-forward, hope this helps.

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.

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.