Recent content by garbled

My setup for the VM that keeps crashing (also, the only one I heavily use) Curious, is everyone having this problem on multi-monitor? All my other spice VM's are single monitor.

I have less problems on my slower machines. When I ran my VM's on an X5670, I had zero crashes ever. When I moved them to a 6140, sometimes it would crash 4-5 times a day. Currently I have the VM sitting on an e5-2690v2 and it's been happy for a week now. Previously it did crash once each on...

https://gitlab.freedesktop.org/spice/spice/-/issues/87 Throwing this link here for future reference

Got one

Hrmm... it looks like my coredumps timeout while being taken, for some wacky reason... The coredump program gets sigkilled...?

Worth noting, the VM of mine that keeps crashing is a debian 11 VM, not windows. So guess would be not guest related.

On mine, which has the same symptoms as above (need to reinstall the core dump capture), the load is pretty minimal on the host. Maybe 4-5% cpu, dual-6140 server. As for what was happening on the guest, I was just scrolling up and down in a web page on firefox (not a complex one, pretty simple...

Here are some logs, from this morning, when the new node rebooted for some reason, and rejoined the cluster. Causing the expected chaos: Feb 25 03:22:55 altair corosync[11414]: [KNET ] link: Resetting MTU for link 0 because host 1 joined Feb 25 03:22:55 altair corosync[11414]: [KNET ]...

I've been having some super odd problems lately, which I thought were a one-off, but now, there is something seriously wrong. Current state: I have one node newly added to a 5 node cluster. If I start corosync and pve-cluster on that node, within 60 seconds, it starts spamming TOTEM retransmit...

I know that stacktrace isn't mine, but I'm using: root@jabbah:~# dpkg -l | grep virt-viewer ii virt-viewer 7.0-2 amd64 Displaying the graphical console of a virtual machine root@jabbah:~# cat /etc/debian_version 11.3 I have not...

Just more data, mine started screaming this into the logs last night. That PID is for the vm that keeps crashing. No crash yet though, so?? Feb 20 08:04:42 ukdah QEMU[2350804]: Resetting rate control (65559 frames) Feb 20 08:04:44 ukdah QEMU[2350804]: Resetting rate control (65923 frames) Feb...

No usb on either side for this VM. The crash is super random. One day, it happened like 3 times, then, 2 weeks with no crash and I thought all was well again. Lately it's been every 2-3 days. Basically, this VM is my daily driver workstation. So I use it *alot*. Haven't had the crash since...

root@ukdah:~# pveversion -v proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve) pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79) proxmox-kernel-helper: 8.1.0 pve-kernel-5.15: 7.4-9 proxmox-kernel-6.5: 6.5.11-7 proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7 pve-kernel-5.0: 6.0-11...

Again today with: Feb 09 06:12:32 ukdah kernel: SPICE Worker[2137550]: segfault at 7f5f240007b0 ip 00007f666590aedd sp 00007f603ddf5dd0 error 4 in libc.so.6[7f666589c000+155000] likely on CPU 19 (core 1, socket 1) Feb 09 06:12:32 ukdah kernel: Code: 08 48 8b 4f 08 48 89 c8 48 83 e0 f8 48 3b 04...

I'm starting to see random crashes with one of my VM's after upgrading to 8.x a few weeks ago. I thought it was maybe a one-off, but this one VM keeps crashing over and over. Prior to this, this particular VM had an uptime of months with constant use. syslog on the proxmox server shows the...