Actually the first partition's start value of 63s is hardcoded into the
script.
Therefore it's easy to change:
Edit /usr/share/pyshared/VMBuilder/disk.py
In line 299, change
partition_start = 63s
to
partition_start = 2048s
--
You received this bug notification because you are a member of
Since Lucid, partitions start at 1MiB (2048s) to ensure good performance
on advanced format drives
(https://wiki.ubuntu.com/LucidLynx/ReleaseNotes#Partition_alignment_changes_may_break_some_systems).
Maybe ubuntu-vm-builder could do the same ?
--
You received this bug notification because you
I've just had a look at this patch again and I see a problem.
You always offset by 63 sectors, despite the out of ubuntu-vmbuilder
saying (see attached output) that the CHS geometry used was */4/32. You
are offsetting by 63 sectors, so that's not a a cyl boundary.
More seriously, if this image
I can confirm that simply change '63s' to '64s' in the attached patch
worked fine. I only applied the portion of the patch related to cylinder
offsets.
If I knew Python, I'd make the partitions file take a start position in
Parted format. But I don't.
--
You received this bug notification
Confirmed that without this patch, grub-setup (hd0) (with grub-pc's
grub-setup)
complains as described above, and, with this patch, it's just fine. So I will
merge
in the patch. Thanks again for the patch, Neil, and for the bug report, Alex.
--
You received this bug notification because you
I may be reading this patch wrong:
lp:~brightbox/vmbuilder/exclude-first-cylinder
but that would appear to create the first partition 63 sectors in. If
so, this is incorrect (note I haven't tried it).
Technically you should get the geometry from the disk, but most disks
(not all) have 63
That's just me getting my tracks and cylinders mixed up then. It
should be 'ignore first track'.
The MSDOS convention is to avoid allocating the first 63 sectors (ie
0x1 lots of 512 bytes about 32K) and that is where grub hides
itself.
Gory details here:
I'm not sure that's right. Firstly, partitions are meant to be cylinder aligned
(per the original DOS specs). sfdisk etc. will refuse to write partition tables
unless they are, unless --force is specified. Secondly, fdisk and other
utilities are now (when they can read the geometry) creating
There appears to be lots of different interpretations that's the
problem. That article was the best description I've found of the
process.
The 63s definition comes from 'partition2disk' as used in the UEC
Eucalyptus implementation. That's the main reason I went with that.
There may be an off by
Just checked partition2disk from Eucalyptus and it does use '63s' as the
start specification for the first partition, so the patch is consistent
with UEC Eucalyptus.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That's not to say that partition2disk is right either - just another
thing that needs to be made consistent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/578199
Title:
ubuntu-vm-builder builds
** Branch linked: lp:~brightbox/vmbuilder/exclude-first-cylinder
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/578199
Title:
ubuntu-vm-builder builds images with no post-MBR gap
--
ubuntu-bugs
** Changed in: ubuntu-vm-builder (Ubuntu)
Status: New = Confirmed
--
ubuntu-vm-builder builds images with no post-MBR gap
https://bugs.launchpad.net/bugs/578199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm doing ubuntu-vm-builder kvm lucid
--
ubuntu-vm-builder builds images with no post-MBR gap
https://bugs.launchpad.net/bugs/578199
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
14 matches
Mail list logo
