maas-devel team mailing list archive

[Julian Edwards <julian.edwards@xxxxxxxxxxxxx>]

On 31/01/14 02:26, Scott Moser wrote:
> On Thu, 30 Jan 2014, Andres Rodriguez wrote:
> 
>> Hi Scott,
>>
>> The way d-i does it is like:
>>
>> d-i debian-installer/add-kernel-opts string

I didn't even manage to get this to work with a d-i installation.  I
edited the preseed such that:

=== modified file 'contrib/preseeds_v2/generic'
--- contrib/preseeds_v2/generic 2013-09-23 15:41:09 +0000
+++ contrib/preseeds_v2/generic 2014-01-31 02:05:27 +0000
@@ -16,6 +16,13 @@
 {{endif}}
 {{enddef}}

+{{def kernel_opts}}
+{{py: tag, opts = node.get_effective_kernel_options()}}
+{{if opts}}
+d-i debian-installer/add-kernel-opts {{opts}}
+{{endif}}
+{{enddef}}
+
 {{def client_packages}}
 d-i     pkgsel/include string cloud-init openssh-server
python-software-properties vim avahi-daemon server^
 {{enddef}}

=== modified file 'contrib/preseeds_v2/preseed_master'
--- contrib/preseeds_v2/preseed_master  2013-07-03 02:17:12 +0000
+++ contrib/preseeds_v2/preseed_master  2014-01-31 01:48:52 +0000
@@ -88,5 +88,8 @@
 # maas preseed
 {{self.preseed}}

+# Kernel options for the installer.
+{{self.kernel_opts}}
+
 # Post scripts.
 {{self.post_scripts}}


Which resulted in this extra line getting added to my preseed for the
node I was booting:

d-i debian-installer/add-kernel-opts nomodeset

However the installed and booted kernel didn't have it set:

ubuntu@gxx4a:~$ dmesg|grep Command
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-58-generic
root=UUID=b915d6a3-34a7-4264-b24e-20a0ae2d6223 ro quiet

>>
>> So I don't know whether curtin will.
> 
> so there is no way to that.  The behavior present (which seems sufficient
> in most cases) is to copy any params from the booted kernel that come
> after a '--'.  If there is no '--', it will copy off 'console=' parameters
> also.

So -- just has the effect of ignoring console= ?  Otherwise all the
current kernel params are copied to the installed system?

I don't see this behaviour though.  I used nomodeset as above in the pxe
options, and the resulting installed system does not have this set.

> Is there a reason you'd boot the installer with one set of parameters but
> need additional ones for the installed system? I'm sure there are some,
> but generally think that using the same set in both cases would work
> right.
> 
> all that said, it can be added as a feature to curtin.

I don't know of a use case for that in maas, at least not yet :)


J.