Desing a basic interface for Disk images

[Daniele Lacamera]

Design a configuration window to manage disk images. There should be possible to attach an icon and a nickname to every disk image along with its path.

A disk image can be "base" or "derived"

All the image will reside in the same directory (Settings.Settings.base_images) or evnetually in subdirs. There should be not possible to move an image once it's been used as a base to derive another one.

If an image is derived it will have an additional parameter saying what is the absolute path to the base image. If the base is not accessible, it will not be possible to use/select the derived image.

If a disk image is derived from another one (which must be base) the base cannot be used any more, or either some read-only must be forced in order to keep a valid base for cow images.

To derive a disk image, use the qemu-img to make a cow. The derived image will inherit icon from the base.

There must be a dialog like in qemulator to create empty disk images.

disk images can be related to a VM (if attached as hda,hdb, ..., sda.. parameter) and shown in qemu config (maybe a combobox would be useful to select from "no image" to one of the images available in the image repository)

[Francesco Apollonio (lorddex)]

closed in r30

[Francesco Apollonio (lorddex)]

It's possible to create an empty disk image (or a base image) through the menu 'Image Creation'->'Create new Image' .

To create a derived image, the user have to select a base image for the VM selected (as it's a normal disk image) from the machine configuration and after check the 'Private COW' box.