@lsouai-vates Great! Thanks for addressing this

@idar21 said in Xen Orchestra 5.110 V2V not working: I certainly didn't mean to dismiss the significant work that's already been done. At the same time, I think it's important for us all to be open to constructive criticism. Sometimes, even with the most thorough testing, unique configurations slip through the cracks, and that's nobody's fault—it's just the nature of complex IT systems. That was exactly my own point. And this forum is filled with posts of us solving bugs from people's feedback, all along from the last 10 years at least. So we do appreciate a LOT any constructive feedback: we want to fix what's broken, even for free! I was talking about this sentence: I don't think the tool has been tested properly. Which doesn't sound very constructive in my opinion. That was my point, nothing more. Constructive feedback: yes. Non-constructive feedback: no. So let's move over, to be able to assist, we need to know your XOA version (or XO commit), exact ESXi version, the kind of storage you use. That is the base of constructive feedback

AlmaLinux 8.10

so it seems like when i make the igpu pass through, i see the starting lines of xcp-ng but it never gets to the console screen. which is what i expect. When I add the pcie devices (igpu/hdmi audio) to a vm and start it up, I get and update to the screen and it shows a red number counting which is part of the console. So it seems that when the VM re-initializes the igpu, dom/xcp retakes it over. I confirmed that by using the keyboard to move around and it reshowing the console and filling the missing details as i move around. So why is the dom/xcp retaking the video device over again when it should be blocked from accessing it? [image: 1756568880819-img_3348.jpeg]

@Greg_E Ah, ok..yeah...guess I did Yep, agree. Really needs more functions...like networking (and elsewhere) ha

looks good Xen Orchestra, commit 384bb Master, commit 384bb thanks for quick fix

@AtaxyaNetwork said in Unbootable VHD backups: @Schmidty86 Try to detach the disk and reattach, it should be xvda in order to be bootable That's what I was thinking as well, but obviously something is off with this VM. @Schmidty86 is the old host still online? If so you might be able to perform a Live Migration or a replication job to copy it from the old host to the new.

@Andrw0830 I am using paid version of ESXi / vSphere. The free version of ESXi has so many limitations that I consider it pretty much unusable / only usable for very limited basic tests. It would not suprise me if your issue is due to the license limitations within ESXi.

@florent so it's like https://github.com/vatesfr/xen-orchestra/commit/a459015ca91c159123bb682f16237b4371a312a6 might introduced a regression? 0 fbeauchamp committed to vatesfr/xen-orchestra Fix(replication): VDI_NOT_MANAGED error (#8935) from ticket #40151

@utopianfish said in 10gb backup only managing about 80Mb: @nikade i think the problem is its using the mgmt interface to do the backup..its not touching the 10GB nics.. when i set it under Pools/Adanced/Backup to use the 10gb nic as default the job fails... setting it back to none the job is successful with a speed of 80 MiB/s.. so using the 1GB mgmt nic... how do i get the backups to use the dedicated 10gb link then. ? May I ask why your management interface is not on the 10G nic? There is absolutely no downside to having that kind of setup. We used this setup for 7 years on our Dell R630's without any issues at all. We had 2x10G NIC in our hosts and then put the management interface on top of the bond0 as a native vlan. Then we just added our VLAN's on top on the bond0 and voila, all your interfaces benefits from the 10G nic's.

Partly, I will see when back from vacation Anyway, unrelated to XO

Thanks everyone for their help. I believe I have a way forward now.

Excellent news!

@AlbertK said in XCP-ng - XOA vs. XOCE: @Danp , Is it possible to add the comparison of the XOCE together wit XO in this page?. https://vates.tech/pricing-and-support/#features-matrix XOCE is a term that I came up with when I originally started writing the deployment script that exists today. It's stuck around. Vates uses the terms XOA and "XO from Sources" as their unique products. XOCE would be "you used a github script to deploy" (my github) XO. XO from Sources is a completely manual process where you're following the documentation to deploy XO. This approach gets you the same thing that XOCE does, but takes longer to complete since you're finishing each step over SSH rather than running a single bash command on a Ubuntu/Debian VM.

@Greg_E thanks for the clarification.

@splastunov said in Intel x710-t2l Problems: xe vif-param-set uuid=VIFUUID other-config:ethtool-tx="off" xe vif-param-set uuid=VIFUUID other-config:ethtool-rx="off" Hi! Thanks for your input. I set the vif parameters as suggested and am still unable to ping the gateway.

@Bastien-Nollet Thanks as always @florent

@chicagomed said in Passthrough Contention Problems with Console and Linux VM: @TeddyAstie great will take a look this weekend. Is there anything in particular you want us to test / check out? What works/doesn't work and overall performance.