On 11/06/15 11:00 +, Soeren Malchow wrote:
We are still having this problem and we can not figure out what to do, i
sent the logs already as download, can i do anything else to help ?
Hi. I'm sorry but I don't have any new information for you yet. One
thing you could do is create a new bu
We are still having this problem and we can not figure out what to do, i
sent the logs already as download, can i do anything else to help ?
On 04/06/15 17:08, "Soeren Malchow" wrote:
>Hi,
>
>I would send those, but unfortunately we did not think about the journals
>getting deleted after a re
Hi,
I would send those, but unfortunately we did not think about the journals
getting deleted after a reboot.
I just made the journals persistent on the servers, we are trying to
trigger the error again last time we only got half way through the VM’s
when removing the snapshots so we have a good
On 04/06/15 13:08 +, Soeren Malchow wrote:
Hi Adam, Hi Eric,
We had this issue again a few minutes ago.
One machine went down exactly the same way as described, the machine had
only one snapshot and it was the only snapshot that was removed, before
that in the same scriptrun we deleted the
Hi Adam, Hi Eric,
We had this issue again a few minutes ago.
One machine went down exactly the same way as described, the machine had
only one snapshot and it was the only snapshot that was removed, before
that in the same scriptrun we deleted the snapshots of 15 other Vms, some
without, some wit
Hi,
This is not happening every time, the last time i had this, it was a
script runnning, and something like th 9. Vm and the 23. Vm had a problem,
and it is not always the same VMS, it is not about the OS (happen for
Windows and Linux alike)
And as i said it also happened when i tried to remove
On 03/06/15 07:36 +, Soeren Malchow wrote:
Dear Adam
First we were using a python script that was working on 4 threads and
therefore removing 4 snapshots at the time throughout the cluster, that
still caused problems.
Now i took the snapshot removing out of the threaded part an i am just
lo
June 2015 01:35
>>To: Soeren Malchow
>>mailto:soeren.malc...@mcon.net>>,
>>"libvirt-us...@redhat.com<mailto:libvirt-us...@redhat.com>"
>>mailto:libvirt-us...@redhat.com>>, users
>>mailto:users@ovirt.org>>
>>Subject: Re: [ovir
Date: Monday 1 June 2015 01:35
To: Soeren Malchow mailto:soeren.malc...@mcon.net>>,
"libvirt-us...@redhat.com<mailto:libvirt-us...@redhat.com>"
mailto:libvirt-us...@redhat.com>>, users mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Bug in Snapshot Remo
Adam, can you take a look at this please?
Thanks!
- Original Message -
> From: "Soeren Malchow"
> To: "Soeren Malchow" , libvirt-us...@redhat.com,
> "users"
> Sent: Monday, June 1, 2015 2:39:24 AM
> Subject: Re: [ovirt-users] Bug in Snaps
"libvirt-us...@redhat.com<mailto:libvirt-us...@redhat.com>"
mailto:libvirt-us...@redhat.com>>, users
mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Bug in Snapshot Removing
Small addition again:
This error shows up in the log while removing snapshots WITHOUT r
;/usr/share/vdsm/virt/vm.py", line 5759, in queryBlockJobs…
—
From: Soeren Malchow mailto:soeren.malc...@mcon.net>>
Date: Monday 1 June 2015 00:56
To: "libvirt-us...@redhat.com<mailto:libvirt-us...@redhat.com>"
mailto:libvirt-us...@redhat.com>>, users
mailto:users@
Dear all
I am not sure if the mail just did not get any attention between all the mails
and this time it is also going to the libvirt mailing list.
I am experiencing a problem with VM becoming unresponsive when removing
Snapshots (Live Merge) and i think there is a serious problem.
Here are th
13 matches
Mail list logo
