On 3/31/22 14:55, Igor Mammedov wrote:
On Tue, 29 Mar 2022 00:15:38 +0300
Maxim Davydov wrote:
The command "query-init-properties" is needed to get values of properties
after initialization (not only default value). It makes sense, for example,
when working with x86_64-cpu.
All machine types
On 3/30/22 18:17, Vladimir Sementsov-Ogievskiy wrote:
29.03.2022 00:15, Maxim Davydov wrote:
The command "query-init-properties" is needed to get values of
properties
after initialization (not only default value). It makes sense, for
example,
when working with x86_64-cpu.
All machine types (
On Tue, 29 Mar 2022 00:15:38 +0300
Maxim Davydov wrote:
> The command "query-init-properties" is needed to get values of properties
> after initialization (not only default value). It makes sense, for example,
> when working with x86_64-cpu.
> All machine types (and x-remote-object, because its i
29.03.2022 00:15, Maxim Davydov wrote:
The command "query-init-properties" is needed to get values of properties
after initialization (not only default value). It makes sense, for example,
when working with x86_64-cpu.
All machine types (and x-remote-object, because its init uses machime
type's i
The command "query-init-properties" is needed to get values of properties
after initialization (not only default value). It makes sense, for example,
when working with x86_64-cpu.
All machine types (and x-remote-object, because its init uses machime
type's infrastructure) should be skipped, because
