Displaying 6 results from an estimated 6 matches for "virstoragefilereportbrokenchain".
2017 Dec 23
2
Re: [BUG] Not exiting media forced a promptly close of libvirt 3.10
...lease let me ask: If understand correctly this issue occoured and reported
in 3.9? And the fix is for 3.11 or 4.0?
Best regards
Holger
Am 22.12.2017 um 22:27 schrieb Jim Fehlig:
> On 12/22/2017 02:21 AM, Holger Schranz wrote:
>> Thread 1 (Thread 0x7f0d525ab700 (LWP 10729)):
>> #0 virStorageFileReportBrokenChain (errcode=2,
>> src=src@entry=0x7f0d4004ac40, parent=0x7f0d4004ac40) at
>> storage/storage_source.c:422
>> access_user = <optimized out>
>> access_group = <optimized out>
>> __FUNCTION__ = "virStorageFileReportBrokenChain&qu...
2017 Dec 22
2
Re: [BUG] Not exiting media forced a promptly close of libvirt 3.10
...quot;, worker = true,
opaque = 0x5557f2391c60}
#4 0x00007f0d55e64744 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#5 0x00007f0d55ba2aad in clone () from /lib64/libc.so.6
No symbol table info available.
Thread 1 (Thread 0x7f0d525ab700 (LWP 10729)):
#0 virStorageFileReportBrokenChain (errcode=2,
src=src@entry=0x7f0d4004ac40, parent=0x7f0d4004ac40) at
storage/storage_source.c:422
access_user = <optimized out>
access_group = <optimized out>
__FUNCTION__ = "virStorageFileReportBrokenChain"
#1 0x00007f0d4b56a262 in qemuDomainDeter...
2017 Dec 22
0
Re: [BUG] Not exiting media forced a promptly close of libvirt 3.10
On 12/22/2017 02:21 AM, Holger Schranz wrote:
> Thread 1 (Thread 0x7f0d525ab700 (LWP 10729)):
> #0 virStorageFileReportBrokenChain (errcode=2, src=src@entry=0x7f0d4004ac40,
> parent=0x7f0d4004ac40) at storage/storage_source.c:422
> access_user = <optimized out>
> access_group = <optimized out>
> __FUNCTION__ = "virStorageFileReportBrokenChain"
> #1 0x00007f0d4b5...
2017 Dec 23
0
Re: [BUG] Not exiting media forced a promptly close of libvirt 3.10
...ue occoured and
> reported
> in 3.9? And the fix is for 3.11 or 4.0?
>
> Best regards
>
> Holger
>
> Am 22.12.2017 um 22:27 schrieb Jim Fehlig:
>> On 12/22/2017 02:21 AM, Holger Schranz wrote:
>>> Thread 1 (Thread 0x7f0d525ab700 (LWP 10729)):
>>> #0 virStorageFileReportBrokenChain (errcode=2,
>>> src=src@entry=0x7f0d4004ac40, parent=0x7f0d4004ac40) at
>>> storage/storage_source.c:422
>>> access_user = <optimized out>
>>> access_group = <optimized out>
>>> __FUNCTION__ = "virStorageFile...
2017 Dec 22
2
[BUG] Not exiting media forced a promptly close of libvirt 3.10
...New LWP 10728]
[New LWP 10740]
[New LWP 10751]
[New LWP 10742]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/local/sbin/libvirtd -d'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 virStorageFileReportBrokenChain (errcode=2,
src=src@entry=0x7f0d4004ac40, parent=0x7f0d4004ac40)
at storage/storage_source.c:422
422 unsigned int access_user = src->drv->uid;
[Current thread is 1 (Thread 0x7f0d525ab700 (LWP 10729))]
Missing separate debuginfos, use: zypper install
device-mapper-debuginfo-1.02...
2017 Dec 22
0
Re: [BUG] Not exiting media forced a promptly close of libvirt 3.10
.../systemd/coredump/core.libvirtd.0.01603763bc784c7380e310d5eea124d6.10728.1513931319000000.xz
> Message: Process 10728 (libvirtd) of user 0 dumped core.
> Core was generated by `/usr/local/sbin/libvirtd -d'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 virStorageFileReportBrokenChain (errcode=2,
> src=src@entry=0x7f0d4004ac40, parent=0x7f0d4004ac40)
> at storage/storage_source.c:422
> 422 unsigned int access_user = src->drv->uid;
> [Current thread is 1 (Thread 0x7f0d525ab700 (LWP 10729))]
> Missing separate debuginfos, use: zypper install
>...