Here's the sequence of events. Provision LVM for a VM. This creates a DM device. It has a certain size. Boot the VM on it.
Later on, customers wants more space. We expand the logical volume with LVM, which does some cleverness with the DM device to cause it to grow bigger. This is pretty much plain-jane LVM up to this point.
When we check the size of the block device from outside the VM, it shows the new size. From within, it shows the old, smaller size. In the olden days, you could do "xm block-configure ...." to cause the VM to pick up the changes. That hasn't worked for me for ages (and digging in the code turned up some interesting comments indicating that it may have not been re-implemented during a rewrite).
On Apr 13, 2008, at 8:58 AM, Mark Williamson wrote:
Our business currently provides literally thousands of VMs withfilesystems via blkback / blkfront.
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel