Your message dated Mon, 15 Jan 2018 09:19:39 +0000
with message-id <e1eb0vb-0000h5...@fasolo.debian.org>
and subject line Bug#881293: fixed in libvirt 4.0.0~rc1-1
has caused the Debian Bug report #881293,
regarding libvirtd crashes when starting a vm with IDE cdrom
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
881293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt
Version: 3.10
Severity: grave

With libvirt version 3.10 I cannot start a VM. Reverting to 3.0
(Debian/stable) all is fine. This was initially found in GNOME-Boxes
but I have been able to reproduce on the command line using virsh.

Note also that I had the same issue with 3.9.

On one console:

$ LIBVIRT_DEBUG=1 gdb /usr/sbin/libvirtd

On a second console, I tried to start the VM:

$ virsh start boxes-winxp

Then I got this exception from libvirtd:

Thread 5 "libvirtd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7febad4a5700 (LWP 7867)]
0x00007feb94b109c8 in virStorageFileReportBrokenChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
(gdb) bt
#0  0x00007feb94b109c8 in virStorageFileReportBrokenChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
#1  0x00007feb7d266da3 in qemuDomainDetermineDiskChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#2  0x00007feb7d28eec2 in qemuProcessPrepareHost ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#3  0x00007feb7d294b71 in qemuProcessStart ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#4  0x00007feb7d2f5201 in ?? ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#5  0x00007feb7d2f58e6 in ?? ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#6  0x00007febb9e5e077 in virDomainCreate (domain=0x7feb980008c0)
    at ../../../src/libvirt-domain.c:6531
#7  0x000056190ba2ed9c in ?? ()
#8  0x00007febb9ec697c in virNetServerProgramDispatchCall (msg=0x56190d9e7590, 
    client=0x56190d9e6fb0, server=0x56190d9d00f0, prog=0x56190d9e4f40)
    at ../../../src/rpc/virnetserverprogram.c:437
#9  virNetServerProgramDispatch (prog=0x56190d9e4f40, server=0x56190d9d00f0, 
    client=0x56190d9e6fb0, msg=0x56190d9e7590)
    at ../../../src/rpc/virnetserverprogram.c:307
#10 0x000056190ba3e988 in ?? ()
#11 0x00007febb9da1c01 in virThreadPoolWorker (
    opaque=opaque@entry=0x56190d9ce9f0)
    at ../../../src/util/virthreadpool.c:167
#12 0x00007febb9da0f78 in virThreadHelper (data=<optimized out>)
    at ../../../src/util/virthread.c:206
#13 0x00007febb68b0519 in start_thread (arg=0x7febad4a5700)
    at pthread_create.c:456
#14 0x00007febb65f2a5f in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
(gdb) 

I noticed that running with 3.0 I had a message saying that /dev/sr0 is
not accessible. And indeed I do not have a CDROM on this machine. The
.xml were migrated from a machine with a CDROM to this new one.

Removing:

    <disk type='block' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source dev='/dev/sr0' startupPolicy='optional'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' target='0' unit='0'/>
    </disk>

Seems to fix the issue. Yet, libvirt should not crash on this. And the
backtrace makes sense with this fix BTW.

Please let me know if you need additional information.

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

--- End Message ---
--- Begin Message ---
Source: libvirt
Source-Version: 4.0.0~rc1-1

We believe that the bug you reported is fixed in the latest version of
libvirt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 881...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Günther <a...@sigxcpu.org> (supplier of updated libvirt package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 15 Jan 2018 09:44:37 +0100
Source: libvirt
Binary: libvirt-clients libvirt-daemon libvirt-daemon-driver-storage-gluster 
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-sheepdog 
libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt0 libvirt-doc 
libvirt-dev libvirt-sanlock libnss-libvirt libvirt-wireshark
Architecture: source
Version: 4.0.0~rc1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Libvirt Maintainers 
<pkg-libvirt-maintain...@lists.alioth.debian.org>
Changed-By: Guido Günther <a...@sigxcpu.org>
Description:
 libnss-libvirt - nss plugin providing IP add ress resolution for virtual 
machines
 libvirt-clients - Programs for the libvirt library
 libvirt-daemon - Virtualization daemon
 libvirt-daemon-driver-storage-gluster - Virtualization daemon glusterfs 
storage driver
 libvirt-daemon-driver-storage-rbd - Virtualization daemon RBD storage driver
 libvirt-daemon-driver-storage-sheepdog - Virtualization daemon Sheedog storage 
driver
 libvirt-daemon-driver-storage-zfs - Virtualization daemon ZFS storage driver
 libvirt-daemon-system - Libvirt daemon configuration files
 libvirt-dev - development files for the libvirt library
 libvirt-doc - documentation for the libvirt library
 libvirt-sanlock - Sanlock plugin for virtlockd
 libvirt-wireshark - Wireshark dissector for the libvirt protocol
 libvirt0   - library for interfacing with different virtualization systems
Closes: 846534 881293 884828
Changes:
 libvirt (4.0.0~rc1-1) experimental; urgency=medium
 .
   [ Guido Günther ]
   * [a225d2b] New upstream version 4.0.0~rc1
     (Closes: #881293, #846534)
   * [2270343] Rediff patches
 .
   [ intrigeri ]
   * [89b8ab4] Allow libvirt to kill unconfined domains
 .
   [ Christian Ehrhardt ]
   * [b2ce106] Clear more directories on purge
     (Closes: #884828)
   * [0cd10ab] Avoid apt seccomp issues due to libnss-libvirt
     (LP: #1732030)
Checksums-Sha1:
 6c3ebb711535af90e80f8e068a424094bd4a44f5 4511 libvirt_4.0.0~rc1-1.dsc
 efda66c5d9df7dca12e176fb6fad3cc1a96d9619 14991464 libvirt_4.0.0~rc1.orig.tar.xz
 02e6b65fa8df2dea49287f43472f488ada7d1ef9 67840 
libvirt_4.0.0~rc1-1.debian.tar.xz
 ffd56abac8ef8d66292996ec1b1f99fbd361f2b3 20329 
libvirt_4.0.0~rc1-1_amd64.buildinfo
Checksums-Sha256:
 901bd028b0081af5a708dab7a855afd2b4633debd6a36605b192db783bb6bb92 4511 
libvirt_4.0.0~rc1-1.dsc
 3fb305425746136774c1f49f303db30a113e20a6f8dee43b7c2bd12ce9cc25c4 14991464 
libvirt_4.0.0~rc1.orig.tar.xz
 a888979c94a4b00b02ca12723907f96283c9d982eb321cef23f47db8a409ca6f 67840 
libvirt_4.0.0~rc1-1.debian.tar.xz
 adf78dcc8187a4a1767b645a68a52b86178b6ae4d5de4e3bd4edb11ea6d02f8e 20329 
libvirt_4.0.0~rc1-1_amd64.buildinfo
Files:
 a23101e980eb65db9da41cdbf513d552 4511 libs optional libvirt_4.0.0~rc1-1.dsc
 bacea4cdd36e73cdadcd9c018f2188a5 14991464 libs optional 
libvirt_4.0.0~rc1.orig.tar.xz
 9fb3954b02f52dfbee6be3823e67ef30 67840 libs optional 
libvirt_4.0.0~rc1-1.debian.tar.xz
 b94c1bd1401785c5fe052ab62f7f9c1d 20329 libs optional 
libvirt_4.0.0~rc1-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEvHzQcjh1660F3xzZB7i3sOqYEgsFAlpcbfAACgkQB7i3sOqY
EgvRLxAAnRFJIPxWUrVFD1EOKGgNqH2rrfPX8LlAHmwSyA0ppF14rdMPaKVPDkmj
vadMIOOnpZPQF0lCczm8qm5/OLE9OWhr9OJygDwH6jSUAnA7rwJyLvO1xkj0THWD
sy1hdstVMHQzBu8XcjArEBqDlkJFJhOIKIBceJmqJcwwwYrRNkLpMQehDR1RDS9e
rjN/UsnRbhogKKgl6WpKzncGB6ZLwcCcdiGjGmliOa8dK3ZNRta54nS50Bn9AoeC
RXKZOme5PMuiHQuY39OMRTvAtcH7dyGmYoi0SXtSrHOkoM8d0xZdU6eEjh0ruFeR
080cDUUnJJTnT3nWWyirex0nzV3aLr0GtSvESsjsku+HM9blIbwfXsmzdPWPZOW0
3zdhVNDHzfGyR3s/rd7tI5cD2F6SBLbMfEDrXrpe8T0305lpr3rBGj3noG3CQzMF
GWtC92ywq2g2k8LRifVsTnAOemsECKAjiQEDbjfhp62ZG9ZWawKUNlfuaDUoK0pg
bdrD9jF2sp/19CpasNU67yBRJ/whtN03o6yGdY9uKlGfOBtLvqmY8qyn3fg6FBYc
7o0fIOd7/KcIKLfxEizmuVuFjTbD9fUYElrwGS7VWmxZRB/g9pPRWtx5j6fP4OhG
g9iHEhUyqrX3/TiTDNekqLdanc3/zD6eqz/zgwr2dgG+wOGjDc8=
=IeNv
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to