[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1025244
Title:
qcow2
Looking through old bug tickets... is there anything left to do here? Or
should we rather close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are
@Mario,
the external snapshots have apparently been around a long time. The
ability to create external snapshots from running vms is newer, but
it appears to exist evn in qemu-kvm 1.0. So all versions in Debian
and Ubuntu should support them.
@Mario, in theory an image that should be taking up 30 GB with four
snapshots should be taking up at most about 150 GB, of course. Now the
question is what you mean by should be taking up 30 GB and by is
taking 600+ GB.
For the latter, did you query the file length (ls -l) or the actual size
@serge, what version would I need to upgrade to be able to use the
external snapshots? that sounds like it would solve my problems
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1025244
Title:
Changing priority given workarounds.
** Changed in: qemu-kvm (Ubuntu)
Importance: High = Low
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1025244
Title:
qcow2 image increasing disk size above
@michael, so you do that once, after some time the machine keeps
growing, and growing and growing... and you have to redo that every so
often... I have a machine that should be taking up 30 gb yet is taking
600+ GB with 4 snapshots... but yeah... I'll just plug in another 1tb
hard drive so that i
For the record, the workaround is deleting old snapshots in shutdown mode
as per comment #14.
Upstream has moved toward external snapshots as the way forward, so while
I don't argue that this is a bug, it seems unlikely to receive a fix from
upstream.
--
You received this bug notification
Looking at what? At the lack of problems as comment #14 says?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1025244
Title:
qcow2 image increasing disk size above the virtual limit
Status in
Is anyone even looking at this? been years and the problem still
persists!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1025244
Title:
qcow2 image increasing disk size above the virtual limit
Thanks for your advices. I have no more problems with VM-size since
deleting snapshot in shutdown-mode. I reduced the overlarge qcow2-images
by converting in qcow2 again (that detects unused sectors and omits
this).
--
You received this bug notification because you are a member of qemu-
On Tue, Dec 18, 2012 at 10:18:20AM -, Andy Menzel wrote:
Any solution right now? I have a similar problem like Todor Andreev;
Our daily backup of some virtual machines (qcow2) looks like that:
1. shutdown the VM
2. create a snapshot via: qemu-img snapshot -c nameofsnapshot...
3. boot
On 01/02/2013 08:50 AM, Stefan Hajnoczi wrote:
On Tue, Dec 18, 2012 at 10:18:20AM -, Andy Menzel wrote:
Any solution right now? I have a similar problem like Todor Andreev;
Our daily backup of some virtual machines (qcow2) looks like that:
1. shutdown the VM
2. create a snapshot via:
I don't know of any qcow2-based workaround.
Is anyone actively working on fixing the qcow2 code? In particular, the
fact that after removing snapshots, un-used blocks are not reclaimed and
disk size is never reduced?
One possible workaround (the one I would use) would be to use lvm-based
Any solution right now? I have a similar problem like Todor Andreev;
Our daily backup of some virtual machines (qcow2) looks like that:
1. shutdown the VM
2. create a snapshot via: qemu-img snapshot -c nameofsnapshot...
3. boot the VM
4. backup the snapshot to another virtual disk via: qemu-img
@Todor,
Thanks, you might be right. It sounds like it's not a missing feature
but a bug. I'll re-raise the priority.
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu)
Importance: Low = High
--
You received this bug notification because you
17 matches
Mail list logo
