Bug 564462 - cloning sparsed image guests with virt-manager produces preallocated guest image
Summary: cloning sparsed image guests with virt-manager produces preallocated guest image
Keywords:
Status: CLOSED DUPLICATE of bug 522720
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-12 20:10 UTC by Joachim Schröder
Modified: 2010-09-28 03:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-01 16:18:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Joachim Schröder 2010-02-12 20:10:48 UTC
Description of problem:
cloning a virtual guest using a sparse image as virtual disk with virt-manager produces a preallocated image.

Version-Release number of selected component (if applicable):


How reproducible:
use virt-manager to clone a virt guest that is using a sparse image.

Actual results:
the cloned image is preallocated.

Expected results:
the cloned image is a sparse image.

Additional info:

Comment 1 Paul Jenner 2010-02-27 21:51:55 UTC
Should this be rolled into a duplicate of bug #522720 ?

Comment 2 Cole Robinson 2010-03-01 04:13:24 UTC
Paul, I haven't seen a dup recommendation from you that I haven't liked :) Please feel free to just dup the bugs, someone will undo if they disagree.

Closing as a dup of 522720

*** This bug has been marked as a duplicate of bug 522720 ***

Comment 3 Joachim Schröder 2010-03-01 08:47:17 UTC
Reopening; please see comment #11 https://bugzilla.redhat.com/show_bug.cgi?id=522720#c11 where I have explicitely been asked to open a new bug for libvirt.
Closing this as a dup now would be unproductive ;-)
jos

Comment 4 Cole Robinson 2010-03-01 16:18:02 UTC
Joachim, sorry about the confusion. I actually reassigned that original bug to libvirt with the intent of using it to track the issue I asked you to file in comment #11. I think it's better if we just stick to the original report where there is already a lot of info reported. Thanks for following up though.

Re-duping to 522720

*** This bug has been marked as a duplicate of bug 522720 ***


Note You need to log in before you can comment on or make changes to this bug.