Dan Smith wrote:
DB> Which would result in $pool-target-dir/$vol-name. This works fine DB> if you only need to be able to create the top level directory for DB> the container filesystem.
Seems reasonable to me.
DB> I really rather want to avoid turning libvirt into a general file DB> management API.
Agreed.
DB> Perhaps simply the ability to 'clone' an existing directory DB> (populated from source external soure, or off NFS) would be DB> sufficient for populating containers ?
Sounds reasonable to me. :)
So, if I understand correctly, the user would specify a directory containing an image of the entire file system they want for the container. This would be clone'd and setup so that it appears as / in the container filesystem?
Maybe Dave L. can chime in here with any thoughts he may have?
------------------------------------------------------------------------
-- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
-- Best Regards, Dave Leskovec IBM Linux Technology Center Open Virtualization