From: Loic Dachary <loic@dachary.org>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: teuthology-lock and choosing a kernel
Date: Tue, 10 Mar 2015 08:48:20 +0100 [thread overview]
Message-ID: <54FEA1C4.7020109@dachary.org> (raw)
In-Reply-To: <CAOi1vP8T+JY1v9fnSAvK3UMr2MnzN+KJTWMY26k6zD5p_HCP_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
Hi Ilya,
On 10/03/2015 08:19, Ilya Dryomov wrote:
> On Tue, Mar 10, 2015 at 1:32 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Andrew,
>>
>> I successfully installed a 3.19 kernel (details at http://dachary.org/?p=3594). It turns out that the loop module is compiled in and defaults to having zero partitions allowed by default. Since I was looking for a solution to have /dev/loop useable for tests, I rebooted with /boot/grub/grub.conf as
>>
>> [ubuntu@vpm083 src]$ cat /boot/grub/grub.conf
>> default=0
>> timeout=5
>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>> hiddenmenu
>> title rhel-6.5-cloudinit (3.19.0-ceph-00029-gaf5b96e)
>> root (hd0,0)
>> kernel /boot/vmlinuz-3.19.0-ceph-00029-gaf5b96e ro root=LABEL=79d3d2d4 loop.max_part=16
>> initrd /boot/initramfs-3.19.0-ceph-00029-gaf5b96e.img
>>
>>
>> and that works fine. Do you know if I could do that from the yaml file directly ? Alternatively I could use a kernel that does not have the loop module compiled in and modprobe it with loop.max_part=16, but it's unclear to me what kernels are available and what their names are.
>
> I think you can run a set of commands from yaml (see "exec" stanza), so
> you can sort of script it (GRUB_CMDLINE_LINUX=, etc), but that's never
> going to be reliable.
>
> Basically the only kernel available right now is the testing flavor.
> debug flavor is some random config and has been unused for a while.
> I can try changing testing config to do CONFIG_BLK_DEV_LOOP=m if you
> don't find a good way to workaround it.
>
> https://lists.ubuntu.com/archives/kernel-team/2009-September/007364.html
> is apparently the reason it's compiled in (our config is a somewhat old
> and slightly stripped down Ubuntu config).
Thanks for exploring the history so far back ;-) I hope to find an easier path but its comforting to know where we stand.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-03-10 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 12:50 teuthology-lock and choosing a kernel Loic Dachary
[not found] ` <6E9B72C6-1FA0-46D3-873E-EA99A52BE669@redhat.com>
2015-03-09 14:01 ` Loic Dachary
2015-03-09 22:32 ` Loic Dachary
2015-03-10 7:19 ` Ilya Dryomov
2015-03-10 7:48 ` Loic Dachary [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54FEA1C4.7020109@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.