How about doing your own matrix?

@dvdhngs install onto (mdadm/ZFS) RAID 10: no to use (mdadm/ZFS) RAID 10 as SR: yes, of course!

@danp said in XCP-ng 7.5.0 final is here: @dblogic said in XCP-ng 7.5.0 final is here: Just tried updating our pool and after updating the master had failed migration of VM (Ubuntu) and then was unable to get VM to start (Missing VDI error). Only solution was to roll master back to 7.4 and everything working again. I ran into a similar situation when I upgraded to 7.5 this week. Did you check to see if there was a non-existent ISO mounted in the CD rom for the VM in question? Thank you. That was my problem. I gave cd empty. Everything works.

Actually, looks like I had already written something about it in the Updates Howto: https://github.com/xcp-ng/xcp/wiki/Updates-Howto#a-special-word-about-xcp-ng-75-76-and-live-migrations

@olivierlambert @prilly Just loaded the XCP-ng 8.0 successfully on a Dell C6100 with 2 x L5630. No errors during install, and boots up just fine for use.

Here are my results on different versions of Windows Server (using Standard Edition). I used the same procedure indicated above. For each system, I update all the operating system to last version possible before installing PV drivers (thanks optic fiber ). Windows Server 2012 R2 Core : successful install, VSS seems good (stable state and no error), soft shutdown and reboot OK. Windows Server 2012 R2 Desktop Experience : successful install, VSS seems good (stable state and no error), soft shutdown and reboot OK. For both Windows Server 2012R2, they require more reboot, especially one more for the storage PV drivers after the installation of network PV drivers, but it works. Windows Server 2016 Core : successful install, VSS seems good (stable state and no error), soft shutdown and reboot OK. Windows Server 2016 Desktop Experience : successful install, VSS seems good (stable state and no error), soft shutdown and reboot OK. I don't know if it's very useful to test on Windows Server 2008/2008 R2 since the extended support will reach his end of life in the next January. But I can provide tests if required.

Hello dear RC testers! We are releasing 7.5.0 final today, so here's how to go from 7.5.0RC to 7.5.0. Warning: this is only for people who installed the RC. Detailed procedure will be given in the release announcement for upgrading an XCP-ng 7.4 server Option 1, upgrade using the installation ISO Will work, although may be a little overkill since you already have a nearly-final 7.5.0. Option 2, update yum repository files and update the system # remove the RC-specific repository file if present rm /etc/yum.repos.d/xcp-ng-7.5.repo -f # install the 7.5 official repository file wget https://updates.xcp-ng.org/7/xcp-ng-7.5.repo -O /etc/yum.repos.d/xcp-ng.repo # update. If you had updated your RC regularly, this will install nothing, else you'll get a few packages yum update # if the kernel or xen-* packages got updated, reboot your server # that's it, you've got 7.5.0 final!

@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

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

Just updated my homelab server from XCP-ng 7.6 to XCP-ng 8.0 Beta, so far so good. I also tested the new experimental UEFI mode with Windows VM, seems good too. I also tested the new XOA deployment through the Web interface of my host, perfect ! We will see during the following week how it goes

@maxcuttins There are two packages. User level blktap driver that you referred blktap and a builtin kernel driver blktap2. Said patch is against mainline kernel as additional driver. You still need to have user land blktap from https://github.com/xapi-project/blktap There are instructions lying around https://xcp-ng.org/forum/topic/122/how-to-build-blktap-from-sources/ to build user land blktap (its without patch).

@sfx please take a look here, there are several discussions there: https://github.com/xcp-ng/xcp/issues/107 olivierlambert created this issue in xcp-ng/xcp open Software RAID install on previous used mdadm disks #107

@redalert11 Thank you, I can now add my AEOTEC Z-wave key to my jeedom VM. But this key doesn't appear in my debian 9 VM. On my server : lsusb Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 003 Device 003: ID 0658:0200 Sigma Designs, Inc. Bus 005 Device 002: ID 10d5:5a08 Uni Class Technology Co., Ltd Bus 005 Device 003: ID 0624:0248 Avocent Corp. Virtual Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Sigma Designs is my USB key I want in my VM. Thanks to @redalert11, I enable the passthroud in XC-ng center. I attach the Sigma Designs key to my Jeedom VM (under Debian 9) I start the VM. lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Sigma Designs is missing. Any Idea ? (tried with Debian 8, and Ubuntu 18.04 LTS, Windows 10 same problem). But no problem when I passthrough the same aeotec key on a Debian9 vm under vmware

Alright. Thanks for letting us know.

What you found is a pretty old and outdated thread, and conclusion is: It's not limited - and there's no real difference between 1 and 10GE. In case it's limited to protect mgmt-int, it would scale with 10GE, but in fact it doesn't.

@Ced76 Ced thanks for the script.

Hello, My idea was to passthrough GPU to specific VM. According to many informations from the Internet, I'm doing this like that: /opt/xensource/libexec/xen-cmdline --set-dom0 "xen-pciback.hide=(03:00.0)(03:00.1)" but still even after reboot I see it on lspci xe vm-param-set other-config:pci=0/0000:03:00.0, 0/0000:03:00.1 uuid=c41704d0-a1f2-6bc1-fe2e-adc26697e636 for old Nvidia 8600 and GT430 it doesn't work - Windows VM see that device, drivers are installed but all the time I have error 43 and this device is stopped for Radeon 7870 it work ok Audio and USB is working with that metod also. Is this connected with Vbios of this GPU's ?

@olivierlambert Okej, its that part that's tricky Yea maybe so, but it's cool. And makes the uptime better even if it's just a lab. I've been using vmware for a while at my last work. But the licensing is not nice for a homelab. So this is my first time with xcp-ng (xenserver). I'll try updating tomorrow. Thanks.

@KapilBandlish I don't understand. You are using XCP-ng and talking about Citrix support recommending something? As @borzel said, thin pro on block device via GFS2 is NOT support in XCP-ng, because the storage drivers aren't open source.