That makes sense. Now that I understand what's going on, I can work around it.
Thanks for the explanation.
-peter
On Friday, December 14, 2018, 3:28:32 PM EST, Michal Prívozník
wrote:
On 12/14/18 4:31 PM, Peter Kukla wrote:
> Autostart is set to "enable" for this domain, but I
On 12/14/18 4:31 PM, Peter Kukla wrote:
> Autostart is set to "enable" for this domain, but I wouldn't expect
> autostart to be invoked when a simple "read-only" command is run. I'd expect
> the "list --all" command to only display details about the domain...not
> change the status of the
Autostart is set to "enable" for this domain, but I wouldn't expect autostart
to be invoked when a simple "read-only" command is run. I'd expect the "list
--all" command to only display details about the domain...not change the status
of the domain by booting it. Maybe I'm misunderstanding
On 12/11/18 3:39 PM, Peter Kukla wrote:
> Hello,
>
Could it be that the domain is set as "autostart"? The session daemon is
slightly different to system daemon. The former come and go if there is
no activity for (by default) 30 seconds. And if the domain would be
marked as 'autostart' (meaning
The /etc/libvirt/libvirtd.conf file was modified to include the following:
log_level = 1 log_filters="3:remote 4:event 3:json 3:rpc"
log_outputs="1:file:/var/log/libvirt/libvirtd.log"
The service was then restarted, and I ran "tail -f" against the log to
determine exactly which entries
On Tue, Dec 11, 2018 at 14:39:40 +, Peter Kukla wrote:
> Hello,
> I have a CentOS 7 client running on a CentOS 7 server. "virsh --version"
> reports that 3.9.0 is being used.
> I'm issuing a "virsh shutdown" command to shutdown the client. I then
> confirm that the client has actually
Hello,
I have a CentOS 7 client running on a CentOS 7 server. "virsh --version"
reports that 3.9.0 is being used.
I'm issuing a "virsh shutdown" command to shutdown the client. I then confirm
that the client has actually shutdown using "virsh list --all".
Lately I've been seeing instances
