That _is_ what I did!

Hmm. Makes it an external process to track VM lineage without that data.

So use the thin-provision only to allow this tracking. And this works with windows VMs? will test shortly.

On Sun, Dec 9, 2012 at 12:41 PM, Itamar Heim <iheim@redhat.com> wrote:
On 12/09/2012 07:28 PM, Jim Kinney wrote:
Greetings,

I've built several new templates from the blank template and a ISO
install of various OS's. However, when I built a new VM using the new
template(s), the new VM still says it's based from the blank template. I
expected it to say it was from the "template-foo" U specified. The VM is
correctly built from the template so I think it's a generation/database
issue.


I'm guessing you used 'clone' (default for new server) rather than 'thinly provisioned' (default for new desktop).
clone means the template disk is copied/cloned for better performance, rather than COW (less space).
when the disk is cloned, there is no longer a relation to the original template at storage level.


--
--
James P. Kinney III
////
////Every time you stop a school, you will have to build a jail. What

you gain at one end you lose at the other. It's like feeding a dog on
his own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain
////
http://electjimkinney.org
http://heretothereideas.blogspot.com/
////


_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users






--
--
James P. Kinney III

Every time you stop a school, you will have to build a jail. What you gain at one end you lose at the other. It's like feeding a dog on his own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain

http://electjimkinney.org
http://heretothereideas.blogspot.com/