Eduardo Habkost writes:
> On Wed, Jan 18, 2017 at 05:04:45PM +0100, Markus Armbruster wrote:
>> Eduardo Habkost writes:
>>
>> > In case there were options set in the default config file, print
>> > a warning so users can update their scripts.
>>
>>
Eduardo Habkost writes:
> In case there were options set in the default config file, print
> a warning so users can update their scripts.
Can you explain why you don't warn on an empty qemu.conf?
> If somebody wants to keep the config file as-is, avoid the
> warning and
On Wed, Jan 18, 2017 at 05:04:45PM +0100, Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > In case there were options set in the default config file, print
> > a warning so users can update their scripts.
>
> Can you explain why you don't warn on an empty qemu.conf?
In case there were options set in the default config file, print
a warning so users can update their scripts.
If somebody wants to keep the config file as-is, avoid the
warning and use a command-line that will work in future QEMU
versions, they can use:
$QEMU -nodefconfig -readconfig