From: Orit Wasserman <owasserm@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
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: Thu, 06 Feb 2014 12:22:09 +0200 [thread overview]
Message-ID: <52F36251.7070806@redhat.com> (raw)
In-Reply-To: <52F337BF.4090509@profihost.ag>
On 02/06/2014 09:20 AM, Stefan Priebe - Profihost AG wrote:
> Am 05.02.2014 21:15, schrieb Dr. David Alan Gilbert:
>> * 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
>>>
Is this live migration with shared storage? what kind of shared storage?
Does this happens with smaller guests?
>>> Qemu is 1.7
>>>
>>> Does anybody know a fix?
>>
>> I don't, but some more information about:
>> 1) What guest you're running
>
> Linux guest the output is also from the guest. Kernel 3.10.26
>
>> 2) The configuration of your hosts
>
> What do you mean by that?
>
>> 3) The command line (or XML if you're running libvirt) for
>> your qemu so we can see what devices you're running.
>
> qemu -chardev
> socket,id=qmp,path=/var/run/qemu-server/179.qmp,server,nowait -mon
> chardev=qmp,mode=control -vnc
> unix:/var/run/qemu-server/179.vnc,x509,password -pidfile
> /var/run/qemu-server/179.pid -daemonize -name K31953 -smp
> sockets=1,cores=16 -nodefaults -boot
> menu=on,strict=on,reboot-timeout=1000 -vga cirrus -cpu
> kvm64,+lahf_lm,+x2apic,+sep -k de -m 32768 -device
> piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device
> usb-tablet,id=tablet,bus=uhci.0,port=1 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -drive
> if=none,id=drive-ide2,media=cdrom,aio=native -device
> ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -device
> virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive
> file=rbd:...,if=none,id=drive-scsi0,iops_rd=1000,iops_wr=500,bps_rd=314572800,bps_wr=209715200,aio=native,discard=on
> -device
> scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100
> -netdev
> type=tap,id=net0,ifname=tap179i0,script=/var/lib/qemu-server/pve-bridge,vhost=on
> -device
> virtio-net-pci,mac=CA:CA:23:AC:2D:C5,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
> -rtc base=localtime -machine type=pc-i440fx-1.7
>
>> Do you get any messages on either the source or destination
>> qemu during the migrate?
>
> no
>
> Stefan
>
next prev parent reply other threads:[~2014-02-06 10:21 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 [this message]
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=52F36251.7070806@redhat.com \
--to=owasserm@redhat.com \
--cc=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).