libvirt users - Nov 2017 - Urgent: virsh - change-media run into a promptly close of libvirt

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.

----------------------

At the end all open consoles of all virtual machines closed and the 
virt-manager also.
A restart of the libvirtd is possible but not helpful

The virsh change-media commands are in procedure andused since a long time.
I need the change-media function at the installation of our test systems.
Therefor I need an urgent help please

Best regards

Holger




---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

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 :|

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