Does netroot=isci: option work with latest dracut
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
A message that is not in the archive (sent off-list or not yet received): [email protected]
Am 01.05.2012 18:47, schrieb Vivek Goyal:
Quoted 13 lines
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.shbut after that nothing happens. Nobody tries to bring up the iscsi luns.I see some code in
iscsiroot.shto 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.
Quoted 5 lines
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=..." ?
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 14 lines · Harald Hoyer
Am 01.05.2012 18:47, schrieb Vivek Goyal:
Quoted 13 lines
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.shbut after that nothing happens. Nobody tries to bring up the iscsi luns.I see some code in
iscsiroot.shto 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.
Quoted 7 lines
Quoted 5 lines
So I am wondering if I am doing something wrong or there is some disconnect in my understanding of how netroot= options works.
Thanks
Vivekdid 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.
What piece of code is supposed to do that. I don't see anybody calling into /sbin/iscsiroot.
Thanks
Vivek
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 18 lines · Vivek Goyal
Quoted 17 lines · Harald Hoyer
Am 01.05.2012 18:47, schrieb Vivek Goyal:
Quoted 16 lines
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.shbut after that nothing happens. Nobody tries to bring up the iscsi luns.I see some code in
iscsiroot.shto 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.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
Thanks
Vivekdid 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?
(I see that mount-sys pre-pivot is running before 85write-ifcfg.sh. Is this right. a --mount might be mounting a disk which is exported over network).
Thanks
Vivek
A message that is not in the archive (sent off-list or not yet received): [email protected]
On Wed, May 02, 2012 at 10:53:33AM -0400, Vivek Goyal wrote:
[..]
Quoted 9 lines
Quoted 5 lines
Quoted 1 line
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.shtakes 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