Hello Philippe, Thanks for the quick response.
I have tested some other cmdline variations, and it makes a difference. I fail to see the logics behind it but here are the results: - several runs with our original settings: about 25% of the runs fails - I removed "bootdev=eth0" as it is not needed with only 1 ip= entry: same result as the original settings - I changed the ip entry to "ip=192.168.4.73:::255.255.255.0::eth0:none" (option 1) booting always failed (tried 20 times) - I added the "ifname=eth0:<mac-address>" entry (option 2) mutch more reliable (1 failure out of 32 runs) Here are the last lines of the bootrace if the failure: -------- [ 0.193542] SCSI subsystem initialized [ 0.195914] Loading iSCSI transport class v2.0-870. [ 0.201704] iscsi: registered transport (tcp) Running in PV context on Xen v4.0. [ 0.211742] udev[68]: starting version 164 [ 0.241931] Initialising Xen virtual ethernet driver. [ 0.244882] udev[70]: renamed network interface eth0 to eth0-renamed [ 0.357445] udev[70]: renamed network interface eth0 to eth0-eth0-renam udevd-work[70]: error changing net interface name eth0-eth0-renam to eth0-renamed: File exists ------ With the last setting it is already mutch more reliable, but I hope to get a complete predictable setup. I also hope you can shine some light on the logics behind these results. Thanks, Gert On 03/21/2011 07:59 PM, Seewer Philippe wrote: > Hello Gert > > Before proceeding further, would you mind trying a few other cmdline > variations? > > 1) extra = 'rd.shell rdnetdebug ip=192.168.4.73:::255.255.255.0::eth0:none > root=/dev/sda1 netroot=iscsi:192.168.4.234::::<target-iqn>' > ==> This should make sure, that the ip line only gets applied to eth0. And > since only one ip line is there anyway bootdev shouldn't be needed > > 2) extra = 'rd.shell rdnetdebug ifname=eth0:00:16:3e:9e:70:71 > ip=192.168.4.73:::255.255.255.0::eth0:none root=/dev/sda1 > netroot=iscsi:192.168.4.234::::<target-iqn>' > ==> If the interface naming somehow gets mixed up ifname should ensure that > eth0 actually is the specified device > > Thank you > Philippe > > > On 03/21/2011 10:21 AM, Gert Huisman wrote: > >> Subject: dracut-network: isciboot sometimes seems to ignore bootdev=eth0 >> argument >> Package: dracut-network >> Version: 005-1 >> Severity: important >> Tags: upstream >> >> We use a dracut-network based initramfs to bootup paravirtualized domU >> machines >> using an iscsi root. This works fine most of the time, but sometimes the >> startiscsi command is selecting the wrong network interface for getting the >> iscsiroot and fails. Usualy a few more trials will bring up the machine >> again, but this is not acceptable for a productions system. >> >> We have a bootdev=eth0 in the kernel command line, which should make shure >> that the iscsi boot is tried from eth0 (bond1). In out current setup it seems >> to be more or less randomly selected. >> >> We are happy to provide additional information if needed. >> >> Gert Huisman >> >> >> >> -- xen config file >> kernel = '/boot/vmlinuz-2.6.32-5-xen-amd64' >> ramdisk = '/etc/xen/iso/dracut-initrd-img-2.6.32-5-xen-amd64' >> vif = [ >> 'mac=00:16:3E:9E:70:71,bridge=bond1', >> 'mac=00:16:3E:9E:70:72,bridge=vlan22', >> 'mac=00:16:3E:9E:70:73,bridge=vlan97' >> ] >> extra = 'rd.shell rdnetdebug ip=192.168.4.73:::255.255.255.0:::none >> bootdev=eth0 root=/dev/sda1 netroot=iscsi:192.168.4.234::::<target-iqn>' >> name = 'geoserver04' >> on_poweroff = 'destroy' >> on_reboot = 'restart' >> on_crash = 'restart' >> -- >> >> >> >> >> -- System Information: >> Debian Release: 6.0 >> APT prefers stable >> APT policy: (500, 'stable') >> Architecture: amd64 (x86_64) >> >> Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/2 CPU cores) >> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> >> Versions of packages dracut-network depends on: >> pn dracut<none> (no description available) >> pn iputils-arping<none> (no description available) >> ii isc-dhcp-client [dh 4.1.1-P1-15+squeeze1 ISC DHCP client >> >> Versions of packages dracut-network recommends: >> pn nbd-client<none> (no description available) >> ii nfs-common 1:1.2.2-4 NFS support files common to >> client >> pn open-iscsi<none> (no description available) >> >> dracut-network suggests no packages. >> >> >> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
