On Thu, Oct 15, 2020 at 3:27 PM Nir Soffer <nsof...@redhat.com> wrote:

> On Thu, Oct 15, 2020 at 3:20 PM Gilboa Davara <gilb...@gmail.com> wrote:
> >
> > On Thu, Oct 15, 2020 at 2:38 PM Nir Soffer <nsof...@redhat.com> wrote:
> >>
> >> > I've got room to spare.
> >> > Any documentation on how to achieve this (or some pointers where to
> look)?
> >>
> >> It should be documented in ovirt.org, and in RHV documentation:
> >>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/
> >>
> >> > I couldn't find LVM / block device under host devices / storage
> domain / etc and Google search returned irrelevant results.
> >>
> >> I tested locally, LVM devices are not available in:
> >> Compute > Hosts > {hostname} > Host Devices
> >>
> >> Looks like libvirt does not support device mapper devices. You can try:
> >> # virsh -r nodedev-list
> >>
> >> To see supported devices. The list seems to match what oVirt displays
> >> in the Host Devices tab.
> >>
> >> So you only option it to attach the entire local device to the VM,
> either using
> >> pci passthrough or as a scsi disk.
> >>
> >> Nir
> >
> >
> > Full SCSI passthrough per "desktop" VM is an overkill for this user
> case. (Plus, I don't see MD devices in the list, only pure SATA/SAS
> devices).
> > Any idea if there are plans to add support for LVM devices (or any other
> block device)?
>
> I don't think there is such a plan, but it makes sense to support such
> usage.
>
> Please file ovit-engine RFE explaining the use case, and we can consider
> it for a future version.
>
> Nir
>

Done.
https://bugzilla.redhat.com/show_bug.cgi?id=1889138

Thanks again for the help!
- Gilboa
_______________________________________________
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/NQOCWZ2SYPS2LXH2MRJLGICWOVZXXMCB/

Reply via email to