** Changed in: qemu-kvm (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh save is very slow
To manage
I see activity around this bug is going on and on, but I don't understand -- is
the talk about this patch --
http://anonscm.debian.org/gitweb/?p=collab-maint/qemu-kvm.git;a=commit;h=7e32b4ca0ea280a2e8f4d9ace1a15d5e633d9a95
?
--
You received this bug notification because you are a member of
Michael: Yes, that is the correct patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh save is very slow
To manage notifications about this bug go to:
I just wanted to point out that we've this patch in Debian since ages,
and it's been included in upstream for a long time too. Added a debbug
reference for this as well.
** Bug watch added: Debian Bug tracker #597517
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597517
** Also affects:
I'm sorry, the lucid qemu-kvm update has been superseded by a security
update in 0.12.3+noroms-0ubuntu9.15.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh save
I'm sorry - per the rules listed in
https://wiki.ubuntu.com/StableReleaseUpdates, only bugs which are =
high priority are eligible for SRU. If you feel this bug should be high
priority, please say so (with rationale) here.
An updated package for lucid through natty will be placed in the ubuntu-
The page you referenced doesn't include anything that I can find about
the ticket priority level. It states that Stable release updates will,
in general, only be issued in order to fix high-impact bugs and
provides several examples. Among them is Bugs which do not fit under
above categories,
Serge - why do you think this can't be SRU'd? It's already been
accepted into lucid-proposed once, then verified, and the only reason
it's not in lucid-updates is that it got superseded by a security upload
before the 7-day testing period had elapsed.
If you made a new upload to lucid-proposed
Jeff thanks for the testing!
I'll take that as verification.. marking verification-done. It just
needs to wait 7 days to clear -proposed in case it causes any unintended
regressions.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
Hello Chris, or anyone else affected,
Accepted qemu-kvm into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
Tested 0.12.3+noroms-0ubuntu9.14 on Lucid amd64 with all available
updates. Save speed is now approx 3 seconds for a 256Mb guest. Tested
virsh with start, stop, save, restore, suspend, resume, shutdown,
destroy. Tested guest with smp, virtio disk, virtio net, vnc display.
Everything worked as
I'd like to help get this fixed, particularly in Lucid. What can I do?
Does #21 and #22 still need testing?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh
@Jeff,
they do still need testing. However at this point new ones need to be
generated. There is a bit of a backlog on libvirt updates to push.
Depending on how those go, I could get packages into -proposed either
next week or in 2-3 weeks.
I'll make a note to queue this, and ping here when
Oops, this is for qemu-kvm, not libvirt. That can go immediately.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh save is very slow
To manage notifications
(setting importance to medium because it has a moderate impact on a core
application, and especially because it has no workaround)
** Changed in: qemu-kvm (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: qemu-kvm (Ubuntu Maverick)
Importance: Undecided = Medium
--
You
Ok, great! Thanks for the quick response. I did just now get finished
testing the packages you attached in #21 using my lucid box. Saves of a
256Mb guest went from ~50 seconds to ~3. So it does seem to fix the
issue. I can set up a Maverick box if you need it tested there as well.
I checked
Actually maverick is waiting for a fix for bug 790145 to be verified,
but lucid is free. I've uploaded the proposed fix to lucid-proposed,
it's waiting for an SRU admin to approve it. I will also post the amd64
lucid .debs at http://people.canonical.com/~serge/qemu-slow-save/.
--
You received
Using ubuntu natty narwhal installed today (2011-03-24) I tried to do a
snapshot with the help of libvirt. Here are the results using natty
version of qemu-kvm and libvirt and using presented slowdown packages.
root@koberec:~# time virsh snapshot-create 1
Domain snapshot 1300968929 created
real
Thanks for that info. That is unexpected. Could you send the xml
description of the domain you were snapshotting, as well as the format
of the backing file (i.e. qemu-img info filename.img) and what
filesystem it is stored on (or whether it is LVM)? I'd like to try to
reproduce it.
Since you
To be clear, please re-install the stock natty packages, do a virsh
snapshot-create, and then do 'ubuntu-bug libvirt-bin' to file a new bug.
Then please give the info I asked for in comment 25 in that bug.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server
In reply to question #26
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/741887
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh save is very slow
--
In reply to question #25: everything is included in #27. Is it enough?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh save is very slow
--
Ubuntu-server-bugs
Yes, thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh save is very slow
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify
** Branch linked: lp:~serge-hallyn/ubuntu/maverick/qemu-kvm/slowsave
** Branch linked: lp:~serge-hallyn/ubuntu/lucid/qemu-kvm/slowsave
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
** Attachment added: amd64 .debs for lucid
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/524447/+attachment/1908989/+files/slowsave-lucid-debs.tgz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
In order to proceed with SRU, we need someone to confirm that the debs
in comment #21 or #22 work for them.
** Description changed:
+ ==
+ SRU Justification:
+ 1. impact: 'qemu save' is slow
+ 2. how addressed: a patch upstream fixes the case when a file does not
Hi,
please test the qemu-kvm packages in ppa:serge-hallyn/virt for lucid
(0.12.3+noroms-0ubuntu10slowsave2) and maverick (0.12.5+noroms-
0ubuntu7slowsave2), which have the proposed patch from upstream. If
they succeed, then I will proceed with the SRU.
--
You received this bug notification
The patch is in 0.13.0, so changing the status.
** Changed in: qemu
Status: Invalid = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh save
How should I interpret Fix Released?
qemu in maverick is still 0.12.5 and 0.12.3 in lucid.
Will this not be fixed in current stable LTS and non-LTS releases?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
Michael Tokarev m...@tls.msk.ru writes:
03.01.2011 16:23, EsbenHaabendal wrote:
How should I interpret Fix Released?
qemu in maverick is still 0.12.5 and 0.12.3 in lucid.
Not all the world is ubuntu. In qemu (and qemu-kvm) the
issue is fixed in 0.13, which were released quite some
time
Will a fix for this go into maverick?
This is quite critical for using kvm/libvirt for virtual server hosting
on maverick.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/524447
Frederick,
please let me know if you can confirm that this patch fixes it for you. If you
need
me to set up a ppa with that patch, please let me know.
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Server
@earl,
thanks for finding the specific patch!
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Frederic, this patch:
http://www.mail-archive.com/qemu-de...@nongnu.org/msg37743.html
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Iggy, which patch exactly? I don't seem to be able to find it.
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
You may want to try the patch to qemu that avi just posted to the qemu-
devel mailing list. I think this would probably fix your issue.
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Just a note that the 0.8.1 release available in maverick gives me about
a 50-second save for a 512M memory image (producing 100M outfile). The
patch listed above and suspected of speeding the saves is not in 0.8.1.
When I hand-apply just that patch, saves take about 8 seconds, but
restore fails.
Do you have a link for the qemu-devel thread? I had a look at
http://lists.gnu.org/archive/html/qemu-devel/ but couldn't see anything.
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Changing to libvirt as commentary here, and on the upstream bug report
by Cole indicate a fix has been commit that improves this performance.
** Package changed: qemu-kvm (Ubuntu) = libvirt (Ubuntu)
** Also affects: libvirt via
https://bugzilla.redhat.com/show_bug.cgi?id=599091
Importance:
Re-introducing qemu-kvm, as commentary on qemu-devel mailing list
suggest there could be a timing concern meaning poor performance.
Leaving Libvirt on this report, as upstream libvirt have quoted improved
performance adjusting the block size for dd. However, Qemu feel that
the real issue is in
I can reproduce with:
x86_64-softmmu/qemu-system-x86_64 -hda ~/images/linux.img -snapshot -m 4G
-monitor stdio -enable-kvm
QEMU 0.12.50 monitor - type 'help' for more information
(qemu) migrate_set_speed 1G
(qemu) migrate -d exec:dd of=foo.img
On:
commit
This actually turns out to be related to dd's default block size. By
default, dd uses a block size of 512. The effect of this is that qemu
fills the pipe buffer very quickly because dd just is submitting very
small requests (that will require a RMW).
If you set an explict block size with dd
I filed an upstream libvirt bug for the dd block size issue:
https://bugzilla.redhat.com/show_bug.cgi?id=599091
** Bug watch added: Red Hat Bugzilla #599091
https://bugzilla.redhat.com/show_bug.cgi?id=599091
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this
This stops me migrating away from VMware Server to KVM/libvirt. I use
suspend (to disk) for backup an when shutting down the host. It would
need nearly an hour to save all domains on our server. Why are there so
few responses here an in the qemu-Mailinglist? Does nobody care?
--
virsh save is
Anthony-
Any upstream update here? Looks like this issue has been reported on
the qemu-de...@mailing list. Curious if or when we might expect a fix
for this?
Thanks!
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided =
I'm marking confirmed, since there's external references to this
situation happening.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Server
** Package changed: libvirt (Ubuntu) = qemu-kvm (Ubuntu)
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
47 matches
Mail list logo
