Digimer writes:
> I did find a way to do it working around virsh, but of course I'd
> prefer to directly query the source instead of infering it if possible.
Speaking about other possible workarounds, what about watching the
/var/log/libvirt/qemu/*.log files (assuming you use the QEMU driver)?
T
On 2020-10-01 1:21 a.m., Michal Prívozník wrote:
> On 10/1/20 3:42 AM, Digimer wrote:
>> Hi all,
>>
>> Is there a way to tell when a tool made a change to guest (ie: used
>> virt-manager to make a change)? Following, is there a way to check to
>> see if there are changes queued to take effect wh
On 2020-10-01 2:29 a.m., wf...@niif.hu wrote:
> daggs writes:
>
>> I'd assume that saying vm running you mean that the os is up and
>> running too. I have similar need, I was able to get something as such
>> to work using virsh console when the guest was a linux with serial
>> console support en
daggs writes:
> I'd assume that saying vm running you mean that the os is up and
> running too. I have similar need, I was able to get something as such
> to work using virsh console when the guest was a linux with serial
> console support enabled. I wasn't able to get this to work in a
> scrip
On 10/1/20 3:42 AM, Digimer wrote:
Hi all,
Is there a way to tell when a tool made a change to guest (ie: used
virt-manager to make a change)? Following, is there a way to check to
see if there are changes queued to take effect when the guest next reboots?
You can listen for events. For
uot;Digimer"
To: libvirt-users@redhat.com
Subject: Determining when a guest booted / how long it's been running
Hi all,
Is there a way to tell when a tool made a change to guest (ie: used virt-manager to make a change)? Following, is there a way to check to see if there are changes q
Hi all,
Is there a way to tell when a tool made a change to guest (ie:
used virt-manager to make a change)? Following, is there a way to
check to see if there are changes queued to take effect when the
guest next reboots?
If either of the above are not
