On 12/16/22 20:19, Laszlo Ersek wrote:
> On 12/16/22 18:09, Andrey Drobyshev wrote:
>> On 12/16/22 10:24, Laszlo Ersek wrote:
>>> On 12/15/22 18:34, Richard W.M. Jones wrote:
On Thu, Dec 15, 2022 at 06:45:46PM +0200, Andrey Drobyshev wrote:
> According to [1], there're different ways to
On 12/16/22 18:09, Andrey Drobyshev wrote:
> On 12/16/22 10:24, Laszlo Ersek wrote:
>> On 12/15/22 18:34, Richard W.M. Jones wrote:
>>> On Thu, Dec 15, 2022 at 06:45:46PM +0200, Andrey Drobyshev wrote:
According to [1], there're different ways to specify which firmware is
to be used by a
On 12/16/22 10:24, Laszlo Ersek wrote:
> On 12/15/22 18:34, Richard W.M. Jones wrote:
>> On Thu, Dec 15, 2022 at 06:45:46PM +0200, Andrey Drobyshev wrote:
>>> According to [1], there're different ways to specify which firmware is
>>> to be used by a libvirt-driven VM. Namely, there's an automatic
On 12/15/22 18:34, Richard W.M. Jones wrote:
> On Thu, Dec 15, 2022 at 06:45:46PM +0200, Andrey Drobyshev wrote:
>> According to [1], there're different ways to specify which firmware is
>> to be used by a libvirt-driven VM. Namely, there's an automatic
>> firmware selection, e.g.:
>>
>> ...
On 12/15/22 19:34, Richard W.M. Jones wrote:
> On Thu, Dec 15, 2022 at 06:45:46PM +0200, Andrey Drobyshev wrote:
>> According to [1], there're different ways to specify which firmware is
>> to be used by a libvirt-driven VM. Namely, there's an automatic
>> firmware selection, e.g.:
>>
>> ...
On Thu, Dec 15, 2022 at 06:45:46PM +0200, Andrey Drobyshev wrote:
> According to [1], there're different ways to specify which firmware is
> to be used by a libvirt-driven VM. Namely, there's an automatic
> firmware selection, e.g.:
>
> ...
>
> ...
>
> and a manual one, e.g.:
>
>
According to [1], there're different ways to specify which firmware is
to be used by a libvirt-driven VM. Namely, there's an automatic
firmware selection, e.g.:
...
...
and a manual one, e.g.:
...
/usr/share/OVMF/OVMF_CODE.fd
...
...
with the
