XCP-ng 8.3 betas and RCs feedback 🚀
-
ISO NFS can't seem to mount with an IPv6 address as it leads to a "DNS Error."
Error code: SR_BACKEND_FAILURE_140 Error parameters: , Incorrect DNS name, unable to resolve.,sr-probe is able to find the target/paths and VDI SR NFS is able to mount using the same path. Tried with and without brackets but no success on the NFS ISO side
-
@laurentm What's the dedicated topic? We can discuss there.
-
@lethedata Can you share the command you're running and the corresponding SMlog?
Thanks
-
-
Just providing feedback:
Love the XO interface at the start, very helpful. Also, I do like the colour scheme. It turned a few heads in the datacentre the other day.
Using a Dell R740xd with 2 GPU's to pass through - Works fine and given the GPU's to a VM each (for 3D mapping).
After watching Lawrence Systems device passthrough vid, I managed to view a PUSB in the XOA via the host. I managed to pass it through to a Windows 10 VM but cannot see if in the device manager. Assuming that this still in beta stages so will try a different set of USB devices for testing but so far the Seagate RSS LLC_00000000NAB7AQ06 doesn't show in Windows.
Happy to test further
-
@cunrun said in XCP-ng 8.3 beta
:Just providing feedback:
Love the XO interface at the start, very helpful. Also, I do like the colour scheme. It turned a few heads in the datacentre the other day.
Using a Dell R740xd with 2 GPU's to pass through - Works fine and given the GPU's to a VM each (for 3D mapping).
After watching Lawrence Systems device passthrough vid, I managed to view a PUSB in the XOA via the host. I managed to pass it through to a Windows 10 VM but cannot see if in the device manager. Assuming that this still in beta stages so will try a different set of USB devices for testing but so far the Seagate RSS LLC_00000000NAB7AQ06 doesn't show in Windows.
Happy to test further
Did you run a scan for changes (the icon of a monitor with a magnifying glass) in that Device Manager window? It will then check for new drivers to install and prepare for use. Prompting for device driver installation if required.
-
@Andrew said in XCP-ng 8.3 beta
:@ravenet I did not have any problems with my Mellanox Connect-4 Lx card during upgrades from 8.2.1 (5.0 driver), to 8.3 (5.4 driver), then update to current 8.3 (5.9 driver), and then update to Xen 4.17.3. My card has the 14.32.1010 firmware. It is not used for the management interface. It is used by VMs and continued to keep the same ethernet name and function for the VMs.
Thanks for testing
I finally got around to updating the firmware on this Mellanox connectx-4 LX adapter. Bit of jumping through hoops to install tools, find proper firmware, but went from FW version14.18.1000 to New FW version: 14.32.1010. Had to do an emergency network reset again, but it's back.
Obviously an incompatibility with the new 5.9 driver with much older mellanox firmware.
-
@ravenet This worries me because I use the Connectx-3 cards in my setup. I wonder if I am going to run into the same problem or is it only a Connectx-4 problem.
-
@Anonabhar I don't think so as the ConnectX-3 is supported only in the older 4.9 drivers and not the newer versions (5.0 or 5.9 or newer). As all of these cards are old and EOL, it would be good to have the latest/last firmware installed anyway.
-
Any reason why xcp-ng is focussing on back porting kernel drivers and fixes to an old kernel instead of using a newer kernel and porting back in what is needed for xcp-ng?
-
@john-c Yeah, tried all of that. I get the same issue with older GPU's when vGPU'ing them. So I'm wondering if it's a setting on the Dell Server BIOS.
-
@xerxist Who says we're not doing both?
-
@Andrew @Anonabhar Indeed, it's not the same driver so the old card will keep using the old driver.
-
@cunrun said in XCP-ng 8.3 beta
:@john-c Yeah, tried all of that. I get the same issue with older GPU's when vGPU'ing them. So I'm wondering if it's a setting on the Dell Server BIOS.
Have you enabled SR-IOV in Integrated Devices on the Dell Server's BIOS?
-
-
Which kernel are you looking at since 4.19 will be EOL in 9 months?
-
I applied the very last batch of XCP-ng 8.3 updates and after a smart reboot (which took forever to complete and did not resume all my VM automatically), I have lost my ISO storage: the folder "/ISO" has been deleted by the update and the fstab has been overwritten. This is becoming annoying, I never ever had to "repair" anything related to my storage in my 20 years of using Vmware Esx but this is already the second time I have to do it in my 2 years of using XCP-ng and the very first time an update deletes a mounting point. I understand 8.3 is still a beta, hence my feedback.
-
@ThierryC01 Why are you using fstab?
-
@Tristis-Oris Well, this is how local disks are mounted right?
-
@ThierryC01 possible way, but not only one. It recomended to configure nothing at dom0.
literally created 2nd local storage with 1 click:
