Breaks update-grub

After this change to menu.lst, update-grub produces useful kernel lines again:
-# kopt=root=/dev/hda1 ro
+# kopt=ro boot=disk resume=/dev/sda3

MIC uses update-grub to generate menu.list. The lines you mentioned are auto generated by update-grub.
Can you elaborate on what MIC should be/shouldn't be doing?

Where do the "boot=disk" and "resume=/dev/sda3" come from in the initial menu.lst found in MIC generated images? This is the place that needs fixing.

From a quick grep, this is in libs/InstallImage.py, in apply_hd_kernel_cmdline(self). What this function does is that it changes the "kernel" commands in menu.lst, but doesn't change the place where the parameters are really defined ("# kopt=").

Instead, MIC should change "#kopt=" as shown above and should then call update-grub which will regenerate the "kernel" commands.

Then I realized that the defoptions were already appending "quiet splash", so no need to list them in hd_kernel_cmdline.

Finally, run update-grub instead of all kernel lines; this takes all changes into account and the resulting menu.lst makes update-grub idempotent.

You're supposed to set the status to Confirmed or New when I add information, otherwise the bug wont show in your bug list -- unless you still consider I didn't provide enough information.

Currently what is it status? I saw a debian/changelog. but I look like that doesn't fix.

I think the patches attached here are relevant and useful; however there's a smaller issue in that /boot isn't mounted when generating menu.lst the first time, so the next kernel upgrades seems to think we're transitionning the config from /boot below / partition to /boot standalone partition.

But the original issue described here is still fixed by the above patches; the second issue is something related to new kernels / kernel upgrades and is already present in the current form.