Hi,
It's possible that you bumped into:
Original bug: https://bugzilla.redhat.com/show_bug.cgi?id=1462236
Downstream clone: https://bugzilla.redhat.com/show_bug.cgi?id=1635337.
It has been solved in 4.3.5.
Regards,
Nicolás
El 2/7/21 a las 13:55, Dominique D escribió:
I created a VM pool
A kind reminder that oVirt conference call for papers closes in 20 days!
Looking forward to user stories, developers onboarding journeys,
integration stories, new features presentation, old features nobody knows
about because nobody presented them before and more you see fit.
You can find call for
On Mon, Jul 5, 2021 at 10:42 AM Nicolás wrote:
> Hi,
>
> It's possible that you bumped into:
>
> Original bug: https://bugzilla.redhat.com/show_bug.cgi?id=1462236
> Downstream clone: https://bugzilla.redhat.com/show_bug.cgi?id=1635337.
>
> It has been solved in 4.3.5.
>
> Regards,
>
> Nicolás
>
On Sun, Jul 4, 2021 at 1:01 PM Nir Soffer wrote:
> On Sun, Jul 4, 2021 at 11:30 AM Strahil Nikolov
> wrote:
> >
> > Isn't it better to strace it before killing qemu-img .
>
> It may be too late, but it may help to understand why this qemu-img
> run got stuck.
>
>
Hi, thanks for your answers and
That NFS looks like it is not properly configured -> nobody:nobody is not
suposed to be seen.
Change the ownership from nfs side to 36:36. Also, you can define
(all_squash,anonuid=36,anongid=36) as export options.
Best Regards,Strahil Nikolov
On Mon, Jul 5, 2021 at 12:52, Gianluca Cecchi
Just found this article[1] today and I think someone here may be
interested: "Enabling High Availability Service with oVirt Virtualization
and CephFS" by Physics Department Brookhaven National Laboratory, supported
by the Office of Nuclear Physics within the U.S. Department of Energy’s
Office of
On Mon, Jul 5, 2021 at 12:50 PM Gianluca Cecchi
wrote:
>
> On Sun, Jul 4, 2021 at 1:01 PM Nir Soffer wrote:
>>
>> On Sun, Jul 4, 2021 at 11:30 AM Strahil Nikolov
>> wrote:
>> >
>> > Isn't it better to strace it before killing qemu-img .
>>
>> It may be too late, but it may help to understand
On Mon, Jul 5, 2021 at 4:06 PM Strahil Nikolov wrote:
>
> >Disks on the export domain are never used by a running VM so there is
> no reason to
> preallocate them. The system should always use sparse disks when
> copying to export
> domain.
>
> >When importing disks from export domain, the system
On Mon, Jul 5, 2021 at 3:36 PM Gianluca Cecchi
wrote:
>
> On Mon, Jul 5, 2021 at 2:13 PM Nir Soffer wrote:
>>
>>
>> >
>> > vdsm 14342 3270 0 11:17 ?00:00:03 /usr/bin/qemu-img convert
>> > -p -t none -T none -f raw
>> >
On Mon, Jul 5, 2021 at 11:56 AM Strahil Nikolov
wrote:
> That NFS looks like it is not properly configured -> nobody:nobody is not
> suposed to be seen.
>
> Change the ownership from nfs side to 36:36. Also, you can define
> (all_squash,anonuid=36,anongid=36) as export options.
>
>
> Best
On Mon, Jul 5, 2021 at 2:13 PM Nir Soffer wrote:
>
> >
> > vdsm 14342 3270 0 11:17 ?00:00:03 /usr/bin/qemu-img
> convert -p -t none -T none -f raw
>
>Disks on the export domain are never used by a running VM so there is
no reason to
preallocate them. The system should always use sparse disks when
copying to export
domain.
>When importing disks from export domain, the system should reconstruct
the original disk
configuration (e.g.
12 matches
Mail list logo