[Bug 303882] Re: python-vm-builder --raw doesn't set size correctly

2010-02-08 Thread Andreas Ntaflos
Would also like to see this fixed for karmic. Using python-vmbuilder 0.11.3-0ubuntu1 and the same error occurs when trying to use a 10G LVM volume as a --raw device. I assume this is the same bug. sudo vmbuilder kvm ubuntu --debug --verbose -m 2048 --raw=/dev/mapper/vg --storage-lv--chat_root

[Bug 303882] Re: python-vm-builder --raw doesn't set size correctly

2009-09-15 Thread Nick Barcet
** Changed in: vm-builder (Ubuntu) Assignee: Nick Barcet (nijaba) = Soren Hansen (soren) -- python-vm-builder --raw doesn't set size correctly https://bugs.launchpad.net/bugs/303882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 303882] Re: python-vm-builder --raw doesn't set size correctly

2009-09-14 Thread Tim Miller Dyck
I see the fix is committed above, but the size='5G' hardcoding on line 37 of /usr/share/pyshared/VMBuilder/disk.py is still present in the current karmic version (python-vm-builder 0.11-0ubuntu2). Can this patch be merged into the karmic version? Thanks! -Tim -- python-vm-builder --raw

[Bug 303882] Re: python-vm-builder --raw doesn't set size correctly

2008-12-01 Thread Nick Barcet
We were indeed mistakenly setting a maximum size of 5G for raw devices for which we should not assume the size. This should now be fixed. Of course there is no telling of what happens if the device is smaller than what you try to fit into it, but I do not see any obvious way to determine

Re: [Bug 303882] Re: python-vm-builder --raw doesn't set size correctly

2008-12-01 Thread Tom
Only suggestion I have is to move away from --raw as an option (except as a last resort) and instead diversify the options such that you could have something like --partition --drive and --lvm (and any others that I am leaving out as valid block devices) and then there should be ways of