Thanks. You are right. I tested another command and don't see logs in the event viewer.
PR was sent. On Fri, Dec 16, 2022 at 5:27 PM Andrey Drobyshev < andrey.drobys...@virtuozzo.com> wrote: > On 12/16/22 12:01, Konstantin Kostiuk wrote: > > Reviewed-by: Konstantin Kostiuk <kkost...@redhat.com > > <mailto:kkost...@redhat.com>> > > Tested-by: Konstantin Kostiuk <kkost...@redhat.com > > <mailto:kkost...@redhat.com>> > > > > > > Hi Andrey, > > Do you expect Event Viewer to be empty by default in the current > > implementation? > > Currently, all logs that we write in the guest agent do not have > > "syslog" domain > > so we will have logs only in file. > > > > [...] > > Do they not really? For instance, I see quite a few such calls in the > implementation of guest commands: > > # grep 'slog(' qga/commands-win32.c | wc -l > 21 > > They just need to be triggered. For instance, if I build QGA with these > patches applied, run it in a VM make a fsfreeze call: > > # virsh domfsfreeze win2k16-qga-win > Froze 2 filesystem(s) > > then I see the message "guest-fsfreeze called" in the event log. > >
