On Thu, Feb 3, 2022 at 2:30 PM Richard W.M. Jones <rjones(a)redhat.com> wrote:
I'm following the instructions here:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/...
I've also added an extra virtual disk to my host node which appears as
/dev/sdb. Although the disk is partitioned, /dev/sdb1 is not created.
Is udev broken in oVirt node?
I cannot see anywhere in the dialog where you specify the name of the
device (eg. "/dev/sdb1"). So how's it supposed to work?
It doesn't work, giving an information-free error message:
Error while executing action Add Storage Connection: Problem while trying to mount
target
You can find more info on the failure in:
/var/log/vdsm/supervdsmd.log
Posix compliant is basically NFS without some mount options:
https://github.com/oVirt/vdsm/blob/878407297cb7dc892110ae5d6b0403ca972492...
Using a local device on a host is less tested path, I'm not QE is testing
this (Avihai, please correct me if you do).
If you have multiple hosts, this will break if the local device does not have
the same name on all hosts (so using /dev/sdb1 is very fragile). If you have
one host it can be fine.
Any reason to add a device to the vm, instead of using an NFS server?
I guess that your purpose is testing virt-v2v with oVirt, so you want to test
a common configuration; NFS is very common for oVirt users.
Nir