vmbuilder sets new VMs' memory limits to 18446744073709551615 kb

[Owen Jacobson]

STR:

1. Install a stock vmbuilder package.
2. Create a ~/.vmbuilder.cfg with the following:
[DEFAULT]
mem = 256

# and other settings as appropriate
3. sudo vmbuilder kvm ubuntu --libvirt qemu:///system # no --mem
4. virsh dumpxml ubuntu | grep memory

If, and apparently only if, the value of mem came from ~/.vmbuilder.cfg, then the <memory /> element will contain 18446744073709551615. The number is identical regardless of the value used for mem in the config -- I've tested 128, 64, and 256, anyways.

This behaviour cannot be reproduced using the --mem flag, and if --mem
is specified, the presence or absence of a mem config file entry becomes
irrelevant (as it should).

It's probably relevant that this number is all-bits-1 for 64 bits, as an unsigned value.

Versions:
ii python-vm-builder 0.10-0ubuntu2

[Charles Hooper (chooper)]

Fixed in lp:~chooper/vmbuilder/fixes