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 getting sizes for some of these types of devices given the extra information provided on the command line.
~tom On Dec 1, 2008, at 5:02 PM, Nick Barcet wrote: > 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 reliably the size of the raw device passed considering the > various type that can be used. Ideas welcome... > > While at it I also realized that it was not possible to use --raw > multiple times as is was possible to do with the bash implementation. > It is quite useful when used together with --part when you specify > multiple disk. I fixed that as well. > > > ** Changed in: vm-builder (Ubuntu) > Assignee: (unassigned) => Nick Barcet (nijaba) > Status: New => Fix Committed > > ** Changed in: vm-builder (Ubuntu) > Importance: Undecided => Medium > > -- > python-vm-builder --raw doesn't set size correctly > https://bugs.launchpad.net/bugs/303882 > You received this bug notification because you are a direct subscriber > of the bug. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
