mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Harald Hoyer <harald-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, 2 May 2012 13:11:49 -0400	[thread overview]
Message-ID: <20120502171149.GJ4141@redhat.com> (raw)
In-Reply-To: <20120502145333.GI4141-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Wed, May 02, 2012 at 10:53:33AM -0400, Vivek Goyal wrote:

[..]
> > > did you specify "ip=..." ?
> > 
> > Yes I did specify "ip=..". Even if network is not up, I thought respective
> > code will try to bring up iscsi lun and fail. I am not seeing anybody even
> > trying to bring up iscsi lun.
> 
> I am going through my debug logs. I do see that ip= option has been parsed
> and in fact 85write-ifcfg.sh takes care of writing the configuration file
> for it. Now who is supposed to bring up eth0?

Ok, I can find logs where we installed a udev rule to bring up eth0. Looks
like that rule ran (ifup) and I see /tmp/net.eth0.up file. Also dhclient
is running.

But when try to ping the vm it does not respond. "ip route show" does not
show any routes either. That would say that this interface is not up
or did not get dhcp address. Not sure why though.

Thanks
Vivek

      parent reply	other threads:[~2012-05-02 17:11 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
     [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 [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=20120502171149.GJ4141@redhat.com \
    --to=vgoyal-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox