On March 7, 2020 1:09:37 AM GMT+02:00, Jayme wrote:
>Strahil,
>
>Thanks for your suggestions. The config is pretty standard HCI setup
>with
>cockpit and hosts are oVirt node. XFS was handled by the deployment
>automatically. The gluster volumes were optimized for virt store.
>
>I tried noop on the
Strahil,
Thanks for your suggestions. The config is pretty standard HCI setup with
cockpit and hosts are oVirt node. XFS was handled by the deployment
automatically. The gluster volumes were optimized for virt store.
I tried noop on the SSDs, that made zero difference in the tests I was
running a
Looks like yum docker-engine querying came back to a normal state
Even docker project url curling is working without the warning message seen
in my first post
Looks like the deployment process hit a bad state in the public repo and
hence caused these errors
Thanks for your attention.
Eugène NG
On March 6, 2020 6:02:03 PM GMT+02:00, Jayme wrote:
>I have 3 server HCI with Gluster replica 3 storage (10GBe and SSD
>disks).
>Small file performance inner-vm is pretty terrible compared to a
>similar
>spec'ed VM using NFS mount (10GBe network, SSD disk)
>
>VM with gluster storage:
>
># dd if=/d
Am 06.03.20 um 10:08 schrieb Sandro Bonazzola:
oVirt 4.4.0 Alpha release refresh is now available for testing
The oVirt Project is excited to announce the availability of the alpha
release refresh of oVirt 4.4.0 for testing, as of March 6th, 2020
There's one mention of "Cinder" on ht
I have 3 server HCI with Gluster replica 3 storage (10GBe and SSD disks).
Small file performance inner-vm is pretty terrible compared to a similar
spec'ed VM using NFS mount (10GBe network, SSD disk)
VM with gluster storage:
# dd if=/dev/zero of=test2.img bs=512 count=1000 oflag=dsync
1000+0 reco
Hi all,
calmer now, sorry for the initial mail, but I was under some pressure.
Strahil Nikolov dixit:
> What are you actually trying to do ? Are you trying to sparsify your
> VM's disks ?
No, not at all. The thing I really needed to do is to prepare a VM
on an oVirt system then export
Hi
Am Fr., 6. März 2020 um 10:50 Uhr schrieb Sandro Bonazzola <
sbona...@redhat.com>:
>
> Il giorno ven 6 mar 2020 alle ore 10:40 Nathanaël Blanchet <
> blanc...@abes.fr> ha scritto:
>
>> [...]
>>
>> In particular, please note that upgrades from 4.3 and future upgrades
>> from this alpha to the fi
Il giorno ven 6 mar 2020 alle ore 10:40 Nathanaël Blanchet
ha scritto:
>
> Le 06/03/2020 à 10:08, Sandro Bonazzola a écrit :
>
> oVirt 4.4.0 Alpha release refresh is now available for testing
>
> The oVirt Project is excited to announce the availability of the alpha
> release refresh of oVirt 4.4
Le 06/03/2020 à 10:08, Sandro Bonazzola a écrit :
oVirt 4.4.0 Alpha release refresh is now available for testing
The oVirt Project is excited to announce the availability of the alpha
release refresh of oVirt 4.4.0 for testing, as of March 6th, 2020
This release unleashes an altogether
Il giorno ven 6 mar 2020 alle ore 10:20 Neal Gompa ha
scritto:
> On Fri, Mar 6, 2020 at 4:12 AM Sandro Bonazzola
> wrote:
>
>> oVirt 4.4.0 Alpha release refresh is now available for testing
>>
>> The oVirt Project is excited to announce the availability of the alpha
>> release refresh of oVirt 4
On Fri, Mar 6, 2020 at 4:12 AM Sandro Bonazzola wrote:
> oVirt 4.4.0 Alpha release refresh is now available for testing
>
> The oVirt Project is excited to announce the availability of the alpha
> release refresh of oVirt 4.4.0 for testing, as of March 6th, 2020
>
> This release unleashes an alto
oVirt 4.4.0 Alpha release refresh is now available for testing
The oVirt Project is excited to announce the availability of the alpha
release refresh of oVirt 4.4.0 for testing, as of March 6th, 2020
This release unleashes an altogether more powerful and flexible open source
virtualization soluti
13 matches
Mail list logo