Topics created by stormi

@KPS Hi. This thread is now inactive sop please open a new thread dedicated to your issue.

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

@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

Actually, on any recent enough Linux system (ie not many years old) , the PV drivers are directly included in the kernel. Unless, maybe, a very specific distro decides that they don't want Xen support in their kernel.

So the tools you install on the VMs are merely an agent to make the VM more cooperative with the hypervisor, but they don't affect performance.

The situation is different on Windows systems where you need to install PV drivers to achieve better performance.

The update is now available for everyone https://xcp-ng.org/blog/2021/01/28/security-issue-in-sudo/

@r1 said in XCP-ng 8.2.0 RC now available!:

@jmccoy555 said in XCP-ng 8.2.0 RC now available!:

CephFS is working nicely, but the update deleted my previous secret in /etc and I had to reinstall the extra packages and recreate the SR and then obviously move the virtual disks back across and refresh

Were you not able to attach the pre-existing SR on CephFS? Accordingly, I'll take a look in the documentation or the driver.

No look. I ended up with a load of orphaned discs with no name or description, just a uuid so it was easier to restore the backups.

I guess this is because the test driver had the CephFS storage as a NFS type, so I have to forget and then re attached as a CephFS type which I guess it didn't like! But its all correct now so I guess this was just a one off moving from the test driver.

Anyway all sorted now and back up and running with no CephFS issues! 🙂

Initial brief test seems ok 👍
Will see if i can do more of the tests later...

Updated from 8.1 via yum which caused windows 10 & windows 2019 server to hang on the tiano logo.
Interestingly a debian 10 uefi vm worked fine...

After the update to uefistored both windows VMs started in recovery and did whatever it is windows does besides spin dots on your screen 🤔
After a reboot both Windows 10 2004 and windows 2019 server booted just fine 👍

@hoerup Hi, I can't remember too much to be honest.

I created a Debian 10 VM with 20GB disk, set up all the stuff that needed to be common for the Ceph pool pretty much following the Ceph documentation using the cephadm method - so Docker etc. This would be my 'Ceph admin VM'

Once that was all sorted I cloned the VM 3 times, for my actual Ceph pool and changed the hostname and static IP etc. I've got 3 hosts with Supermicro boards that have two SATA controllers on board, so on each one I passed though one of the controllers to the Ceph VM and then just deployed Ceph and followed the documentation. The only issues I ran into and any other tips are in the other post I linked to. Now Ceph is all containerised it all seams a bit too easy! Hope they're not my famous last words!! 😖 It does like a lot of RAM, so I've reduced the OSD limits down a bit and its fine for me.

Cheers.

@stormi said in Looking for a temporary test host with a nVIDIA GPU:

For the tests we had a need for 1 week ago, it's now fine, however I'll probably update this thread once we have an ISO image that can be tested by users that have such hardware. Note: it's not about using the GPU itself, but simply about making sure that the hypervisor works well with the changes we made to replace the not-built-by-us gpumon tool whose absence would make XCP-ng 8.1 unbootable (as we sadly found out after the release) with a dummy one built by us.

Now is time for the tests I was talking about earlier. XCP-ng 8.2 beta is now available with our dummy gpumon and we need users who have nVIDIA GPUs to test it and give us feedback. There may be situations we have not tested where our dummy gpumon is not enough to make the XAPI happy, despite the fact that we don't support nVIDIA vGPUs (proprietary software from Citrix required for that feature).

@stormi Exactly. Must've been related to something other than just the latest packages.

I'm not sure Unitrends is supporting XCP-ng. Please refer to your backup vendor.

Current backup solutions claming to support XCP-ng: https://xcp-ng.org/docs/backup.html

@FMaster007 Not if you do it correctly. See here -- https://github.com/xcp-ng/xcp/wiki/Upgrade-Howto

anyone can request a change in https://github.com/xcp-ng/xenadmin/issues 🙂

When you boot in UEFI mode, press "e" to edit the boot command line, you have a line to change the memory for dom0.

Testhost at home updated

XCP-ng 8.0 beta CPU: i5-4430 (Haswell) https://ark.intel.com/content/www/de/de/ark/products/75036/intel-core-i5-4430-processor-6m-cache-up-to-3-20-ghz.html (XEN) [ 0.000000] Hardware features: IBRS/IBPB STIBP L1D_FLUSH SSBD MD_CLEAR

Host started just fine, Win10 VM startetd also.