* Stefan Priebe (s.pri...@profihost.ag) wrote:
>
> Am 13.02.2014 21:06, schrieb Dr. David Alan Gilbert:
> >* Stefan Priebe (s.pri...@profihost.ag) wrote:
> >>Am 10.02.2014 17:07, schrieb Dr. David Alan Gilbert:
> >>>* Stefan Priebe (s.pri...@profihost.ag) wrote:
> i could fix it by explicitly
Am 13.02.2014 21:06, schrieb Dr. David Alan Gilbert:
* Stefan Priebe (s.pri...@profihost.ag) wrote:
Am 10.02.2014 17:07, schrieb Dr. David Alan Gilbert:
* Stefan Priebe (s.pri...@profihost.ag) wrote:
i could fix it by explicitly disable xbzrle - it seems its
automatically on if i do not set t
got it here:
http://lists.nongnu.org/archive/html/qemu-devel/2014-02/msg02341.html
will try asap
Am 13.02.2014 21:06, schrieb Dr. David Alan Gilbert:
* Stefan Priebe (s.pri...@profihost.ag) wrote:
Am 10.02.2014 17:07, schrieb Dr. David Alan Gilbert:
* Stefan Priebe (s.pri...@profihost.ag) wro
Am 13.02.2014 21:06, schrieb Dr. David Alan Gilbert:
* Stefan Priebe (s.pri...@profihost.ag) wrote:
Am 10.02.2014 17:07, schrieb Dr. David Alan Gilbert:
* Stefan Priebe (s.pri...@profihost.ag) wrote:
i could fix it by explicitly disable xbzrle - it seems its
automatically on if i do not set t
* Stefan Priebe (s.pri...@profihost.ag) wrote:
> Am 10.02.2014 17:07, schrieb Dr. David Alan Gilbert:
> >* Stefan Priebe (s.pri...@profihost.ag) wrote:
> >>i could fix it by explicitly disable xbzrle - it seems its
> >>automatically on if i do not set the migration caps to false.
> >>
> >>So it see
Am 11.02.2014 14:45, schrieb Orit Wasserman:
> On 02/11/2014 03:33 PM, Stefan Priebe - Profihost AG wrote:
>>
>> Am 11.02.2014 14:32, schrieb Orit Wasserman:
>>> On 02/08/2014 09:23 PM, Stefan Priebe wrote:
i could fix it by explicitly disable xbzrle - it seems its
automatically on if i d
On 02/11/2014 03:33 PM, Stefan Priebe - Profihost AG wrote:
Am 11.02.2014 14:32, schrieb Orit Wasserman:
On 02/08/2014 09:23 PM, Stefan Priebe wrote:
i could fix it by explicitly disable xbzrle - it seems its
automatically on if i do not set the migration caps to false.
So it seems to be a xb
Am 11.02.2014 14:32, schrieb Orit Wasserman:
> On 02/08/2014 09:23 PM, Stefan Priebe wrote:
>> i could fix it by explicitly disable xbzrle - it seems its
>> automatically on if i do not set the migration caps to false.
>>
>> So it seems to be a xbzrle bug.
>>
>
> XBZRLE is disabled by default (ac
On 02/08/2014 09:23 PM, Stefan Priebe wrote:
i could fix it by explicitly disable xbzrle - it seems its automatically on if
i do not set the migration caps to false.
So it seems to be a xbzrle bug.
XBZRLE is disabled by default (actually all capabilities are off by default)
What version of Q
Am 10.02.2014 17:07, schrieb Dr. David Alan Gilbert:
* Stefan Priebe (s.pri...@profihost.ag) wrote:
i could fix it by explicitly disable xbzrle - it seems its
automatically on if i do not set the migration caps to false.
So it seems to be a xbzrle bug.
Stefan can you give me some more info on
* Stefan Priebe (s.pri...@profihost.ag) wrote:
> i could fix it by explicitly disable xbzrle - it seems its
> automatically on if i do not set the migration caps to false.
>
> So it seems to be a xbzrle bug.
Stefan can you give me some more info on your hardware and
migration setup; that stress
* Stefan Priebe (s.pri...@profihost.ag) wrote:
> i could fix it by explicitly disable xbzrle - it seems its
> automatically on if i do not set the migration caps to false.
>
> So it seems to be a xbzrle bug.
Ah right, yes that would make sense for the type of errors
you're seeing, and does make i
i could fix it by explicitly disable xbzrle - it seems its automatically
on if i do not set the migration caps to false.
So it seems to be a xbzrle bug.
Stefan
Am 07.02.2014 21:10, schrieb Stefan Priebe:
Am 07.02.2014 21:02, schrieb Dr. David Alan Gilbert:
* Stefan Priebe (s.pri...@profihost
Am 07.02.2014 21:02, schrieb Dr. David Alan Gilbert:
* Stefan Priebe (s.pri...@profihost.ag) wrote:
anything i could try or debug? to help to find the problem?
I think the most useful would be to see if the problem is
a new problem in the 1.7 you're using or has existed
for a while; depending
* Stefan Priebe (s.pri...@profihost.ag) wrote:
> anything i could try or debug? to help to find the problem?
I think the most useful would be to see if the problem is
a new problem in the 1.7 you're using or has existed
for a while; depending on the machine type you used, it might
be possible to
anything i could try or debug? to help to find the problem?
Stefan
Am 07.02.2014 14:45, schrieb Stefan Priebe - Profihost AG:
it's always the same "pattern" there are too many 0 instead of X.
only seen:
read:0x ... expected:0x
or
read:0x ... e
it's always the same "pattern" there are too many 0 instead of X.
only seen:
read:0x ... expected:0x
or
read:0x ... expected:0x
or
read:0xbf00bf00 ... expected:0xbfffbfff
or
read:0x ... expected:
Hi,
Am 07.02.2014 14:19, schrieb Paolo Bonzini:
> Il 07/02/2014 14:04, Stefan Priebe - Profihost AG ha scritto:
>> first of all i've now a memory image of a VM where i can reproduce it.
>
> You mean you start that VM with -incoming 'exec:cat /path/to/vm.img'?
> But google stress test doesn't repor
Hi,
Am 07.02.2014 14:15, schrieb Dr. David Alan Gilbert:
> * Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
>> Hi,
>>
>> Am 07.02.2014 14:08, schrieb Dr. David Alan Gilbert:
>>> * Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
>
first of all i've now a memory image
Il 07/02/2014 14:04, Stefan Priebe - Profihost AG ha scritto:
first of all i've now a memory image of a VM where i can reproduce it.
You mean you start that VM with -incoming 'exec:cat /path/to/vm.img'?
But google stress test doesn't report any error until you start
migration _and_ it finishe
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
> Hi,
>
> Am 07.02.2014 14:08, schrieb Dr. David Alan Gilbert:
> > * Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
> >> first of all i've now a memory image of a VM where i can reproduce it.
> >> reproducing does NOT work
Hi,
Am 07.02.2014 14:08, schrieb Dr. David Alan Gilbert:
> * Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
>> Hi,
>>
>> Am 07.02.2014 13:44, schrieb Paolo Bonzini:
>>> Il 07/02/2014 13:30, Stefan Priebe - Profihost AG ha scritto:
>>> i was able to reproduce with a longer running
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
> Hi,
>
> Am 07.02.2014 13:44, schrieb Paolo Bonzini:
> > Il 07/02/2014 13:30, Stefan Priebe - Profihost AG ha scritto:
> >>> >> i was able to reproduce with a longer running test VM running the
> >>> google
> >>> >> stress test.
> >>>
Hi,
Am 07.02.2014 13:44, schrieb Paolo Bonzini:
> Il 07/02/2014 13:30, Stefan Priebe - Profihost AG ha scritto:
>>> >> i was able to reproduce with a longer running test VM running the
>>> google
>>> >> stress test.
>>>
>>> Hmm that's quite a fun set of differences; I think I'd like
>>> to underst
Il 07/02/2014 13:30, Stefan Priebe - Profihost AG ha scritto:
>> i was able to reproduce with a longer running test VM running the google
>> stress test.
Hmm that's quite a fun set of differences; I think I'd like
to understand whether the pattern is related to the pattern of what
the test is do
Hi,
Am 07.02.2014 13:21, schrieb Dr. David Alan Gilbert:
> * Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
>> Hi,
>>
>> i was able to reproduce with a longer running test VM running the google
>> stress test.
>
> Hmm that's quite a fun set of differences; I think I'd like
> to unders
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
> Hi,
>
> i was able to reproduce with a longer running test VM running the google
> stress test.
Hmm that's quite a fun set of differences; I think I'd like
to understand whether the pattern is related to the pattern of what
the test
Hi,
i was able to reproduce with a longer running test VM running the google
stress test.
And it happens exacly when the migration finishes it does not happen
while the migration is running.
Google Stress Output displays Memory errors:
Page Error:
You mean to reproduce?
I'm more interested in seeing what type of corruption is happening;
if you've got a test VM that corrupts memory and we can run a program
in that vm that writes a known pattern into memory and checks it
then see what changed after migration, it might give a clue.
But obvi
Am 07.02.2014 10:31, schrieb Dr. David Alan Gilbert:
> * Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
>>
>> Am 07.02.2014 10:15, schrieb Dr. David Alan Gilbert:
>>> * Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
Am 07.02.2014 09:15, schrieb Alexandre DERUMIER:
>>
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
>
> Am 07.02.2014 10:15, schrieb Dr. David Alan Gilbert:
> > * Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
> >> Am 07.02.2014 09:15, schrieb Alexandre DERUMIER:
> >>>
> >>> do you use xbzrle for live migration ?
> >>
> >
Hi,
Am 07.02.2014 10:29, schrieb Marcin Gibuła:
> do you use xbzrle for live migration ?
no - i'm really stucked right now with this. Biggest problem i can't
reproduce with test machines ;-(
>>>
>>> Only being able to test on your production VMs isn't fun;
>>> is it possible or y
do you use xbzrle for live migration ?
no - i'm really stucked right now with this. Biggest problem i can't
reproduce with test machines ;-(
Only being able to test on your production VMs isn't fun;
is it possible or you to run an extra program on these VMs - e.g.
if we came up with a simple (
; - Mail original -
>>>
>>> De: "Stefan Priebe"
>>> À: "Dr. David Alan Gilbert"
>>> Cc: "Alexandre DERUMIER" , "qemu-devel"
>>>
>>> Envoyé: Jeudi 6 Février 2014 21:00:27
>>> Objet: R
De: "Stefan Priebe"
> > À: "Dr. David Alan Gilbert"
> > Cc: "Alexandre DERUMIER" , "qemu-devel"
> >
> > Envoyé: Jeudi 6 Février 2014 21:00:27
> > Objet: Re: [Qemu-devel] [pve-devel] QEMU LIve Migration - swap_free: Bad
> &
e"
> À: "Dr. David Alan Gilbert"
> Cc: "Alexandre DERUMIER" , "qemu-devel"
>
> Envoyé: Jeudi 6 Février 2014 21:00:27
> Objet: Re: [Qemu-devel] [pve-devel] QEMU LIve Migration - swap_free: Bad swap
> file entry
>
> Hi,
>
do you use xbzrle for live migration ?
- Mail original -
De: "Stefan Priebe"
À: "Dr. David Alan Gilbert"
Cc: "Alexandre DERUMIER" , "qemu-devel"
Envoyé: Jeudi 6 Février 2014 21:00:27
Objet: Re: [Qemu-devel] [pve-devel] QEMU LIve Migration -
Hi,
Am 06.02.2014 20:51, schrieb Dr. David Alan Gilbert:
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
some more things which happen during migration:
php5.2[20258]: segfault at a0 ip 00740656 sp 7fff53b694a0
error 4 in php-cgi[40+6d7000]
php5.2[20249]: segfault
* Stefan Priebe - Profihost AG (s.pri...@profihost.ag) wrote:
> some more things which happen during migration:
>
> php5.2[20258]: segfault at a0 ip 00740656 sp 7fff53b694a0
> error 4 in php-cgi[40+6d7000]
>
> php5.2[20249]: segfault at c ip 7f1fb8ecb2b8 sp 7fff642d9c20
>
On 06.02.2014 15:03, Stefan Priebe - Profihost AG wrote:
some more things which happen during migration:
php5.2[20258]: segfault at a0 ip 00740656 sp 7fff53b694a0
error 4 in php-cgi[40+6d7000]
php5.2[20249]: segfault at c ip 7f1fb8ecb2b8 sp 7fff642d9c20
error 4 in ZendOp
some more things which happen during migration:
php5.2[20258]: segfault at a0 ip 00740656 sp 7fff53b694a0
error 4 in php-cgi[40+6d7000]
php5.2[20249]: segfault at c ip 7f1fb8ecb2b8 sp 7fff642d9c20
error 4 in ZendOptimizer.so[7f1fb8e71000+147000]
cron[3154]: segfault at 7f
May be,
sadly i've no idea. Only using 3.10 Kernel with XFS.
Stefan
Am 06.02.2014 12:40, schrieb Alexandre DERUMIER:
>>> PS: all my guests do not even have !!SWAP!!
>
> Not sure is related to swap file.
>
> I found an similar problem here, triggered with suspend/resume on ext4
>
> http://lkm
>>PS: all my guests do not even have !!SWAP!!
Not sure is related to swap file.
I found an similar problem here, triggered with suspend/resume on ext4
http://lkml.indiana.edu/hypermail/linux/kernel/1106.3/01340.html
Maybe is it a guest kernel bug ?
- Mail original -
De: "Stefan Prieb
Am 06.02.2014 12:14, schrieb Alexandre DERUMIER:
> Do you force rbd_cache=true in ceph.conf?
no
> if yes, do you use cache=writeback ?
yes
So this should be safe.
PS: all my guests do not even have !!SWAP!!
# free|grep Swap
Swap:0 0 0
Stefan
> according to cep
Do you force rbd_cache=true in ceph.conf?
if yes, do you use cache=writeback ?
according to ceph doc:
http://ceph.com/docs/next/rbd/qemu-rbd/
"Important If you set rbd_cache=true, you must set cache=writeback or risk data
loss. Without cache=writeback, QEMU will not send flush requests to librb
45 matches
Mail list logo
