similar to: Urgent: virsh - change-media run into a promptly close of libvirt

Hi Daniel, here are any informations. A little bit strange, coredumpctl showthe libvirtd. coredumpctl dump libvirt and info libvirt  no information. Best regards Holger -------------------------------------------------------------------------- etcsvms5:/var/adm # coredumpctl TIME                            PID   UID   GID SIG PRESENT EXE Tue 2017-11-07 16:22:57 CET     485     0     0  11

Ups ... my fault ... libvirtd instead libvirt .... etcsvms5:/var/lib/systemd/coredump # coredumpctl info libvirtd            PID: 10177 (libvirtd)            UID: 0 (root)            GID: 0 (root)         Signal: 11 (SEGV)      Timestamp: Tue 2017-11-14 10:11:32 CET (9h ago)   Command Line: /usr/local/sbin/libvirtd -d     Executable: /usr/local/sbin/libvirtd  Control Group: /         

On Tue, Nov 14, 2017 at 06:47:04PM +0100, Holger Schranz wrote: > Hello, > > I use the virsh change-media command and since the combination of: > > etcsvms5:/kvm/CS8400/M1 # virsh version > Compiled against library: libvirt 3.9.0 > Using library: libvirt 3.9.0 > Using API: QEMU 3.9.0 > Running hypervisor: QEMU 2.10.1 > > etcsvms5:/kvm/CS8400/M1 # > > I

On Tue, Nov 14, 2017 at 07:19:01PM +0100, Holger Schranz wrote: > Ups ... my fault ... > > libvirtd instead libvirt .... > > > etcsvms5:/var/lib/systemd/coredump # coredumpctl info libvirtd >            PID: 10177 (libvirtd) >            UID: 0 (root) >            GID: 0 (root) >         Signal: 11 (SEGV) >      Timestamp: Tue 2017-11-14 10:11:32 CET (9h ago)

On 11/15/2017 06:54 AM, Holger Schranz wrote: > Thread 1 (Thread 0x7f4a069cc700 (LWP 10178)): > #0 0x00007f49ff969170 in qemuDomainChangeEjectableMedia ( > driver=driver@entry=0x7f49f841b700, vm=vm@entry=0x7f49ec02fbd0, > disk=disk@entry=0x7f49ec0375d0, newsrc=0x7f49e8014d10, force=force@entry=false) > at qemu/qemu_hotplug.c:303 This is fixed in current upstream by

On Thu, May 02, 2019 at 01:07:32PM +0200, Michal Privoznik wrote: >On 5/2/19 12:08 PM, Lothar Schilling wrote: > >> I turned logging up to maximum. That's all I get: >> >> May  2 11:02:06 hl308-3 systemd: Starting Virtualization daemon... >> May  2 11:02:06 hl308-3 libvirtd: 472: info : libvirt version: 4.5.0, package: 10.el7_6.7 (CentOS BuildSystem

Am 03.05.2019 um 16:43 schrieb Martin Kletzander: > On Thu, May 02, 2019 at 02:25:28PM +0200, Martin Kletzander wrote: >> On Thu, May 02, 2019 at 01:07:32PM +0200, Michal Privoznik wrote: >>> On 5/2/19 12:08 PM, Lothar Schilling wrote: >>> >>>> I turned logging up to maximum. That's all I get: >>>> >>>> May  2 11:02:06 hl308-3

I am unable to locate systemd-coredump service on CentOS 7.5. It is not listed under "systemctl -a" and also I'm unable to locate the associated unit file (folder /usr/lib/systemd/system/ ). Am I missing any package which installs this service?

Hello, In the .xml file I use a media which is no longer available. In the past, I got the information media not available and the creation of the VM was stopped - O.k. behavior. Since 3.10 the libvirtd stopped promptly and all open consoles windows and the virt-manager closed promptly. For diagnose: etcsvms1:/kvm/CS8200/M5 # coredumpctl TIME PID UID GID SIG

Den 2023-04-05 kl. 09:47, skrev Peter Krempa: > The backup operation is quite complex so it is possible. > Please have a look into /var/log/libvirt/qemu/$VMNAME.log to see whether > qemu logged something like an assertion failure before crashing. > > Additionally you can have a look into 'coredumpctl' whether there are > any recorded crashes of

The reason given is shut off (crashed). So something virsh backup-begin does is causing he guest to crash? Den 2023-04-04 kl. 16:58, skrev Peter Krempa: > On Tue, Apr 04, 2023 at 16:28:18 +0200, Andr? Malm wrote: >> Hello, >> >> For some vms the virsh backup-begin sometimes shuts off the vm and returns >> "error: operation failed: domain is not running"

Found while working on the retry filter. Swap the order of the two patches to see nbdkit ignore assertion failures with status 0. Eric Blake (2): server: Propagate unexpected nbdkit failure with --run tests: Enhance captive test server/captive.c | 43 ++++++++++++++++++++++++++++++---------- tests/test-captive.sh | 46 +++++++++++++++++++++++++++++++++++++++---- 2 files changed, 75

We are happy to announce 2.3.17.1 patch release of Dovecot. This contains some fixes for issues found after 2.3.17 release. https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy -- - dsync: Add back

We are happy to announce 2.3.17.1 patch release of Dovecot. This contains some fixes for issues found after 2.3.17 release. https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.17.1.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy -- - dsync: Add back

On Fri, Dec 22, 2017 at 09:52:33AM +0100, Holger Schranz wrote: > etcsvms1:/kvm/CS8200/M5 # coredumpctl gdb libvirtd > PID: 10728 (libvirtd) > UID: 0 (root) > GID: 0 (root) > Signal: 11 (SEGV) > Timestamp: Fri 2017-12-22 09:28:39 CET (18min ago) > Command Line: /usr/local/sbin/libvirtd -d > Executable:

https://bugs.freedesktop.org/show_bug.cgi?id=93795 Bug ID: 93795 Summary: G98: GL(X) compositing - XRandR DPMS trouble Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

Hi, I'm hitting that issue since Mesa 20.0.6 and it is present still in latest version 20.1.7 ``` [tkloczko at barrel SPECS]$ coredumpctl gdb 3926866 PID: 3926866 (test_va_api) UID: 1000 (tkloczko) GID: 1000 (tkloczko) Signal: 11 (SEGV) Timestamp: Sun 2020-09-13 18:57:06 BST (32s ago) Command Line: ./test_va_api Executable:

On Thu, May 02, 2019 at 02:25:28PM +0200, Martin Kletzander wrote: >On Thu, May 02, 2019 at 01:07:32PM +0200, Michal Privoznik wrote: >>On 5/2/19 12:08 PM, Lothar Schilling wrote: >> >>> I turned logging up to maximum. That's all I get: >>> >>> May  2 11:02:06 hl308-3 systemd: Starting Virtualization daemon... >>> May  2 11:02:06 hl308-3

I think were getting closer: I did: - I edited /etc/default/asterisk to include : AST_USER="root" AST_GROUP="root" # systemctl daemon-reload # systemctl start asterisk # ps aux | grep asterisk root 3602 7.1 2.5 60332 26012 ? Ssl 16:00 0:03 /usr/sbin/asterisk -U root -G root -g # rasterisk # pkill -SEGV asterisk Then console showed: Segmentation error (core

Summary: Changeset 10173 - 64bit UP and SMP guests boot cleanly - 32bit UP guests boot clean and 32bit SMP guests still fail to boot (see failure.7) - 32bit UP guests lockup under load with "ata1: command 0x25 timeout" (see failure.4) - 64bit SMP 2 CPU guests lockup under load with "ata1: command 0x25 timeout" (see failure.2) - 32bit UP guest crashed on user load test