** Changed in: qemu
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741887
Title:
virsh snapshot-create too slow (kvm, qcow2, savevm)
To manage notifications about thi
Cool. Writes about 9 times the data of the actual snapshot size.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741887
Title:
virsh snapshot-create too slow (kvm, qcow2, savevm)
To manage notificati
@edison,
if you want to push such a patch, please do it through upstream, since
it is actually a new feature.
I'm going to mark this 'wontfix' (as I thought I had done before),
rather than invalid, though the latter still sounds accurate as well.
** Changed in: qemu-kvm (Ubuntu)
Status: C
I had posted a patch to fix the issue
before:(http://patchwork.ozlabs.org/patch/64346/), saving memory state
is time consuming, which may takes several minutes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
In qemu 0.14 cache=writeback and cache=none are expected to perform
well. The default cache=writethrough is a very conservative setting
which is slow by design. I'm pretty sure that it has always been slow,
even before 0.12.5.
I think that the specific problem with savevm may be related to the VM
I confirm that without 'cache' option, I have got from iostat those
result while doing 'savevm'
Device: sda
rrqm/s: 0.00
wrqm/s: 316.00
r/s: 0.00
w/s: 94.80
rkB/s: 0.00
wkB/s: 1541.60
avgrq-sz: 32.52
avgqu-sz: 0.98
await: 10.32
svctm: 10.10
%util: 95.76
I also confirm, that when option 'cache=uns
Confirmed that doing
kvm -drive file=lucid.img,cache=unsafe,index=0,boot=on -m 512M -smp 2 -vnc :1
-monitor stdio
and doing 'savevm savevm5'
takes about 2 seconds.
So, for fast savevm, 'cache=unsafe' is the workaround. Shoudl this bug
then be marked invalid, or 'wontfix'?
--
You received
savevm _is_ slow, because it's writing to a qcow2 file with full
(meta)data allocation which is terrible slow since 0.13 (and 0.12.5)
unless you use cache=unsafe. It's the same slowdown as observed with
default cache mode when performing an operating system install into a
freshly created qcow2 - i
The current upstream qemu.git from git://git.savannah.nongnu.org/qemu.git
also has the slow savevm. However, it's loadvm takes only a few seconds.
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Yup, I can definately reproduce this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741887
Title:
virsh snapshot-create too slow (kvm, qcow2, savevm)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Package changed: libvirt (Ubuntu) => qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment added: "used virsh domain XML definition"
https://bugs.launchpad.net/bugs/741887/+attachment/1937063/+files/vm.xml
** Description changed:
Action
==
# time virsh snapshot-create 1
* Taking snapshot of a running KVM virtual machine
Result
==
Domain snap
12 matches
Mail list logo
