[libvirt-users] Urgent: virsh - change-media run into a promptly close of libvirt

Daniel P. Berrange berrange at redhat.com
Tue Nov 14 17:51:12 UTC 2017


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
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|




More information about the libvirt-users mailing list