From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: Does netroot=isci: option work with latest dracut
Date: Wed, 02 May 2012 11:12:48 +0200 [thread overview]
Message-ID: <4FA0FA90.1010702@redhat.com> (raw)
In-Reply-To: <20120501164704.GA18202-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Am 01.05.2012 18:47, schrieb Vivek Goyal:
> Hi,
>
> On F17, I am trying kdump to an iscsi target. And I am passing a
> netroot=iscsi:..... cmdline to dracut. But that does not seem to work.
>
> Some debugging showed that we do parse the netroot= arguemnt in
> parse-iscsiroot.sh but after that nothing happens. Nobody tries to
> bring up the iscsi luns.
>
> I see some code in iscsiroot.sh to call iscsistart to bring up iscsi
> luns but that code does not seem to be hooked up. I could not figure
> out who calls /sbin/iscsiroot.
>
> So I am wondering if I am doing something wrong or there is some
> disconnect in my understanding of how netroot= options works.
>
> Thanks
> Vivek
did you specify "ip=..." ?
next prev parent reply other threads:[~2012-05-02 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 16:47 Does netroot=isci: option work with latest dracut Vivek Goyal
[not found] ` <20120501164704.GA18202-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-05-02 9:12 ` Harald Hoyer [this message]
[not found] ` <4FA0FA90.1010702-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-05-02 13:54 ` Vivek Goyal
[not found] ` <20120502135426.GF4141-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-05-02 14:53 ` Vivek Goyal
[not found] ` <20120502145333.GI4141-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-05-02 17:11 ` Vivek Goyal
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=4FA0FA90.1010702@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
/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.