Hello,
In OVirt, we have a property propagate_error at the disk level that
decides in case of an error, how this error be propagated to the VM.
This value is maintained in the database table with the default value
set as Off. The default setting(Off) results in a policy that ends up
pausing
Il giorno lun 27 lug 2020 alle ore 14:25 Pavel Bar ha
scritto:
> Hi,
> I upgraded the OS on my laptop from Fedora 30 to Fedora 32 and now have
> issues with running an engine - some libraries are missing.
> I know that the new Fedora releases are not supported.
> I couldn't downgrade back to
> 1) So there is no workaround, like playing with repositories like I tried to
> do?
I tried a couple of months ago (I upgraded to fc32 right after it was
made available), I tried building otopi manually and discussed this
with Didi, but the rabbit hole for the code changes required was far
too
Thanks Benny :)
1) So there is no workaround, like playing with repositories like I
tried to do?
2) Suppose I take your approach - install CentOs 8 on a Virtual Machine.
What is exactly your development process?
a) How do you debug the Engine/GUI using IDE installed on your laptop?
b) What
On Mon, Jul 27, 2020 at 10:45 AM Daniel Erez wrote:
>
>
>
> On Fri, Jul 24, 2020 at 1:02 PM Radoslaw Szwajkowski
> wrote:
>>
>> Hi all,
>> we plan to bump the GWT version to 2.9.0 (patch [1]).
>> Key changes:
>> 1. support for building with Java 11
>> 2. removing support for classic dev mode (
engine does not work on fedora 32, I move my development env to a centos 8
VM
On Mon, Jul 27, 2020 at 3:24 PM Pavel Bar wrote:
> Hi,
> I upgraded the OS on my laptop from Fedora 30 to Fedora 32 and now have
> issues with running an engine - some libraries are missing.
> I know that the new
Hi,
I upgraded the OS on my laptop from Fedora 30 to Fedora 32 and now have
issues with running an engine - some libraries are missing.
I know that the new Fedora releases are not supported.
I couldn't downgrade back to Fedora 30 and I don't want to totally
reinstall the OS (either to an old
On Fri, Jul 24, 2020 at 1:02 PM Radoslaw Szwajkowski
wrote:
> Hi all,
> we plan to bump the GWT version to 2.9.0 (patch [1]).
> Key changes:
> 1. support for building with Java 11
> 2. removing support for classic dev mode ( use super dev mode instead)
>
Is it mandatory to remove classic dev
> > As you indicate, the vendor driver is responsible for checking version
> > information embedded within the migration stream. Therefore a
> > migration should fail early if the devices are incompatible. Is it
> but as I know, currently in VFIO migration protocol, we have no way to
> get
