I'm seeing this any time vmbuilder fails. If it fails more than a few times, I run out of loopback devices and can't build anything more. Here are the loopback devices it leaves for a VM with two hard disks:
I'm able to clean up the loopback devices manually, but it's quite a pain: aaron.smith@asmith ~/dvp/vm % sudo losetup -a /dev/loop0: [0801]:678634 (/tmp/tmpZjs7XP) /dev/loop1: [0801]:678638 (/tmp/tmpFfS6q9) aaron.smith@asmith ~/dvp/vm % sudo losetup -d /dev/loop0 loop: can't delete device /dev/loop0: Device or resource busy aaron.smith@asmith ~/dvp/vm % sudo kpartx -d /dev/loop0 aaron.smith@asmith ~/dvp/vm % sudo losetup -d /dev/loop0 aaron.smith@asmith ~/dvp/vm % sudo losetup -a /dev/loop1: [0801]:678638 (/tmp/tmpFfS6q9) -- OK, one down. The last one is a litte more painful: aaron.smith@asmith ~/dvp/vm % sudo dmsetup table loop1p1: 0 15622984 linear 7:1 63 aaron.smith@asmith ~/dvp/vm % sudo kpartx -dv /dev/mapper/loop1p1 aaron.smith@asmith ~/dvp/vm % sudo losetup -d /dev/mapper/loop1p1 aaron.smith@asmith ~/dvp/vm % sudo losetup -a aaron.smith@asmith ~/dvp/vm % If a person is trying to automate creation of a VM in a build process, this becomes burdensome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/583530 Title: vm-builder 0.12.3-0ubuntu1 crashes and causes loop devices to be stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/583530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
