- On Jun 14, 2019, at 9:14 AM, Peter Krempa pkre...@redhat.com wrote:
> On Thu, Jun 13, 2019 at 16:01:18 +0200, Lentes, Bernd wrote:
>>
>> - On Jun 13, 2019, at 1:08 PM, Bernd Lentes
>> bernd.len...@helmholtz-muenchen.de wrote:
>>
>> I found further information in /var/log/messages fo
On Thu, Jun 13, 2019 at 16:01:18 +0200, Lentes, Bernd wrote:
>
> - On Jun 13, 2019, at 1:08 PM, Bernd Lentes
> bernd.len...@helmholtz-muenchen.de wrote:
>
> I found further information in /var/log/messages for both occurrences:
>
> 2019-06-01T03:05:31.620725+02:00 ha-idg-2 systemd-coredump[
- On Jun 13, 2019, at 1:08 PM, Bernd Lentes
bernd.len...@helmholtz-muenchen.de wrote:
I found further information in /var/log/messages for both occurrences:
2019-06-01T03:05:31.620725+02:00 ha-idg-2 systemd-coredump[14253]: Core Dumping
has been disabled for process 30590 (qemu-system-x86
- On Jun 13, 2019, at 9:56 AM, Peter Krempa pkre...@redhat.com wrote:
>
> Thanks for comming back to me with the information.
>
> Unfortunately this is not a full debug log but I can try to tell you
> what I see here:
I configured libvirtd that way:
ha-idg-1:~ # grep -Ev '^$|#' /etc/lib
On Tue, Jun 11, 2019 at 19:19:05 +0200, Lentes, Bernd wrote:
[...]
>
> Hi,
Hi,
>
> it happened again.
> Following the log of my script it started on 8th of june at 5:59:09 (UTC+2)
> to blockcommit the domain.
> These are the related lines in libvirtd.log:
> ==
- On Jun 5, 2019, at 4:49 PM, Peter Krempa pkre...@redhat.com wrote:
> On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote:
>> Hi Peter,
>>
>> thanks for your help.
>>
>> - On Jun 5, 2019, at 9:27 AM, Peter Krempa pkre...@redhat.com wrote:
>
> [...]
>
>>
>> >
>> > So that's
On Wed, Jun 05, 2019 at 18:02:06 +0200, Lentes, Bernd wrote:
[...]
> Hi,
>
> i followed https://wiki.libvirt.org/page/DebugLogs.
> Where do i have to set LIBVIRT_LOG_OUTPUTS="1:file:/tmp/libvirt_client.log" ?
> Also in /etc/libvirt/libvirtd.conf ?
No, that's an environment variable if you want
- On Jun 5, 2019, at 4:49 PM, Peter Krempa pkre...@redhat.com wrote:
> On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote:
>> Hi Peter,
>>
>> thanks for your help.
>>
>> - On Jun 5, 2019, at 9:27 AM, Peter Krempa pkre...@redhat.com wrote:
>
> [...]
>
>>
>> >
>> > So that'
On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote:
> Hi Peter,
>
> thanks for your help.
>
> - On Jun 5, 2019, at 9:27 AM, Peter Krempa pkre...@redhat.com wrote:
[...]
>
> >
> > So that's interresting. Usually assertion failure in qemu leads to
> > calling abort() and thus the v
Hi Peter,
thanks for your help.
- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkre...@redhat.com wrote:
>> =
>> ...
>> 2019-05-31 20:31:34.481+: 4170: error : qemuMonitorIO:719 : internal
>> error:
>> End of file from qemu monit
On Tue, Jun 04, 2019 at 14:44:29 +0200, Lentes, Bernd wrote:
> Hi,
Hi,
>
> i have several domains running on a 2-node HA-cluster.
> Each night i create snapshots of the domains, after copying the consistent
> raw file to a CIFS server i blockcommit the changes into the raw files.
> That's runn
Hi,
i have several domains running on a 2-node HA-cluster.
Each night i create snapshots of the domains, after copying the consistent raw
file to a CIFS server i blockcommit the changes into the raw files.
That's running quite well.
But recent the blockcommit didn't work for one domain:
I create
12 matches
Mail list logo