On Fri, Mar 27, 2020 at 1:12 PM Daniel P. Berrangé wrote:
>
> On Fri, Mar 27, 2020 at 12:31:07PM +0100, Miguel Duarte de Mora Barroso wrote:
> > Hi,
> >
> > I've seen that in the past, libvirt couldn't start VMs when the disk
> > image was stored on a file system that doesn't support direct I/O
>
On Fri, Mar 27, 2020 at 12:31:07PM +0100, Miguel Duarte de Mora Barroso wrote:
> Hi,
>
> I've seen that in the past, libvirt couldn't start VMs when the disk
> image was stored on a file system that doesn't support direct I/O
> having the 'cache=none' configuration [0].
>
> On the KubeVirt
Hi,
I've seen that in the past, libvirt couldn't start VMs when the disk
image was stored on a file system that doesn't support direct I/O
having the 'cache=none' configuration [0].
On the KubeVirt project, we have some storage tests on a particular
provider which does just that - try to create
