frequent network collapse possibly due to bridging

[Charles Polisher]

On 1/29/22 10:06, Hakan E. Duran wrote:
> Thank you so much for sharing your script as well! This is so helpful. 
Thank the author, Yury V. Zaytsev <yury at shurup.com>
> I truly appreciate it knowing that it may not be possible to identify what actually is wrong/failing.

Please post the version of your Hypervisor's OS ("cat /etc/os-release").
If that file doesn't exist, any of: /etc/system-release, 
/etc/redhat-release,
/etc/SuSE-release, /etc/debian_version, /etc/arch-release,
/etc/gentoo-release, /etc/slackware-version, /etc/frugalware-release,
/etc/altlinux-release, /etc/mandriva-release, or /etc/meego-release.

Also please post the version of spice-server: considering
https://bugzilla.redhat.com/show_bug.cgi?id=912218 ,
which is described as
    boot up guest in rhel7 host then, do screen via qmp monitor
    in loop, qemu report error message:*"qxl_send_events: spice-server**
**   bug: guest stopped, ignoring*".
    Version-Release number of selected component :
*spice-server-0.12.2-1.el7.x86_64*
    qemu-kvm-1.3.0-5.el7.x86_64
and which is claimed to be fixed. If this is a regression,
and you're running a Red Hat system, you might report it there.

Finally, there is a method for increasing the verbosity of error
logging, but it's a bit tedious to set up and to interpret the
results. See: https://libvirt.org/logging.html#log_config
For example, setting *LIBVIRT_DEBUG=2* in the startup code for
libvirt. Where exactly to set this will depend on your OS.

Best luck,
-- 
Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20220129/dd35efd1/attachment.htm>