[Qemu-devel] [Bug 524447] Re: virsh save is very slow

[Jeff Snider]

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, [security vulnerabilities, severe regressions, or loss
of user data] but (1) have an obviously safe patch and (2) affect an
application rather than critical infrastructure packages (like X.org or
the kernel)."

I submit that this is an "obviously safe patch."  The change is small,
simple, isolated, has been tested to work, and doesn't change any
interfaces.  Is qemu-kvm considered a "critical infrastructure package"
or not?  I don't know the answer to that, but I can see valid arguments
both for and against.

I also have an example of a potential data loss situation, though it is
admittedly somewhat weak.  I'll spare everyone the narrative but I'll
share it if it would be helpful.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/524447

Title:
  virsh save is very slow

Status in libvirt virtualization API:
  Unknown
Status in QEMU:
  Fix Released
Status in “libvirt” package in Ubuntu:
  Invalid
Status in “qemu-kvm” package in Ubuntu:
  Fix Released
Status in “libvirt” source package in Lucid:
  Won't Fix
Status in “qemu-kvm” source package in Lucid:
  Won't Fix
Status in “libvirt” source package in Maverick:
  Won't Fix
Status in “qemu-kvm” source package in Maverick:
  Won't Fix

Bug description:
  ==================================
  SRU Justification:
  1. impact: 'qemu save' is slow
  2. how addressed: a patch upstream fixes the case when a file does not 
announce when it is ready.
  3. patch: see the patch in linked bzr trees
  4. TEST CASE: see comment #4 for a specific recipe
  5. regression potential:  this patch only touches the vm save path.
  ==================================

  As reported here: http://www.redhat.com/archives/libvir-
  list/2009-December/msg00203.html

  "virsh save" is very slow - it writes the image at around 1MB/sec on
  my test system.

  (I think I saw a bug report for this issue on Fedora's bugzilla, but I
  can't find it now...)

  Confirmed under Karmic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/524447/+subscriptions