Search results

(gdb) thread apply all backtrace Thread 10 (Thread 0x7f63371fe6c0 (LWP 1233149)): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7f63371f8fe0, op=393, expected=0, futex_word=0x55c3000c15c4) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common...

New crash # coredumpctl gdb -1 PID: 1801697 (kvm) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Mon 2024-03-11 10:18:55 MSK (3min 2s ago) Command Line: /usr/bin/kvm -id 123 -name VM3,debug-threads=on -no-shutdown -chardev...

(gdb) thread apply all backtrace Thread 12 (Thread 0x7fb57bfff6c0 (LWP 847242)): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7fb57bff9fe0, op=393, expected=0, futex_word=0x5628f23a25c0) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common...

New crash # coredumpctl gdb -1 PID: 2403438 (kvm) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Wed 2024-03-06 12:30:37 MSK (12min ago) Command Line: /usr/bin/kvm -id 104 -name VM2,debug-threads=on -no-shutdown -chardev...

When VMs crashed I found that system storage latancy were over 7000 ms. Also every VM had 4Gb memory. I delete storage replica and latency down below 20 ms. Also I increased memory to 6Gb. There are no crashes after this steps. I'm continue monitoring the situation.

Do you have any news for us?

server side (proxmox) # dpkg --list libc6 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description...

Client side dpkg -l | grep virt-viewer ii virt-viewer 11.0-2 amd64 Displaying the graphical console of a virtual machine ii libc6:amd64 2.36-9+deb12u3 amd64 GNU C Library: Shared libraries cat /etc/debian_version 12.2

apt install libspice-server1-dbgsym The coredumpctl gdb -1 output is equal to the above. (gdb) thread apply all backtrace Thread 10 (Thread 0x7fb73bfff6c0 (LWP 1561872)): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7fb73bff9fe0, op=393, expected=0...

(gdb) thread apply all backtrace Thread 10 (Thread 0x7fb73bfff6c0 (LWP 1561872)): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7fb73bff9fe0, op=393, expected=0, futex_word=0x55c10bb64880) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common...

# coredumpctl gdb -1 PID: 7899 (kvm) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Tue 2024-02-20 16:31:07 MSK (16h ago) Command Line: /usr/bin/kvm -id 110 -name VM,debug-threads=on -no-shutdown -chardev...

# apt install gdb pve-qemu-kvm-dbg Reading package lists... Done Building dependency tree... Done Reading state information... Done Package pve-qemu-kvm-dbg is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only...

https://www.mail-archive.com/kde-bugs-dist@kde.org/msg885246.html Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.22-1~deb12u1.amd64 Stack trace of thread 100710:

# coredumpctl info PID: 7899 (kvm) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Tue 2024-02-20 16:31:07 MSK (15min ago) Command Line: /usr/bin/kvm -id 110 -name VM,debug-threads=on -no-shutdown -chardev...

# coredumpctl list TIME PID UID GID SIG COREFILE EXE SIZE Tue 2024-02-20 16:31:43 MSK 7899 0 0 SIGSEGV present /usr/bin/qemu-system-x86_64 1.4G

I have got the dump. How can I upload it? It is 1.4Tb size

I also installed systemd-coredump. I will send you dump as soon as possible.

I'm try to use default display memory # qm config 109 agent: 1 audio0: device=ich9-intel-hda,driver=spice boot: order=virtio0 cores: 4 cpu: host description: %D0%AE%D1%80%D0%B8%D0%B4%D0%B8%D1%87%D0%B5%D1%81%D0%BA%D0%B8%D0%B9 %D0%BE%D1%82%D0%B4%D0%B5%D0%BB machine: pc-q35-8.1 memory: 4096 meta...

same issue # pveversion pve-manager/8.1.4/ec5affc9e41f1d79 (running kernel: 6.5.11-8-pve)

Can you recommended me what should I exclude from AV scan to stable work of hypervisor