From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jim Fehlig <jfehlig@novell.com>
Cc: LibVir <libvir-list@redhat.com>, Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [libvirt] speeding up qemu core dumps
Date: Thu, 4 Aug 2011 09:07:43 +0100 [thread overview]
Message-ID: <20110804080743.GA14075@redhat.com> (raw)
In-Reply-To: <4E3A151F.1040205@novell.com>
On Wed, Aug 03, 2011 at 09:42:23PM -0600, Jim Fehlig wrote:
> Eric Blake wrote:
> > On 08/03/2011 08:37 AM, Jim Fehlig wrote:
> >> http://lists.nongnu.org/archive/html/qemu-devel/2011-02/msg01156.html
> >>
> >> I thought there were more discussions on the topic but can only find the
> >> above thread ATM.
> >>
> >> Do folks here have objections to increasing the migration speed prior to
> >> core dump? If not, any suggestions for a value? I set the migration
> >> speed to 1G in doCoreDump() prior to calling qemuMigrationToFile() with
> >> following improvement dumping a 4G guest
> >
> > Why any limit at all? When dumping to file rather than network, I
> > can't think of any justification for a default limit when targetting a
> > local drive (a particular installation may have a reasonable limit,
> > especially if the file involved happens to use a network - think
> > NFS). It seems like it would make sense to override the qemu defaults
> > and go with unlimited speed for faster dump and save operations.
>
> Agreed, 1G was just a test value, but I'm haven't yet figured out how to
> define unlimited. From libvirt json monitor connection I tried
> migrate_set_speed with INT64_MAX, but that was invalid. Using qemu
> monitor directly, I can go as high as INT64_MAX-512
>
> (qemu) migrate_set_speed 9223372036854775295B
> (qemu) migrate_set_speed 9223372036854775296B
> invalid size
>
> Any hints on proper way to set unlimited migration speed?
The code doesn't seem to have a way to set a truely unlimited rate,
but even INT64_MAX / 2 would be more than sufficient for us to max
out the host OS storage throughput
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2011-08-04 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E395D19.4050302@novell.com>
[not found] ` <4E3960EF.60603@redhat.com>
2011-08-04 3:42 ` [Qemu-devel] [libvirt] speeding up qemu core dumps Jim Fehlig
2011-08-04 8:07 ` Daniel P. Berrange [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=20110804080743.GA14075@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jfehlig@novell.com \
--cc=libvir-list@redhat.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).