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
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'
On 22/01/28 10:47PM, Charles Polisher wrote:
> ...
> Seeing as there are no other replies yet, for what it's worth,
> on my hypervisor I see similar results for a working system,
> and to my knowledge it's all running correctly:
>
> # virsh net-info default
> Name: default
> U
On 1/24/22 17:29, Hakan E. Duran wrote
Then due to its inactive status, I thought it would be a good idea to
start it with:
$sudo virsh net-start default
Network default started
Of note, even though the default network was marked as inactive as
above, it was working. In other words, I was able
Thank you for the reply. I truly appreciate them.
I used virt-manager to set up my VMs and manage them on a daily basis.
After reading your responses I used the commands below to gather some
information:
$sudo virsh net-list --all
Name State Autostart Persistent
-
On 1/24/22 4:35 AM, Martin Kletzander wrote:
On Fri, Jan 21, 2022 at 08:42:58AM -0600, Hakan E. Duran wrote:
Hi,
I would like some help to troubleshoot the problem I have been having
lately with my VM host, which contains 5 VMs, one of which is for
pi-hole, unbound services. It has been a re
On Fri, Jan 21, 2022 at 08:42:58AM -0600, Hakan E. Duran wrote:
Hi,
I would like some help to troubleshoot the problem I have been having
lately with my VM host, which contains 5 VMs, one of which is for
pi-hole, unbound services. It has been a relatively common occurrence in
the last few weeks
