From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, pve-devel@pve.proxmox.com
Subject: Re: [Qemu-devel] [pve-devel] QEMU LIve Migration - swap_free: Bad swap file entry
Date: Thu, 06 Feb 2014 15:03:08 +0100 [thread overview]
Message-ID: <52F3961C.3000807@profihost.ag> (raw)
In-Reply-To: <52F37BBF.7060203@profihost.ag>
some more things which happen during migration:
php5.2[20258]: segfault at a0 ip 0000000000740656 sp 00007fff53b694a0
error 4 in php-cgi[400000+6d7000]
php5.2[20249]: segfault at c ip 00007f1fb8ecb2b8 sp 00007fff642d9c20
error 4 in ZendOptimizer.so[7f1fb8e71000+147000]
cron[3154]: segfault at 7f0008a70ed4 ip 00007fc890b9d440 sp
00007fff08a6f9b0 error 4 in libc-2.13.so[7fc890b67000+182000]
Stefan
Am 06.02.2014 13:10, schrieb Stefan Priebe - Profihost AG:
> 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://lkml.indiana.edu/hypermail/linux/kernel/1106.3/01340.html
>>
>>
>> Maybe is it a guest kernel bug ?
>>
>> ----- Mail original -----
>>
>> De: "Stefan Priebe - Profihost AG" <s.priebe@profihost.ag>
>> À: "Alexandre DERUMIER" <aderumier@odiso.com>
>> Cc: pve-devel@pve.proxmox.com, "qemu-devel" <qemu-devel@nongnu.org>
>> Envoyé: Jeudi 6 Février 2014 12:19:36
>> Objet: Re: [pve-devel] QEMU LIve Migration - swap_free: Bad swap file entry
>>
>>
>> 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 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 librbd. If QEMU exits uncleanly in this configuration, filesystems on top of rbd can be corrupted."
>>>
>>>
>>>
>>> ----- Mail original -----
>>>
>>> De: "Stefan Priebe" <s.priebe@profihost.ag>
>>> À: pve-devel@pve.proxmox.com, "qemu-devel" <qemu-devel@nongnu.org>
>>> Envoyé: Mercredi 5 Février 2014 18:51:15
>>> Objet: [pve-devel] QEMU LIve Migration - swap_free: Bad swap file entry
>>>
>>> Hello,
>>>
>>> after live migrating machines with a lot of memory (32GB, 48GB, ...) i
>>> see pretty often crashing services after migration and the guest kernel
>>> prints:
>>>
>>> [1707620.031806] swap_free: Bad swap file entry 00377410
>>> [1707620.031806] swap_free: Bad swap file entry 00593c48
>>> [1707620.031807] swap_free: Bad swap file entry 03201430
>>> [1707620.031807] swap_free: Bad swap file entry 01bc5900
>>> [1707620.031807] swap_free: Bad swap file entry 0173ce40
>>> [1707620.031808] swap_free: Bad swap file entry 011c0270
>>> [1707620.031808] swap_free: Bad swap file entry 03c58ae8
>>> [1707660.749059] BUG: Bad rss-counter state mm:ffff88064d09f380 idx:1
>>> val:1536
>>> [1707660.749937] BUG: Bad rss-counter state mm:ffff88064d09f380 idx:2
>>> val:-1536
>>>
>>> Qemu is 1.7
>>>
>>> Does anybody know a fix?
>>>
>>> Greets,
>>> Stefan
>>> _______________________________________________
>>> pve-devel mailing list
>>> pve-devel@pve.proxmox.com
>>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>>
next prev parent reply other threads:[~2014-02-06 14:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 17:51 [Qemu-devel] QEMU LIve Migration - swap_free: Bad swap file entry Stefan Priebe
2014-02-05 20:15 ` Dr. David Alan Gilbert
2014-02-06 7:20 ` Stefan Priebe - Profihost AG
2014-02-06 10:22 ` Orit Wasserman
2014-02-06 10:49 ` Stefan Priebe - Profihost AG
2014-02-06 11:14 ` [Qemu-devel] [pve-devel] " Alexandre DERUMIER
2014-02-06 11:19 ` Stefan Priebe - Profihost AG
2014-02-06 11:40 ` Alexandre DERUMIER
2014-02-06 12:10 ` Stefan Priebe - Profihost AG
2014-02-06 14:03 ` Stefan Priebe - Profihost AG [this message]
2014-02-06 14:12 ` Marcin Gibuła
2014-02-06 19:51 ` Dr. David Alan Gilbert
2014-02-06 20:00 ` Stefan Priebe
2014-02-07 8:15 ` Alexandre DERUMIER
2014-02-07 8:17 ` Stefan Priebe - Profihost AG
2014-02-07 9:15 ` Dr. David Alan Gilbert
2014-02-07 9:20 ` Stefan Priebe - Profihost AG
2014-02-07 9:29 ` Marcin Gibuła
2014-02-07 9:30 ` Stefan Priebe - Profihost AG
2014-02-07 9:31 ` Dr. David Alan Gilbert
2014-02-07 9:37 ` Stefan Priebe - Profihost AG
2014-02-07 12:02 ` Stefan Priebe - Profihost AG
2014-02-07 12:21 ` Dr. David Alan Gilbert
2014-02-07 12:30 ` Stefan Priebe - Profihost AG
2014-02-07 12:44 ` Paolo Bonzini
2014-02-07 13:04 ` Stefan Priebe - Profihost AG
2014-02-07 13:08 ` Dr. David Alan Gilbert
2014-02-07 13:10 ` Stefan Priebe - Profihost AG
2014-02-07 13:15 ` Dr. David Alan Gilbert
2014-02-07 13:21 ` Stefan Priebe - Profihost AG
2014-02-07 13:19 ` Paolo Bonzini
2014-02-07 13:39 ` Stefan Priebe - Profihost AG
2014-02-07 13:45 ` Stefan Priebe - Profihost AG
2014-02-07 19:21 ` Stefan Priebe
2014-02-07 20:02 ` Dr. David Alan Gilbert
2014-02-07 20:10 ` Stefan Priebe
2014-02-08 19:23 ` Stefan Priebe
2014-02-10 9:30 ` Dr. David Alan Gilbert
2014-02-10 16:07 ` Dr. David Alan Gilbert
2014-02-10 18:53 ` Stefan Priebe
2014-02-13 20:06 ` Dr. David Alan Gilbert
2014-02-13 20:26 ` Stefan Priebe
2014-02-13 20:31 ` Stefan Priebe
2014-02-13 21:18 ` Stefan Priebe
2014-02-14 9:06 ` Dr. David Alan Gilbert
2014-02-11 13:32 ` Orit Wasserman
2014-02-11 13:33 ` Stefan Priebe - Profihost AG
2014-02-11 13:45 ` Orit Wasserman
2014-02-11 14:49 ` Stefan Priebe - Profihost AG
2014-02-07 9:59 ` Marcin Gibuła
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F3961C.3000807@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=aderumier@odiso.com \
--cc=pve-devel@pve.proxmox.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).