Most probably when virtualization is enabled vdsm services can start and they create a lvm filter for your Gluster bricks.

Boot the system (most probably with virtualization disabled), move your entry from /etc/fstab to a dedicated '.mount' unit and boot with the virt enabled.

Once booted with the flag enabled -> check the situation (for example blacklist local disks in /etc/multipath/conf.d/blacklist.conf, check and adjust the LVM filter, etc).

Best Regards,
Strahil Nikolov

On Wed, Feb 2, 2022 at 11:52, eevans@digitaldatatechs.com
<eevans@digitaldatatechs.com> wrote:
My setup is 3 ovirt nodes that run gluster independently of the engine server, even thought the engine still controls it. So 4 nodes, one engine and 3 clustered nodes.
This has been and running with no issues except this:
But now my arbiter node will not load the gluster drive when virtualization is enable in the BIOS. I've been scratching my head on this and need some direction.
I am attaching the error.

https://1drv.ms/u/s!AvgvEzKKSZHbhMRQmUHDvv_Xv7dkhw?e=QGdfYR

Keep in mind, this error does not occur is VT is turned off..it boots normally.

Thanks in advance.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HXRDM6W3IRTSUK46FYZZR4JRR766B2AX/