Re: [libvirt PATCH 00/10] Cleanup and test more firmware handling scenarios

2022-04-21 Thread Daniel P . Berrangé
On Mon, Apr 04, 2022 at 02:45:41PM -0400, Cole Robinson wrote: > On 2/16/22 8:17 AM, Michal Prívozník wrote: > > On 2/15/22 19:54, Daniel P. Berrangé wrote: > >> There are a mind bending number of possible ways to configure the > >> firmware with/without NVRAM. Only a small portion are tested and >

Re: [libvirt PATCH 00/10] Cleanup and test more firmware handling scenarios

2022-04-04 Thread Cole Robinson
On 2/16/22 8:17 AM, Michal Prívozník wrote: > On 2/15/22 19:54, Daniel P. Berrangé wrote: >> There are a mind bending number of possible ways to configure the >> firmware with/without NVRAM. Only a small portion are tested and >> many error scenarios are silently ignored. >> >> This series attempts

Re: [libvirt PATCH 00/10] Cleanup and test more firmware handling scenarios

2022-02-16 Thread Michal Prívozník
On 2/15/22 19:54, Daniel P. Berrangé wrote: > There are a mind bending number of possible ways to configure the > firmware with/without NVRAM. Only a small portion are tested and > many error scenarios are silently ignored. > > This series attempts to get coverage of every possible XML config > sc

[libvirt PATCH 00/10] Cleanup and test more firmware handling scenarios

2022-02-15 Thread Daniel P . Berrangé
There are a mind bending number of possible ways to configure the firmware with/without NVRAM. Only a small portion are tested and many error scenarios are silently ignored. This series attempts to get coverage of every possible XML config scenario and report explicit errors in all invalid configs