I've installed on a HP ML10 G9 server and all works fine on this server using UEFI based BIOS configuration etc. The only issue I have found so far is when imported vmdk images using the wizard, even when I choose to set the BIOS to UEFI after the import and conversation has completed the VM won't boot. After looking at the settings for the newly created VM the BIOS is set to BIOS not UEFI. Simple to resolve either be detaching the storage and removing/recreating the virtual machine and re-attaching the original imported storage. Or I am guessing (although haven't tried yet), using the console to set the machine type. So possibly an issue with the Import Wizard? UPDATED I tried the shell commands to change the imported VM to UEFI, and although initially it looks fine when examining the console and seeing that the BIOS setting has updated. When trying to start the VM it won't boot due to an error. So after detaching the disk and deleting the VM I recreated a new VM using UEFI and no disk attached. Then once created I attached the original imported disk and it works fine. Also I using VirtualBox to export a VM to OCI Format 1.0 which was setup running as UEFI, after the import into XCP it had changed the BIOS to BIOS not UEFI. So again I followed what I did above and the VM works fine. So it does look like an issue with the Import Wizard, although it allows you the option to choose BIOS type it doesn't honour the setting and reverts to standard BIOS.

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

@stormi dd stands for disk dump and does exactly that: Copy a stream of data. Fio however can be configured for precise workloads and read/write mixes, parallel workloads etc. So the first thing will only give you streamline benchmarks, what almost nobody cares about. The second can simulate realworld (VM/database...) workloads, where (controller) Caches and non magnetic storage (Flash, Optane, MRAM...) makes the real difference. Also use big amount of data, since caches can impact small ones extremely. Don't get me wrong: We need them and they can make huge differences, but as long as your benchmarks fully fit into them, it gives your nonsense/fake results. Also (consumer) SSDs start throttling after some 10 to a very few 100 GB of data written. Their caches fill up and they 'overheat'. You can spend days on benchmarks and how to do what.

I tested on a fresh 2016 install. The install went well and the management agent was installed. I enabled VSS but the VSS snapshots don't seem to be working. To compare I installed the citrix client tools on a fresh 2016 install and VSS does work.

Thanks for your input! I think it might be the one then Also, if there is a big problem with it, we can always update the package!

Here's another willing script tester

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!

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

Hey I tried today to update version 7.6 to version 8.0 RC. Sadly the installer did not start. In normal upgrade mode the installer just hangs with a black screen and when i tried the installation in safe mode the installer halted with the message: (XEN)[ 34.0279] Hardware Dom0 halted: halting maschine I have uploaded an image of the boot screen in safe mode: image

@Kudzu he uses OpenLDAP, as he said in this thread earlier.

@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).

Hello, I am Georg, and I am also new to XCP, kind of...at work, we have XEN, but sadly, thats not my business. Long story short, I got nearly everything sorted out, but not USB passthrough. I got all devices showing up in XCP-center, and attached them to the VM. When I start the VM, all USB devices are attached. But as soon as the VM is booting, the status "Attached" changes to "No". [VM -> Properties -> USB] However, what I found out: for example, I attach my keyboard and pass it to my Windows vm: then why I can control the local XEN console with this keyboard I passed through? And this error: "Failed","Starting VM 'Windows 10 (64-bit) (1)' 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", "", _) Time: 00:00:23","xcp-ng","Jun 29, 2019 12:05 AM"

@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

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.