On Mon, Dec 25, 2006 at 12:20:43AM +0100, Henning Sprang wrote: > The problem why it didn't stop was, it seems to only check if a given > lvm or disk already exists.
True. > It seems not to check, if the vm config file it is about to create > already exists and just overwrote an existing config. > While in this case I don't blame xen-tools for my own errors, I think > it's generally a important to check if a config file already exists, > and only overwrite it with --force. Fixed in CVS. > Also interesting: the config file was also written when the lvm volume > couldn't be created. It seemd like xen-tools doesn't realize if > there's an error in lvm creation (ganna add an extra bug for this). (Fixed that seperately.) Steve --
signature.asc
Description: Digital signature