Hi Strahil,
Apologies for the delay.
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 100G 0 disk
`-sda1 8:10 100G 0 part
|-vg00-root 253:40 99G 0 lvm /
`-vg00-swap_1 253:5
Hello everyone,
I must mention that there is the same behavior on CentOS 8 Stream. I think it's
a python problem.
Has anyone managed this problem?
Thanks,
Dan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to
Dear Gianluca,
Thanks a lot for this valuable and very helpful simulation.
best regards,
samuel
Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed (成就他人)
From: Gianluca Cecchi
Date: 2022-10-12 10:02
To: Martin Perina
CC: users
Subject: [ovirt-users] Re: How to
On Tue, Oct 11, 2022 at 1:42 PM Klaas Demter wrote:
> Don't storage leases solve that problem?
>
Not entirely, you are not able to kill a VM via storage lease, you can only
detect that even though we lost connection from engine to host (and this
means also VMs), then we can check if host/VM
On Wed, Oct 12, 2022 at 9:14 AM Martin Perina wrote:
>
>
> On Tue, Oct 11, 2022 at 1:42 PM Klaas Demter
> wrote:
>
>> Don't storage leases solve that problem?
>>
>
> Not entirely, you are not able to kill a VM via storage lease, you can
> only detect that even though we lost connection from
5 matches
Mail list logo
