help
On 2/22/22 00:25, Michal Prívozník wrote:
On 2/21/22 17:12, Charles Polisher wrote:
Hey, please the list on CC for benefit of others, e.g. when somebody
runs into the same problem they can find the discussion in the archive.
Oops... unintentional.
On 2/21/22 01:54, Michal Prívozník wrote:
On 2/22/22 16:36, Дмитрий wrote:
> # lsof -p $(cat /run/libvirtd.pid) > run1
> # virt-df -d kvm3586
> # lsof -p $(cat /run/libvirtd.pid) > run2
> # diff run1 run2
> 196a197
>> libvirtd 3618992 root 54u unix 0x902dc0c58440 0t0 99330533
>> type=STREAM
>
I wonder whether this is
# lsof -p $(cat /run/libvirtd.pid) > run1
# virt-df -d kvm3586
# lsof -p $(cat /run/libvirtd.pid) > run2
# diff run1 run2
196a197
> libvirtd 3618992 root 54u unix 0x902dc0c58440 0t0 99330533
> type=STREAM
On Tue, Feb 22, 2022 at 06:23:13PM +0300, Дмитрий wrote:
>
> Updated libvirt with:
>
> # dnf install @virt
>
> Not its 2.module_el8.6.0+1087+b42c8331
>
> Testing:
>
> # virt-df -d kvm3551
>
> But still, issue remains. Here how it looks like in /proc (all these
> socket/pipe symlinks are
Updated libvirt with:
# dnf install @virt
Not its 2.module_el8.6.0+1087+b42c8331
Testing:
# virt-df -d kvm3551
But still, issue remains. Here how it looks like in /proc (all these
socket/pipe symlinks are broken):
# ls -lah /proc/$(pgrep -f libvirtd)/fd/*
lrwx-- 1 root root 64 фев 22
On Tue, Feb 22, 2022 at 06:00:50PM +0300, Дмитрий wrote:
> Hello,
>
> ## SETUP
>
> CentOS 8 Stream
> libguestfs-tools.noarch 1:1.40.2-24.el8.plesk
> libvirt.x86_64 7.6.0-6.el8s
The current libvirt shipping in CentOS 8 Stream is
8.0.0-2.module_el8.6.0+1087+b42c8331
which is 6 months newer
Hello,
## SETUP
CentOS 8 Stream
libguestfs-tools.noarch 1:1.40.2-24.el8.plesk
libvirt.x86_64 7.6.0-6.el8s
## ISSUE REPRODUCTION
lsof -p $(cat /run/libvirtd.pid) | wc -l # here we have N open file descriptors
by libvirtd
guestfish --ro -d domain1
run # here we have N+1 open file
On 2/22/22 09:48, lejeczek wrote:
> Hi guys
>
> I see this often(perhaps once a day) on VMs:
>
> ... watchdog: BUG: soft -lockup - CPU#1 stuck for xxXXxxs! [swapper/1:0]
I used to see these when I suspended the host with guests running. But
in your case, because of the "swapper" suffix I
On 2/21/22 17:12, Charles Polisher wrote:
Hey, please the list on CC for benefit of others, e.g. when somebody
runs into the same problem they can find the discussion in the archive.
> On 2/21/22 01:54, Michal Prívozník wrote:
>
>> On 2/20/22 04:07, Charles Polisher wrote:
>>> Hello,
>>>
>>>
10 matches
Mail list logo