After OpenNebula 6.6, qcow2 are referencing the original image and not cloned

Product Support Operations
1

Hi,

After I upgraded from 6.0 to 6.6, the qcow2 images show a different behavior.
While with 6.0 the qcow2 image would be fully cloned to the system ds, now it seems to reference the original image and only differences are stored in system ds.
How can I configure 6.6 to work the same as 6.0?

Thanks

2

I had a look into the shared tm and can see that it uses the “create” command, and that will always create a qcow2 with the original image as backing file.
If I change the clone tm script to use “convert” instead, it will do as I want.
Clone.ssh also seems to use convert, but I’m unsure how to make the shared tm use clone.ssh instead of clone.
From the original clone tm scripts I cant see any code flow that would not create the disk with a backing file, when format is qcow2.

So, to make the question more clear:

  • how to setup the system so that shared tm will not create the qcow2 using a backing file, but fully copy the image to the ds?

Thanks

3

Maybe it’s the QCOW2_STANDALONE option?

But I found that it’s implemented only in 6.8 and not 6.6.

I found it, it was solved in 6.6.2 enterprise edition.

4

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.