On 04/18/2010 12:26 PM, Lucas Meneghel Rodrigues wrote: > On Sat, 2010-04-17 at 22:55 -0600, David S. Ahern wrote: >> >> On 04/17/2010 10:09 PM, Amos Kong wrote: >>> %post --interpreter /usr/bin/python >>> import socket, os >>> os.system('dhclient') >>> os.system('chkconfig sshd on') >>> os.system('iptables -F') >>> os.system('echo 0 > /selinux/enforce') >>> server = socket.socket(socket.AF_INET, socket.SOCK_STREAM) >>> server.bind(('', 12323)) >>> server.listen(1) >>> (client, addr) = server.accept() >>> client.send("done") >>> client.close() >> >> So, effectively after the install completes use dhclient to configure a >> network address, start a server on a known port and when a client >> connects send the message "done". I would expect that to work just fine. > > Me too, it has been working for RHEL 4.X, 5.X 32/64 bit and 3.X 64 bit. > The problem has been effectively 3.9 32 bit. I fired up a 3.9 guest with your ks.cfg. The problem is due to the limited functionality in the RHEL3 BOOT kernel for i386. Specifically, dhclient is failing at: setsockopt(6, SOL_SOCKET, SO_ATTACH_FILTER, "\v\0\6\10\240Y\n\10", 8) = -1 ENOPROTOOPT So dhclient client is out. But you can still configure and use networking via ifconfig if static addressing is an option for you. I was able to use that command to configure eth0 and push an strace output file for dhclient. Also, a couple of comments on this use case: - SELinux is not applicable - 32 GB of RAM is way beyond what the RHEL3 i386 can detect and use - 12 vcpus seems high as well. David > >> What part is not working? Have you used anaconda's root shell (alt-f2) >> to confirm each step and if so which one is not setup as expected? > > dhclient. It fails saying "module IP_... could not be loaded. > >> David >> -- >> To unsubscribe from this list: send the line "unsubscribe kvm" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html