Nick Moffitt wrote:
Alas, I am now faced with a more revealing error:
http://dpaste.com/hold/119347/
Looking through storage_conf.c and storage_backend_logical.c, I believe
that my XML matches the XPath used on line 1005 of storage_conf.c:
char *format =
Daniel P. Berrange:
http://libvirt.org/formatstorage.html#StorageVolBacking
This is currently support for Cow, QCow, QCow2, VMDK and LVM storage
types. Some of these allow for the underling backing store to be
writable, others require that its readonly.
I tried the following under libvirt
Further sanity checking:
# lvcreate --size 2G --snapshot --name lol /dev/VMs/test-disk
# dmsetup ls --target snapshot
VMs-lol (254, 2)
--
Though the great song return no more Nick Moffitt
There's keen delight in what we have:
Alas, I am now faced with a more revealing error:
http://dpaste.com/hold/119347/
Looking through storage_conf.c and storage_backend_logical.c, I believe
that my XML matches the XPath used on line 1005 of storage_conf.c:
char *format = virXPathString(conn,
On Mon, Feb 09, 2009 at 10:03:19PM +, Nick Moffitt wrote:
I'm working on an existing system that creates, manages, and destroys
Xen guests on a pool of host systems, and I use LVM copy-on-write
snapshots to keep creation rapid.
http://libvirt.org/storage.html describes logical volume
I'm working on an existing system that creates, manages, and destroys
Xen guests on a pool of host systems, and I use LVM copy-on-write
snapshots to keep creation rapid.
http://libvirt.org/storage.html describes logical volume pools, for
which you simply supply the name of a volume group and it
