@stormi I know this is quite an old topic, but this is still happening on XCP-ng 8.2.1. Do we need to update the RPM manually still or should this have been dealt with in the newer versions?

Only when we'll have a more recent kernel in Dom0 🙂 But this will come at some point.

Sadly, it's not that simple. Allowing to change the partition layout will add probably a lot of complexity to maintain. However, we are not against a contribution, then we could judge the risk on getting it upstream or not 🙂

Sure, let me come back to you this week!

I am playing a bit with SMAPIv3, I created a storage of type file in /mnt/ and a VM, after restarting xcp-ng /mnt/ was not mounted so the storage was not mounted, I did it manually and when starting the VM Throw me

Error code: SR_BACKEND_FAILURE_24 Error parameters: VDIInUse, The VDI is currently in use

I did a detach to the disk from the vm and I also deleted the vm and created a new one but it still gives the same error.

detach and repair does the same

@cyoung_mi It's a XCP Xen/Kernel code issue... So if that can be fixed then yes.

@Andrew Let's start with igc.

Install git-lfs if not done already, fork and clone https://github.com/xcp-ng-rpms/igc-module/ and then create a PR against the 8.2 branch, based on the existing spec file.

@TheFrisianClause

From my experiments using a GTX1080ti you'll have to follow the instructions for generic pcie-passthrough to the letter, which mostly means that the passthrough needs to be done on both sides, on the Dom0 for relinquishing device control and for the DomU to pick up the device (section 5). Perhaps now that the restrictions from Nvidia have gone, Vates will kindly include some GUI support for those operations in XOA.

Note, that if your dGPU has multiple devices (e.g. my GTX 1080ti also has a USB-C controller on-board), both entries need to be added in a single 'xe vm-param-set' statement, otherwise only the latter device (USB in my case) will wind up in the VM.... (yeah, at least 30 minutes of puzzling on that one)

Of course, if the dGPU is your console device, it means flying blind afterwards, but I'm getting used to that with all the recent iGPUs as well (then again, I have some DisplayLink hardware that's currently unused and EL7/8 drivers for those have popped up recently...)

Thankfully the dreaded error 43 issues have gone away with the more recent Nvidia drivers, sadly Kepler support has been retired (got a lot of those still around), so you may want to preserve the latest CUDA 11.4 release as one that offers both, but for Maxwell you should still be fine.

Before trying to diagnose with the Nvidia drivers, you should be able to see the device transition via lspci on both sides, Dom0 and DomU.

@rajaa-b no problem

@jedimarcus true, but as this is the development part of the forum, I'm more coming from a "Nice to have" request.

The obvious solution is multiple orchestra servers 😉

Indeed, we are close to finish it, maybe even March release 🙂 Hang on!

Guys, would it be possible to use a Matrox G200EH as a vGPU? I see my vm using a basic microsoft video

da9dd982-146c-4a2d-a72a-9c490b517ee7-image.png

@stormi Nope.... my mistake. Now ubuntu 20.04 and Windows 2016 boot with UEFI Secure Boot enabled.

# secureboot-certs install No arguments provided to command install, default arguments will be used: - PK: default - KEK: default - db: default - dbx: latest Downloading https://www.microsoft.com/pkiops/certs/MicCorKEKCA2011_2011-06-24.crt... Downloading https://www.microsoft.com/pkiops/certs/MicCorUEFCA2011_2011-06-27.crt... Downloading https://www.microsoft.com/pkiops/certs/MicWinProPCA2011_2011-10-19.crt... Downloading https://uefi.org/sites/default/files/resources/dbxupdate_x64.bin... Successfully installed certificates to the XAPI DB for pool.

@stormi, @olivierlambert

Thanks to everyone, I was able to complete it.
Thank you very much!!

Solved the problem by explicitly specifying the data type

$resize = 'VDI.resize'; $xcpapi->$resize($vdi, ''.(int)$hdd2.'');

Doesn't work without brackets

''.(int)$hdd2.''

@andrew Yes indeed, those are known shortcomings:

The installer does not wipe previous RAID setups. It does not offer to create another RAID for data storage. There's an extensive guide about this at https://xcp-ng.org/docs/guides.html#software-raid-storage-repository

Your starting point will be https://xcp-ng.org/docs/develprocess.html#local-rpm-build

Yes, I told them we'd like to cooperate to release something faster.