http://bugzilla.suse.com/show_bug.cgi?id=1170842
http://bugzilla.suse.com/show_bug.cgi?id=1170842#c3
--- Comment #3 from Thomas Blume
(In reply to Thomas Blume from comment #1)
Thomas, thanks for checking this one too!
If not explicitly given at the command line, dracut will only set up one interface and just continue if this is successfull, which is the case here:
This confuses me, as traditionally all my PXE images for the last 1.5 year are using two interfaces, and the tftp server was listening on the second one. As we say in the log from the Intel device, both interfaces were detected and ifup was called for them.
Yes, if the dhcp setup of the first network interface is not sucessfull, subsequent ones are tried until the setup on one succeeds. But if the setup on the first interface already succeeds, there is no need to setup additional interfaces (unless explicitly specified with the ip= parameter). If your pxe server only listens on the second interface, the dhcp setup on the first one will fail and dracut should go to the next.
Still, I can see that a device gets plugged:
--> [ 36.297674] localhost systemd[1]: dev-vda.device: Changed dead -> plugged [ 36.298760] localhost systemd[1]: sys-devices-platform-LNRO0005:1f-virtio2-block-vda.device: Changed dead -> plugged --<
Is vda the device configured for installation?
You just found a new bug. You are right that indeed I cannot see vda with this new version of the image, but can be a kernel issue. I will rebuild the image under a more up-to-date TW in some days.
Ok -- You are receiving this mail because: You are on the CC list for the bug.