This week I managed to get most of the work on the libvirt xenlight driver done.
There is some kind of problem on the xen llibxl, developers are not
very sure about how exactly it should be done and me and my mentor
realized it may take longer to get the work acked in libxl.I worked
around that by patching xen to provide some imaginary API.This API
should be what will be provided when the xen libxl work gets acked.
The libvirt work is now almost complete(considering the imaginary API)
and I will push it to github over the weekend(
).The patch will have to
wait for the xen libxl work to get acked so that it can be pushed to
We then agreed with my mentor that over the coming period I will work
on something else. This will be a parser for changing the xl
configuration format to libvirt XML and vice versa.
On Sun, Jun 8, 2014 at 10:15 PM, David kiarie <davidkiarie4(a)gmail.com> wrote:
Let me not start another thread because I don't have much to report.
This week I finished working on the above functions and I few other
Next week I will hopefully take on the actual snapshot functions and
finally the beast domainSnapshotCreateXML
On Sat, May 31, 2014 at 8:20 AM, David kiarie <davidkiarie4(a)gmail.com> wrote:
> Hi there,
> This week I worked on helper functions which are needed by the major
> functions(API) which I am supposed to implement.This included
> This function should be called each time a snapshot is taken to update
> libvirt xml metadata to track the snapshot.
> This function should be called on various occasions e.g to update the
> current domain xml config after taking or deleting a snapshot.
> This function is a wrapper function around xen libxl's disk_snapshot
> function.I takes care of all the disks on a domain.This is what should
> be called when taking the internal snapshot of an inactive domain.
> This function takes a snapshot and returns a snapshot obj
> representation.The difference between the two being that the "snapshot
> obj" structure has more information.
> Also because I am following the libvirt qemu driver(which I this has a
> lot of boiler plate code anyway) I was thinking about having functions
> to prepare the disks for snapshots.Here I am taking of checking the
> user commands for errors and maybe some operations which are not
> All in all, I will continue working on this and should be done next week.
> *Ahem*,..sorry for writing sooo much detail.I just don't know how else
> to explain this.
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org