From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"pve-devel@pve.proxmox.com" <pve-devel@pve.proxmox.com>
Subject: Re: [Qemu-devel] QEMU LIve Migration - swap_free: Bad swap file entry
Date: Wed, 5 Feb 2014 20:15:02 +0000 [thread overview]
Message-ID: <20140205201501.GL2398@work-vm> (raw)
In-Reply-To: <52F27A13.7090003@profihost.ag>
* Stefan Priebe (s.priebe@profihost.ag) wrote:
> 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?
I don't, but some more information about:
1) What guest you're running
2) The configuration of your hosts
3) The command line (or XML if you're running libvirt) for
your qemu so we can see what devices you're running.
would probably help people.
Do you get any messages on either the source or destination
qemu during the migrate?
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-02-05 20:40 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 [this message]
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
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=20140205201501.GL2398@work-vm \
--to=dgilbert@redhat.com \
--cc=pve-devel@pve.proxmox.com \
--cc=qemu-devel@nongnu.org \
--cc=s.priebe@profihost.ag \
/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).