[Bug 285093] Re: Dapper images fail to boot

2008-10-29 Thread Nick Barcet
** Changed in: vmbuilder Status: Fix Committed = Fix Released -- Dapper images fail to boot https://bugs.launchpad.net/bugs/285093 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 285093] Re: Dapper images fail to boot

2008-10-24 Thread Launchpad Bug Tracker
This bug was fixed in the package vm-builder - 0.9-0ubuntu3 --- vm-builder (0.9-0ubuntu3) intrepid; urgency=low [ Johan Euphrosine ] * Fix exception when suite provided does not exist (LP: #281801) and provide unit test for it. [ Chuck Short ] * Added parameters required

[Bug 285093] Re: Dapper images fail to boot

2008-10-20 Thread Albert Damen
Nick, I am surprised Gutsy works for you with inode size 256, given the grub change was first made in Hardy (and even Debian got that fix only in 0.97-30, Feb 2008). So I tested this and for me the Gutsy vm fails to boot with grub error 2, just like Dapper did. -- Dapper images fail to boot

Re: [Bug 285093] Re: Dapper images fail to boot

2008-10-20 Thread Nick Barcet
Yep, it failed for me when I redid the tests, so now hardy is in 128bit as well. Thanks. -- Dapper images fail to boot https://bugs.launchpad.net/bugs/285093 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 285093] Re: Dapper images fail to boot

2008-10-19 Thread Albert Damen
Recently I had the grub error 2 when I wanted to move my system from an old hard-disk to a new one. It turned out recent mkfs will create the filesystem with inode size 256. This is only supported by grub since hardy (grub 0.97-29ubuntu19). ubuntu-vm-builder on hardy uses inode size 128 both

[Bug 285093] Re: Dapper images fail to boot

2008-10-19 Thread Albert Damen
Ah, that was not too hard. In /usr/share/pyshared/VMBuilder/disk.py line 282/283, I changed: def mkfs_fstype(self): return { TYPE_EXT2: ['mkfs.ext2', '-F'], TYPE_EXT3: ['mkfs.ext3', '-F'], TYPE_XFS: ['mkfs.xfs'], TYPE_SWAP: ['mkswap'] }[self.type] into: def mkfs_fstype(self):

[Bug 285093] Re: Dapper images fail to boot

2008-10-19 Thread Nick Barcet
Albert Damen wrote: However, the kernel line in grub is not correct and needed to be edited during the boot: kernel /boot/vmlinuz-2.6.15-52-amd64-server root=/dev/hdbound method Disk.devletters of VMBuilder.disk.Disk object at 0x7feee257c8d01 ro quiet splash Thanks a lot to your

[Bug 285093] Re: Dapper images fail to boot

2008-10-19 Thread Nick Barcet
rev 250 of trunk includes the fix for the inode. I decided to use 128 bit inode for dapper, edgy and feisty, as gutsy and seems to boot with 256 bit. Will run some test again on all suite to check. ** Changed in: vmbuilder Status: In Progress = Fix Committed ** Changed in: vm-builder