Re: Yuriy about NVMe over fabrics for oVirt
by Nir Soffer
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
4 months, 2 weeks
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
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
11 months