The initial reason we've chosen to create an "all-in-one" ISO image was to simplify further configuration of an automated installation with PXE / Answerfile. We tried driver disks before, though in our special case of mellanox-mlnxen-alt and hardware without any other NICs, I believe it always ends up requiring manual intervention. I haven't found a way to load the driver disk in the installer that is not connected to the network. I think, even though my approach requires a bit more effort, it can still prove useful in some cases.

@flakpyro i try to find a new version but site and search only found 3.3.0. When try to search again in a proxmon forum found the repo xD

Hi @qwkcroc, Unfortunately there are no packages available for XCP-ng right now. The current work for Q35 support takes place on top of upstream versions of Xen and Qemu that are more recent than the ones ran by XCP-ng. Once upstreamed it will be possible to backport it (and we will do so of course) but it's not yet planned. Also, additionally to Xen and Qemu, there will be work needed on the XCP-ng toolstack before being able to enable Q35 support and PCIe device passthhroug. My work trees are available for both Xen and Qemu so if you feel adventurous enough you can give it a try. I was able to passthough an NVMe device to a VM using this kind of setup (with some hacks in Qemu though...). Regards, Thierry

@gb.123 In XO on the "Advanced" tab for the VM I added the GPU devices by first adding them both as "Attached PCIs" near the bottom of the page. I also disabled the "VGA" option under "Xen Settings" and clicked the "+" next to "GPUs" and added the vGPU type "passthrough () 0x0" which was available on the drop-down list. I don't know if it matters or not, but I also set the "Static Max", "Dynamic Min", and "Dynamic Max" memory limits under "VM limits" to the total RAM size I allocated the VM.

Ahh excellent news! Thanks for keeping us posted

@dmz0001 In theory, XCP-ng 8.3 is mostly on par with XenServer 8.4, it's only a naming thing that they did as their previous naming was confusing some of their customers. Long story short, XCP-ng ~= XenServer 8.4. So what you see in the compatibility list of XenServer 8.4 is the right reference for XCP-ng 8.3. Unfortunately we do not have much feedback on Zen 5 at this time on our side.

@TeddyAstie Thanks for the input. This is what I was afraid of somehow In the meantime (a few months ago) I have done some tests with the machine. Installed opnsense as described in the opening post and directly to the device without xcp-ng just to see if there is any issue. The result is the same (i have used in both cases the same settings and same spoofed mac) the spoofing did work without xcp-ng, this is why I was hoping that something can be done via xcp. @olivierlambert said in NIC Passthrough with mac spoofing: Out of curiosity, what about SRIOV in that case? Regarding SRIOV right now its not possible for me to check if thats enabled/supported in the bios but its a good point, thanks Will take about 3-4 weeks to check.

@XCP-ng-JustGreat I only use the passthrough part of disks, not controllers. VUSB part in xo i don't use. I think that's a completely different approach. Maybe you could check your drivers and manager. There is a cleaner somewhere, don't know the link, to remove the old drivers in windows with powershell and after that install the xen drivers XenServer VM Tools for Windows 9.4.1. I got it from here: https://www.xenserver.com/downloads https://github.com/xcp-ng/win-pv-drivers/releases/download/v9.0.9065/XenClean.zip docs: https://docs.xcp-ng.org/vms/#fully-removing-xen-pv-drivers-with-xenclean

No, it's not possible to choose explicitely/easily them because they are all the same from Xen perspective. I wonder if you can "cheat" by doing vCPU pinning though

@MasterOSkillio Typically, C-states need to be changed in the BIOS. In some cases, it can be very helpful. I wrote a few blogs including this topic entitled "A Tale of Two Servers" but cannot readily find them on-line at the moment. Alas, Citrix has purged a lot of still relevant older content over the years.

Reping @dthenot

@GTwannabe I assume he means using PCI passthrough for the USB port/controller so HA has direct access to that level of the hardware to circle around some USB passthrough problems. In my case this did not helped with the ConBee, but you might try it anyway and it is no problem to reboot the host which is needed to activate the PCI passthrough Another pro for switching to an IP based controller is that you can backup and migrate the VM without any problem.

@sotero could you post the output of: # Collect xen info xl info # Collect C-States info xenpm start 3 ?

@Nevering We used to offer a “hosted Vates Stack” service, but right now we’re rethinking that and don’t have anything "official" to share just yet (though you might wanna keep an eye on our newsletter ). In the meantime, here are two easy options: Head over to our Partner Locator and use the filters to find a CSP (Cloud Service Provider) — some MSPs also offer hosted setups. Shoot us a message at partners@vates.tech or via our Contact Form, and we’ll do our best to point you in the right direction.

@Riven, What I am not sure is how Xen arrange the CPU, is it core first followed by the SMT/HyperThread Core? or is it alternating ie RealCore, HyperThread Core.

@2planks said in NIC not working on new HPE DL360 Gen11: Has this issue happened before? I don't remember such an issue on this hardware. Can you share the outputs of lspci -v, lsmod, dmesg, and dmidecode?

@efny I thought it wouldn't but in fact since I have it (almost a year) I had 0 bug. It's a Core i7-1255U.

@olivierlambert Looks like it would arrive April 14th: https://www.dell.com/fr-fr/shop/intel-flex-140-pcie-75-w-12go-passif-unique-wide-profil-bas-gpu-installation-par-le-client/apd/490-biio/cartes-graphiques

@MJGZ51 Hi! Since 8.3 PCI passthrough is part of the XAPI and come with dedicated xe commands: xe pci-list to have the list of PCI devices and then: xe pci-disable-dom0-access uuid=<pci uuid> to hide th device from dom0 xe pci-enable-dom0-access uuid=<pci uuid> to unhide the from dom0 These are the same API calls made by XO or any XAPI clients No need to edit manually the cmdline anymore! Regards