Public bug reported: I am using version 0.12.4+bzr462-0ubuntu1 in Ubuntu Natty. I've noticed that when I build a lucid virtual machine, it complains during boot.
During build, I see this in the build log: 2011-02-28 15:36:01,700 INFO : Adding type 3 partition to disk image: /tmp/tmpnFjJJ2 2011-02-28 15:36:01,707 INFO : [0] ../../libparted/filesys.c:148 (ped_file_system_type_get): File system alias linux-swap(new) is deprecated 2011-02-28 15:36:01,713 INFO : Creating loop devices corresponding to the created partitions 2011-02-28 15:36:01,721 INFO : Creating file systems 2011-02-28 15:36:01,833 INFO : mke2fs 1.41.14 (22-Dec-2010) 2011-02-28 15:36:14,592 INFO : mkswap: /dev/mapper/loop0p2: warning: don't erase bootbits sectors 2011-02-28 15:36:14,592 INFO : on whole disk. Use -f to force. At the end of the build log, there is a traceback: 2011-02-28 15:39:44,643 INFO : Unmounting tmpfs from /tmp/tmp1TErm0tmpfs 2011-02-28 15:39:44,650 INFO : umount: /tmp/tmp1TErm0tmpfs: device is busy. 2011-02-28 15:39:44,650 INFO : (In some cases useful info about processes that use 2011-02-28 15:39:44,650 INFO : the device is found by lsof(8) or fuser(1)) Traceback (most recent call last): File "/usr/bin/vmbuilder", line 24, in <module> cli.main() File "/usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py", line 239, in main util.clean_up_tmpfs(tmpfs_mount_point) File "/usr/lib/python2.7/dist-packages/VMBuilder/util.py", line 199, in clean_up_tmpfs run_cmd(*umount_cmd) File "/usr/lib/python2.7/dist-packages/VMBuilder/util.py", line 120, in run_cmd raise VMBuilderException, "Process (%s) returned %d. stdout: %s, stderr: %s" % (args.__repr__(), status, mystdout.buf, mystderr.buf) VMBuilder.exception.VMBuilderException: Process (['umount', '-t', 'tmpfs', '/tmp/tmp1TErm0tmpfs']) returned 1. stdout: , stderr: umount: /tmp/tmp1TErm0tmpfs: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) None of this happens when I do not specify a swap partition. This also doesn't happen when I build a hardy machine (I've only tried hardy and lucid as targets) Once you boot the machine, you will see this message: The disk drive for /dev/sda2 is not ready yet or not present Continue to wait; or Press S to skip mounting or M for manual recovery Let me know if you need any further information! ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. https://bugs.launchpad.net/bugs/726790 Title: python-vm-builder-0.12.4+bzr462-0ubuntu1: swap partitions fail to be created properly when "lucid" is the target -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs