I can confirm this bug too, using vmbuilder 0.12.4 on an up to date lucid. Vmbuilder complete guest creation without an error. But launching the guest with the mapping cause immediate fs corruption. This has nothing to do with the lv size. Simon have done all the investigation correctly but I don't how to fix that. The only solution is to not forget to remove this mapping before launchping the guest. I would appreciate if this could be fixed. Regards
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/531599 Title: device mappings for partitions not removed after build using --raw, leading to filesystem corruption -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs