On 14/11/25 at 16:01, [email protected] wrote:
You gave me an idea, so I went:
strace -f -o /tmp/trace qemu ...
(yes, I had a qemu hanging around in my history. It is qemu-kvm, so it
might be a close cousin). Looking at the opens, I see one potential
config:
openat(AT_FDCWD, "/etc/qemu/qemu.conf", O_RDONLY) = -1 ENOENT (No such file
or directory)
It's a system config, but might be a start 🙂
No manpage for qemu.conf, alas.
@Franco: perhaps you could try a similar trick?
This was what I wanted to do, but without documentation about what the
qemu.conf file should contain it is not possible to accomplish that.
Does anybody know the purpose of "/etc/qemu/qemu.conf"? And looking
again (thanks The Wanderer) at the kvm(1) man-page the options:
-readconfig file
Read device configuration from file. This approach is useful when
you want to spawn QEMU process with many command line options but
you don't want to exceed the command line character limit.
-no-user-config
The -no-user-config option makes QEMU not load any of the
user-provided config files on sysconfdir.
What does they mean? Is it possible to have a config file or I must use
a front-end like aqemu?
Thanks, kind regards.
--
Franco Martelli
