On Thu, Feb 03, 2022 at 06:31:52PM +0200, Nir Soffer wrote:
> This is expected on oVirt, our multipath configuration is intentionally
> grabbing
> any device that multipath can work with, even if the device only has one path.
> The motivation is to be able to configure a system when only one path is
> available (maybe you have an hba/network/server issue), and once the other
> paths are available the system will use them transparently.
>
> To avoid this issue with local devices, you need to blacklist the device.
>
> Add this file:
>
> $ cat /etc/multipath/conf.d/local.conf
> blacklist {
> wwid "QEMU HARDDISK"
> }
Thanks - for the mailing list record the syntax that worked for me is:
# cat /etc/multipath/conf.d/local.conf
blacklist {
wwid ".*QEMU_HARDDISK.*"
}
> Configuring NFS on some other machine is easy.
>
> I'm using another VM for this, so I can easily test negative flows like
> stopping
> or restarting the NFS server while it is being used by vms or storage
> operations.
> I'm using 2G alpine vm for this, it works fine even with 1G memory.
I think I can get local storage working now (I had it working before).
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/AU5UUXFNGPMBGETPZI3R445FFWESUGXK/
