vmbuilder team mailing list archive

[l8gravely <john@xxxxxxxxxxx>]

Hi,

Has the command line API (args, etc) completely changed in Lucid's
version of the vmbuilder tool?  I'm running Lucid Alpha on an x86_64
system and during the alpha 1 to alpha 2 or 3 updates, the following
broke badly:

vmbuilder kvm ubuntu --suite=${suite} --flavour=virtual --arch=amd64
--mirror=${mirror} -o --libvirt=qemu:///system --tmpfs=-
--ip="${subnet}.${ip}" --gateway="${subnet}.254"
--part=vmbuilder.partition --templates=mytemplates --user=${username}
--name=${username} --pass=${username} --addpkg=vim-nox --addpkg
=unattended-upgrades --addpkg=acpid --raw=/dev/virtmachs/${hostname}
--firstboot=boot.sh --mem=${mem} --hostname=${hostname}
--bridge=${bridge}

The -o switch is now complained about, along with the --tmpfs=- and
--firstboot=boot.sh args.  When I remove all and run my script, this is
what I get:

sail:~> vmbuilder kvm ubuntu --suite=karmic --flavour=virtual
--arch=amd64 --mirror=http://192.168.1.3:9999/ubuntu
--libvirt=qemu:///system --ip=192.168.1.54 --part=vmbuilder.partition
--templates=mytemplates --user=john --name=john --pass=john --addpkg
=vim-nox --addpkg=unattended-upgrades --addpkg=acpid
--raw=/dev/virtmachs/vm4 --mem=256 --hostname=vm4 --bridge=br0
2010-03-09 10:53:55,861 INFO    : Calling hook: preflight_check
2010-03-09 10:53:55,872 INFO    : Calling hook: set_defaults
2010-03-09 10:53:55,873 INFO    : Calling hook: bootstrap
Traceback (most recent call last):
  File "/usr/bin/vmbuilder", line 24, in <module>
    cli.main()
  File "/usr/lib/python2.6/dist-packages/VMBuilder/contrib/cli.py", line
99, in main
    distro.build_chroot()
  File "/usr/lib/python2.6/dist-packages/VMBuilder/distro.py", line 82,
in build_chroot
    self.call_hooks('bootstrap')
  File "/usr/lib/python2.6/dist-packages/VMBuilder/distro.py", line 66,
in call_hooks
    call_hooks(self, *args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/VMBuilder/util.py", line 165,
in call_hooks
    getattr(context, func, log_no_such_method)(*args, **kwargs)
  File "/usr/lib/python2.6/dist-
packages/VMBuilder/plugins/ubuntu/distro.py", line 142, in bootstrap
    self.suite.debootstrap()
  File "/usr/lib/python2.6/dist-
packages/VMBuilder/plugins/ubuntu/dapper.py", line 272, in debootstrap
    run_cmd(*cmd, **kwargs)
  File "/usr/lib/python2.6/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
(['/usr/sbin/debootstrap', '--arch=amd64', 'karmic', '/tmp/tmpSCGmm5',
'http://192.168.1.3:9999/ubuntu']) returned 1. stdout: E: debootstrap
can only run as root
, stderr:


Does anyone have a document listing the changes or upgrade process to be
used between Karmic and Lucid versions of vmbuilder?  I've been looking
around, but not having any success on this.

Thanks,
John
-- 
This message was sent from Launchpad by the user
l8gravely (https://launchpad.net/~john-stoffel)
using the "Contact this team" link on the VMBuilder team page.
For more information see
https://help.launchpad.net/YourAccount/ContactingPeople