On Tue, 2021-07-13 at 21:01 +0300, Nir Soffer wrote:
> On Tue, Jul 13, 2021 at 2:57 PM Branimir Pejakovic <
> branim...@gmail.com> wrote:
> ...
> > > On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic
> > > > >
> > > Unfortunately vdsm (the core package for ovirt host) does not
> > > have
That worked! Thank you very much.
On Wed, Jul 14, 2021 at 12:11 AM Arik Hadas wrote:
>
>
> On Tue, Jul 13, 2021 at 3:56 PM Richard Chan
> wrote:
>
>> Hello list,
>>
>> I had an unsuccessful zombie clone VM task -
>> 1. Target: was able to unlock the disks and delete the target VM
>> 2.
After rebootof node1 -> bricks must always come up. Most probably VDO had to
recover for a longer period blocking the bricks coming up on time.Investigate
this issue before rebooting another host.
Best Regards,Strahil Nikolov
Hi guys,
one strange thing happens, cannot understand it.
Thanks folks.
Submitted:
https://bugzilla.redhat.com/show_bug.cgi?id=1981946
Hope sufficient info is included.
Cheers,
Gervais
> On Jul 13, 2021, at 4:35 AM, Tomáš Golembiovský wrote:
>
> Hi, sorry for late reply. To understand this we will have to see the
> logs. Please open a bug on vdsm
Dear Arik and Milan,
In the meantime, I was asked to check if in current 4.4 version or coming 4.5,
are/will there any capabilities or options of emulating aarch64 on x86_64
platform and if so, what would be the steps to test/enable it.
Can you provide some information?
-
kind regards/met
On Tue, Jul 13, 2021 at 4:19 PM Marcin Sobczyk wrote:
>
>
>
> On 7/12/21 2:11 AM, Nir Soffer wrote:
> > On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic
> > wrote:
> >> It was a fresh install of 2 VMs on top of VirtualBox with Rocky fully
> >> updated on both prior to oVirt installation. I
On Tue, Jul 13, 2021 at 2:57 PM Branimir Pejakovic wrote:
...
> > On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic
> > >
> > Unfortunately vdsm (the core package for ovirt host) does not
> > have ovirt-prefix. Which version do you have?
> > ...
>
> Just in case:
>
> # rpm -qa | grep vdsm
>
On Tue, Jul 13, 2021 at 3:56 PM Richard Chan
wrote:
> Hello list,
>
> I had an unsuccessful zombie clone VM task -
> 1. Target: was able to unlock the disks and delete the target VM
> 2. Source: able to unlock the disks.
>
> Now I cannot do anything with the source as it is flagged as "VM is
On 7/12/21 2:11 AM, Nir Soffer wrote:
On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic wrote:
It was a fresh install of 2 VMs on top of VirtualBox with Rocky fully updated
on both prior to oVirt installation. I installed it yesterday and followed the
usual way of installing it:
On 7/13/2021 8:11 AM, Branimir Pejakovic wrote:
I've been giving this a look and it seems that we aren't building the
advanced virt modules because CentOS builds them from upstream?
I've found no mention of them in their Pagure, and they're built on
their Community Build System via a SIG, with
Hello list,
I had an unsuccessful zombie clone VM task -
1. Target: was able to unlock the disks and delete the target VM
2. Source: able to unlock the disks.
Now I cannot do anything with the source as it is flagged as "VM is being
clone".
Is there a way to remove this flag manually?
> I've been giving this a look and it seems that we aren't building the
> advanced virt modules because CentOS builds them from upstream?
>
> I've found no mention of them in their Pagure, and they're built on
> their Community Build System via a SIG, with the metadata set on them
> as `Extra:
Hi Nir
> On Mon, Jul 12, 2021 at 1:50 AM Branimir Pejakovic wrote:
>
> Unfortunately vdsm (the core package for ovirt host) does not
> have ovirt-prefix. Which version do you have?
> ...
Just in case:
# rpm -qa | grep vdsm
vdsm-jsonrpc-4.40.60.7-1.el8.noarch
On Monday, 12 July 2021 16:59:40 CEST Gangi Reddy wrote:
> Thank you.
>
> Kindly share the Ovirt Node and VM max limits please. In terms of
> CPU/Memory/Storage.
> How many storage disks we can provision through one storage domain?
see e.g.
Hi, sorry for late reply. To understand this we will have to see the
logs. Please open a bug on vdsm with description of the problem and log
attached.
Use the following procedure:
- stop the VM on problematic host
- enable debug logs for vds logger, you can do that either in
15 matches
Mail list logo
