From: "Marcin Gibuła" <m.gibula@beyond.pl>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Alexandre DERUMIER <aderumier@odiso.com>
Subject: Re: [Qemu-devel] [pve-devel] QEMU LIve Migration - swap_free: Bad swap file entry
Date: Fri, 07 Feb 2014 10:59:19 +0100 [thread overview]
Message-ID: <52F4AE77.70506@beyond.pl> (raw)
In-Reply-To: <20140207093159.GD2374@work-vm>
>> 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 obviously this would only be of any use if run on the VM that actually
> fails.
Hi,
Seeing similar issue in my company I would be happy to run such tests.
Do you have any test suite I could run or some leads how to write it?
--
mg
prev parent reply other threads:[~2014-02-07 9:59 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
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 [this message]
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=52F4AE77.70506@beyond.pl \
--to=m.gibula@beyond.pl \
--cc=aderumier@odiso.com \
--cc=dgilbert@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.