search for: libguestfs_version_numbers

libguestfs 1.12 will be the next stable release of libguestfs, following the usual version numbering scheme: http://libguestfs.org/guestfs.3.html#libguestfs_version_numbers In order to coincide with the Fedora 16 schedule, I'd like to make the 1.12.0 release on or around 2011-07-20. The Fedora 16 branch date is 2011-07-26. Why might you care? (1) RHEL 6.3: *If* we were going to rebase libguestfs for RHEL 6.3 [we're not sure yet], then we'd likely want...

...ch around the end of this month (Oct'11) (3) Put this new stable version into Fedora 16 after 16 is released. https://fedoraproject.org/wiki/Releases/16/Schedule (4) Test, test, test. Backport bugfixes into 1.14.x branch as per the usual plan. http://libguestfs.org/guestfs.3.html#libguestfs_version_numbers (5) Put 1.14.x into RHEL 6.3 (around 1Q 2012). Comments? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.r...

...ment on the mailing list." For commits to the stable branch: "Any committer who wants to make a new stable release may cherry pick patches from the development branch on to the stable branch, in accordance with the stable branch policy here: http://libguestfs.org/guestfs.3.html#libguestfs_version_numbers Posting the rebased patches on the mailing list and ACK-ing patches is NOT required." (2) Hosting of the main website. Current status: http://libguestfs.org is hosted on a semi-official Red Hat-sponsored server. We use ~ 1.4 GB of disk space on this server, and some unknown but small a...

As you might have seen for the past 3 days I've been tackling a nasty data corruption bug[1][2]. The bug occurs when ALL of the following conditions are true: (a) You are using a qcow2 image file. (b) You are writing out data to the image file using libguestfs or a libguestfs-using tool like guestfish or virt-resize. (c) The data is not being written to a filesystem (to files or

This change renames the following 2 apis: * mdadm_create -> md_create * mdadm_detail -> md_detail This is more consistent with list_md_devices, and removes a reference to an implementation detail from the api. --- daemon/md.c | 24 ++++++++++++------------ generator/generator_actions.ml | 4 ++-- regressions/test-list-filesystems.sh | 2 +-