Hi, We are working on mirrors, expect some news in the next weeks

At the moment https://github.com/xcp-ng-rpms only contains repositories for the packages that we had to modify. For other packages, you can find their sources in the source RPMs in https://updates.xcp-ng.org/7/7.6/base/Source/SPackages/

@olivierlambert Of course. Right now I just got enough information to start the modification on the script which I start tomorrow. In fact, all that is needed to get usbnics working properly in xapi is simply being able to identify usb locations. THAT'S IT! All NICs if you look in the logs are initially named side then because the rename script runs and after properly identifying it assigns a ethxx name which the api will work with. All this would take is an import command and a few if commands. I got the logic down so now it is just about editing, trial and error. Question regarding: import sys, logging from optparse import OptionParser, OptionGroup from os.path import join as joinpath, normpath, exists as pathexists from subprocess import Popen try: import cStringIO as StringIO except ImportError: import StringIO import xcp.logger as LOG from xcp.pci import PCI from xcp.net.biosdevname import all_devices_all_names from xcp.net.ip import ip_link_set_name from xcp.net.ifrename.logic import rename from xcp.net.ifrename.macpci import MACPCI from xcp.net.ifrename.static import StaticRules from xcp.net.ifrename.dynamic import DynamicRules from xcp.net.ifrename.util import niceformat from xcp.net.mac import MAC for the import command as my google fu was no help for the above xcp.net and xcp.pci what is it specifically referring to? What I have that down we simply need to add and import for usb then modify a few existing calls with the first being if device location = usb format then run the modify version of the script that would have the edited fields to pull the proper usb locations etc. For the vendor and device it would be best and most simple if we refer to the usbvidpid list it can simply call the info from an already large existing database which can also be easily updated and/or modified for an entry. Functionality wise all that is needed is those if commands to make a usb location referable. Then any usb NIC (so long as drivers provided) would be truly plug and play and we could use the existing config to chose a specific ethxx name based on MAC so they survive reboots without further editing anything. Got it is referring to the python libary / libs

@mpyusko it's important to reboot the vm after you cleaned it well. Just if after cleaning and reboot your vm has the two devices and does not find automatically the drivers... then you are ready to install new ones. It 'svery complicated and complex... I don't know why Citrix has gone this way...Not fun to support such mess...

The case is solved. Here is an updated entry in our Troubleshooting Guide: Cause a) There can be leftovers from old Citrix XenServer Client Tools. -> https://github.com/xcp-ng/xcp/wiki/Troubleshooting#the-management-agent-installer-was-executed-but-the-pv-drivers-are-not-installed-in-the-device-manager

Hello all together, here is a updated version of the installer that removes also old citrix tools/drivers: https://github.com/xcp-ng/xcp/issues/23#issuecomment-435696690 olivierlambert created this issue in xcp-ng/xcp open Windows PV tools #23

You can find all ISOs at https://updates.xcp-ng.org/isos/ @olivierlambert we may want to offer a link to that under a "Do you need an older installer?" link on the main website?

Just got a Ryzen 2700X in the lab. Everything works fine (I just lost 10min to find the "VMX" option to enable it in the BIOS)

@fjen I also got the same error... INTERNAL_ERROR(xenopsd internal error: Call to usb reset failed: Forkhelpers.Spawn_internal_error("usage: usb_reset.py attach [-h] -d DOMID -p PID [-r RESET_ONLY] device\nusb_reset.py attach: error: argument -r: expected one argument\n", "", _))

@jtbw911 also I am interest to have Nvidia GPU I try to with GTX 1050 TI but unfortunately nothing successful specially my all test are with windows 10 and server 2016 always got error 43 in driver I hope some one can help

@mpyusko I'm working on a more recent kernel. You can try it on a test machine to see if the problem that you saw initially, repeats. https://github.com/xcp-ng/xcp/wiki/How-to-install-kernel-exp-(4.9)-for-XCP-NG-dom0

@misterpc23 sometimes even lazy people have to go to the cli

Hi there! There is NO way they'll communicate publicly on that. This is specifically true since XCP-ng is out. We can dig around on various GH repo, but a lot of their work is on internal repos, so no chance to get that Regarding the kernel, it will be VERY likely a more recent LTS kernel: 4.9 or 4.14. I would put a dime on 4.9 because it's mature enough and got the longest time before EOL (see https://www.kernel.org/category/releases.html) Regarding Xen, IDK yet, but it will be indeed a more recent version I presume. If you get any info by Open Source Intelligence (OSINT), feel free to share here

@borzel Shhhh....Not so loud,,, my boss can hear u Kidding....lol sitting at work, there I have internet