This looks like a good candidate :
https://bugs.launchpad.net/vmbuilder/+bug/966439
I tested the script and adding --removepkg=cron does fix this behavior
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
Hi all,
Same issue here, modifying dapper.py and util.py with '-l' as described
above by mattanja works fine for me.
--
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:
I also had the problem building a lucid image but the added sync line
did not help.
I added the -l option (lazy unmount) to both umount commands in
plugins/ubuntu/dapper.py and util.py and it worked and the devices got
unmounted.
util.py (starting in line 194):
def clean_up_tmpfs(mount_point):
I was having the same problem, while building maverick image.
Taco's fix worked, thanks.
--
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:
I was having the same problem, and Taco's fix worked for me too. Note I
needed to edit the dapper.py file even though I was creating a lucid VM.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
I was having the same issue and after adding Taco's sync line in the
dapper.py file everything worked smoothy. Thanks Taco!
--
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
Using version 0.12.4+bzr469-0ubuntu1 I also get the exception that the
device is busy. When I insert a run_cmd('sync') just before the umount
command it works OK and building finishes without the exception.
So, the /usr/lib/python2.7/dist-
packages/VMBuilder/plugins/ubuntu/dapper.py file
I have the same problem with vmbuilder 0.12.4.r466 (Ubuntu 11.10 amd64).
Here are the last lines of output for this command :
sudo vmbuilder kvm ubuntu --suite natty --flavour virtual --arch i386 -o
--iso=/home/isos/ubuntu-11.04-server-i386.iso --mirror
http://ftp.heanet.ie/pub/ubuntu --debug
I have the same problem using python-vm-builder 0.12.4+bzr469-0ubuntu1.
Only, I am not using a partitions file, but simply specify
--optsize=10240
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
** Changed in: vm-builder (Ubuntu)
Status: New = Confirmed
--
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
Hi Randy,
Thank you for reporting bugs and trying to make Ubuntu Server better!
Could you please provide a Step by step to be able to reproduce this
bug. Once we can reproduce this bug we'll investigate further and maybe
ask for more information.
I'm marking this bug as incomplete until the
I am attaching a build script that uses a partitions file to demonstrate
the issue. When you run this script, the traceback that I listed doesn't
occur (not sure why). However, the built machine does still complain
about /dev/sda2, and you can verify that it does not have swap.
** Attachment
I moved the ticket status back to New. I've actually been wondering,
is it appropriate for me to alter the ticket state back to new after I
provide the requested information, or would it have been better if I
left it at Incomplete?
--
You received this bug notification because you are a member
This is the partitions file that I used.
** Attachment added: partitions
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/726790/+attachment/1879354/+files/partitions
** Changed in: vm-builder (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because
Quoting Randy Barlow (726...@bugs.launchpad.net):
I moved the ticket status back to New. I've actually been wondering,
is it appropriate for me to alter the ticket state back to new after I
provide the requested information, or would it have been better if I
left it at Incomplete?
Thanks, yes
15 matches
Mail list logo
