January 2024 - Devel - oVirt List Archives

Re: Yuriy about NVMe over fabrics for oVirt
by Nir Soffer 12 Aug '24

12 Aug '24

On Thu, Nov 2, 2023 at 4:40 PM Yuriy <ykhokhlov(a)gmail.com> wrote: > Hi Nir! > > This is Yuriy. > We agreed to continue the subject via email. > So the options are: 1. Using Managed Block Storage (cinderlib) with a driver that supports NVMe/TCP. Lastest oVirt has the needed changes to configure this. Benny and I tested with Lightbits[1] driver in a virtualized environment. This is basically a POC that may work for you or not, or require more work that you will have to do yourself since not much development is happening now in oVirt. 2. Using the devices via multipath Legacy storage domains are based on multipath. It may be possible to use multipath on top of NVMe devices, and in this case they look like a normal LUN so you can create a storage domain from such devices. oVirt will not handle connections for you, and all the devices must be connected to all nodes at the same time, just like FC/iSCSI LUNs. You will likely not get the performance benefit of NVMe/TCP. 3. Using host devices If what you need is using some devices (which happen to be connected via be NVMe/TCP), maybe you can attach them to a VM directly (using host devices). This gives the best possible performance but no features (snapshots, backup, live migration, live storage migration, etc.) [1] https://www.lightbitslabs.com/ Nir

2 3

ovirt-system-tests
by stephan.duehr＠bareos.com 15 Mar '24

15 Mar '24

Hi, about two years ago, I used OST to setup a oVirt test/dev environment. Now I tried again, following https://github.com/oVirt/ovirt-system-tests/blob/master/README.md but it fails because https://templates.ovirt.org/yum/ is unavailable. Or isn't it meant to be available for public access any more? Regards, Stephan

3 2

Foreman needs a release of ovirt-engine-sdk-ruby
by ewoud+ovirt＠kohlvanwijngaarden.nl 02 Feb '24

02 Feb '24

Hello everyone, Foreman is a bit late in updating Ruby to a newer version. Looking ahead we're aiming at Ruby 3.1+ but ovirt-engine-sdk-ruby doesn't compile on it. https://github.com/oVirt/ovirt-engine-sdk-ruby/pull/3 was merged in September 2022 and a request to release it was opened a year ago: https://github.com/oVirt/ovirt-engine-sdk-ruby/issues/4 The Foreman community is currently discussing dropping oVirt support: https://community.theforeman.org/t/proposal-to-drop-support-for-ovirt/36324 Is there anyone who can still perform this release, or should we proceed with removal? Regards, Ewoud Kohl van Wijngaarden

2 1

Foreman needs a release of ovirt-engine-sdk-ruby
by Ewoud Kohl van Wijngaarden 29 Jan '24

29 Jan '24

Hello everyone, Foreman is a bit late in updating Ruby to a newer version. Looking ahead we're aiming at Ruby 3.1+ but ovirt-engine-sdk-ruby doesn't compile on it. https://github.com/oVirt/ovirt-engine-sdk-ruby/pull/3 was merged in September 2022 and a request to release it was opened a year ago: https://github.com/oVirt/ovirt-engine-sdk-ruby/issues/4 The Foreman community is currently discussing dropping oVirt support: https://community.theforeman.org/t/proposal-to-drop-support-for-ovirt/36324 Is there anyone who can still perform this release, or should we proceed with removal? Regards, Ewoud Kohl van Wijngaarden

2 1

How is oVirt Node ISO (CentOS Stream 8 or 9) kernel or boot parameters different to other distros - EFI boot freeze.
by john＠alwayson.net.au 24 Jan '24

24 Jan '24

Related to my question posted in the Users forum, I'm trying to understand why the oVirt Node ISO based on CentOS Stream 8 or 9 freezes immediately on my hardware. These distros work: oVirt Node ISO based on CentOS Stream 7 works. Fedora 39 works RHEL 9 works. Hardware is Apple Mac Pro 2013: Intel Xeon CPU E5-1650v2 6-core 64G (4x8) 1866MHz DDR3 ECC memory Dual AMD FirePro D700 graphics processors with 6GB of GDDR5 VRAM PCIe-based SSD NVME (Linux recognises /dev/nvme0n1) thanks John

1 0

[VDSM] Started getting virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired
by Edward Haas 11 Jan '24

11 Jan '24

Hi, I have a VM which acts as an oVirt host with VDSM installed. I use it for testing without connecting it to Engine. Recently VDSM fails to come up and I see this error: Sep 26 17:58:18 localhost libvirtd: 2018-09-26 14:58:18.978+0000: 12176: error : virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired Any hint on how to generate or fetch a new certificate without the help of Engine? Thanks, Edy.

3 5