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 got the following problem: ---------------------- etcsvms5:/kvm/CS8400/M1 # virsh change-media S5VCS84M1-VLP0 hdc --eject Successfully ejected media. etcsvms5:/kvm/CS8400/M1 # virsh change-media S5VCS84M1-VLP0 hdc /home/kvm/etcsdvmb/Medien/V7.0A/CS_licenses/key-cd_VCS85FTSVTL.iso --insert error: Disconnected from qemu:///system due to end of file error: Failed to complete action insert on media error: End of file while reading data: Input/output error ---------------------- journalctl -b | less shows the following: Nov 14 10:11:32 etcsvms5 kernel: libvirtd[10178]: segfault at 10 ip 00007f49ff969170 sp 00007f4a069cb940 error 4 in libvirt_driver_qemu.so[7f49ff8d9000+172000] Nov 14 10:11:37 etcsvms5 systemd-coredump[42152]: Process 10177 (libvirtd) of user 0 dumped core.

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 /usr/sbin/plymouthd Wed 2017-11-08 14:44:12 CET     485     0     0  11 /usr/sbin/plymouthd Tue 2017-11-14 10:11:37 CET   10177     0     0  11 * /usr/local/sbin/libvirtd etcsvms5:/var/adm # coredumpctl --help etcsvms5:/var/adm # coredumpctl dump libvirt No match found. etcsvms5:/var/adm # coredumpctl info libvirt No coredumps found. etcsvms5:/var/adm # etcsvms5:/var/adm # coredumpctl info . .            PID: 10177 (libvirtd)            UID: 0 (root)            GID: 0 (root)         Signal: 11 (SEGV)      Timestamp: Tue 2017-11-14 10:11:32 CET (8h ago)   Command Line: /usr/local/sbin/libvirtd -d     Executable: /usr/local/sbin/libvirtd  Control Group: /          Slice: -.slice        Boot ID: 4d5f74eefb0244c2bc3b2c99986dcee8     Machine ID: beeb301fe87a14b2eabdb6a75a01cbae       Hostname: etcsvms5       Coredump: /var/lib/systemd/coredump/core.libvirtd.0.4d5f74eefb0244c2bc3b2c99986dcee8.10177.1510650692000000.xz        Message: Process 10177 (libvirtd) of user 0 dumped core. etcsvms5:/var/adm # Am 14.11.2017 um 18:51 schrieb Daniel P. Berrange: > 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 got the following problem: >> >> ---------------------- >> >> etcsvms5:/kvm/CS8400/M1 # virsh change-media S5VCS84M1-VLP0 hdc --eject >> Successfully ejected media. >> >> etcsvms5:/kvm/CS8400/M1 # virsh change-media S5VCS84M1-VLP0 hdc >> /home/kvm/etcsdvmb/Medien/V7.0A/CS_licenses/key-cd_VCS85FTSVTL.iso >> --insert >> error: Disconnected from qemu:///system due to end of file >> error: Failed to complete action insert on media >> error: End of file while reading data: Input/output error >> >> ---------------------- >> >> journalctl -b | less shows the following: >> >> Nov 14 10:11:32 etcsvms5 kernel: libvirtd[10178]: segfault at 10 ip >> 00007f49ff969170 sp 00007f4a069cb940 error 4 in >> libvirt_driver_qemu.so[7f49ff8d9000+172000] >> Nov 14 10:11:37 etcsvms5 systemd-coredump[42152]: Process 10177 >> (libvirtd) >> of user 0 dumped core. > Seeing the stack trace of libvirtd will be key to identifying the > bug. With > any luck systemd-coredump will have captured that. So can you run > 'coredumpctl' > to get the stack trace it saved. > > Then I'd suggest filing a bugzilla ticket against libvirt with the > resulting > info so we have a record of it. > > Regards, > Daniel --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users

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) >   Command Line: /usr/local/sbin/libvirtd -d >     Executable: /usr/local/sbin/libvirtd >  Control Group: / >          Slice: -.slice >        Boot ID: 4d5f74eefb0244c2bc3b2c99986dcee8 >     Machine ID: beeb301fe87a14b2eabdb6a75a01cbae >       Hostname: etcsvms5 >       Coredump: /var/lib/systemd/coredump/core.libvirtd.0.4d5f74eefb0244c2bc3b2c99986dcee8.10177.1510650692000000.xz >        Message: Process 10177 (libvirtd) of user 0 dumped core. > etcsvms5:/var/lib/systemd/coredump # coredumpctl dump 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: / >          Slice: -.slice >        Boot ID: 4d5f74eefb0244c2bc3b2c99986dcee8 >     Machine ID: beeb301fe87a14b2eabdb6a75a01cbae >       Hostname: etcsvms5 >       Coredump: /var/lib/systemd/coredump/core.libvirtd.0.4d5f74eefb0244c2bc3b2c99986dcee8.10177.1510650692000000.xz >        Message: Process 10177 (libvirtd) of user 0 dumped core. > Refusing to dump core to tty. > etcsvms5:/var/lib/systemd/coredump # Probably need to try 'coredumpctl gdb libvirtd' to launch the debugger from where you can use 'thread apply all backtrace' to get the stack Regards, Daniel

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 commit id '8056721cbb' John > #1 0x00007f49ff9e9253 in qemuDomainChangeDiskLive (force=false, driver=0x7f49f841b700, > dev=<optimized out>, vm=<optimized out>, conn=<optimized out>) > at qemu/qemu_driver.c:7842 > #2 qemuDomainUpdateDeviceLive (dom=<optimized out>, force=false, dev=<optimized out>, > vm=<optimized out>, conn=<optimized out>) at qemu/qemu_driver.c:7873 > #3 qemuDomainUpdateDeviceFlags (dom=<optimized out>, xml=<optimized out>, flags=1) > at qemu/qemu_driver.c:8583 > #4 0x00007f4a0cdd3f47 in virDomainUpdateDeviceFlags ( > domain=domain@entry=0x7f49e800a470, > xml=0x7f49e800a530 "<disk type=\"file\" device=\"cdrom\">\n <driver name=\"qemu\" type=\"raw\"/>\n <source file=\"/home/kvm/etcsdvmb/Medien/V7.0A/CS_licenses/key-cd_VCS85FTSVTL.iso\"/>\n <target dev=\"hdc\" bus=\"sata\" tr"..., flags=0) > at libvirt-domain.c:8338 > #5 0x000056177c3e3c3e in remoteDispatchDomainUpdateDeviceFlags (server=0x56177ca8ba60, > msg=0x56177ca98210, args=0x7f49e8002e10, rerr=0x7f4a069cbc90, > client=<optimized out>) at remote_dispatch.h:12339 > #6 remoteDispatchDomainUpdateDeviceFlagsHelper (server=0x56177ca8ba60, > client=<optimized out>, msg=0x56177ca98210, rerr=0x7f4a069cbc90, > args=0x7f49e8002e10, ret=0x7f49e8004770) at remote_dispatch.h:12315 > #7 0x00007f4a0ce49a02 in virNetServerProgramDispatchCall (msg=0x56177ca98210, > client=0x56177ca99b80, server=0x56177ca8ba60, prog=0x56177ca986f0) > at rpc/virnetserverprogram.c:437 > #8 virNetServerProgramDispatch (prog=0x56177ca986f0, > server=server@entry=0x56177ca8ba60, client=0x56177ca99b80, msg=0x56177ca98210) > at rpc/virnetserverprogram.c:307 > #9 0x000056177c40ab6d in virNetServerProcessMsg (msg=<optimized out>, > prog=<optimized out>, client=<optimized out>, srv=0x56177ca8ba60) > at rpc/virnetserver.c:148 > #10 virNetServerHandleJob (jobOpaque=<optimized out>, opaque=0x56177ca8ba60) > at rpc/virnetserver.c:169 > #11 0x00007f4a0cd0cb01 in virThreadPoolWorker (opaque=opaque@entry=0x56177ca989f0) > at util/virthreadpool.c:167 > #12 0x00007f4a0cd0b8f8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 > #13 0x00007f4a0a254744 in start_thread () from /lib64/libpthread.so.0 > #14 0x00007f4a09f92aad in clone () from /lib64/libc.so.6 > (gdb) q > PID: 10177 (libvirtd) > UID: 0 (root) > GID: 0 (root) > Signal: 11 (SEGV) > Timestamp: Tue 2017-11-14 10:11:32 CET (1 day 2h ago) > Command Line: /usr/local/sbin/libvirtd -d > Executable: /usr/local/sbin/libvirtd > Control Group: / > Slice: -.slice > Boot ID: 4d5f74eefb0244c2bc3b2c99986dcee8 > Machine ID: beeb301fe87a14b2eabdb6a75a01cbae > Hostname: etcsvms5 > Coredump: /var/lib/systemd/coredump/core.libvirtd.0.4d5f74eefb0244c2bc3b2c99986dcee8.10177.1510650692000000.xz > Message: Process 10177 (libvirtd) of user 0 dumped core.