From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: "David S. Ahern" <daahern@cisco.com>
Cc: Amos Kong <akong@redhat.com>, kvm@vger.kernel.org
Subject: Re: [Autotest] Autotest: Unattended_install testcase always fail with rhel3.9-32 guest
Date: Mon, 19 Apr 2010 15:56:03 -0300 [thread overview]
Message-ID: <1271703363.2505.15.camel@localhost.localdomain> (raw)
In-Reply-To: <4BCBCED9.4000004@cisco.com>
On Sun, 2010-04-18 at 21:32 -0600, David S. Ahern wrote:
> 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.
Problem resolved :) Yay!
http://autotest.kernel.org/changeset/4432
Thank you very much David,
prev parent reply other threads:[~2010-04-19 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <-1719040579288086063@unknownmsgid>
2010-04-14 14:01 ` [Autotest] Autotest: Unattended_install testcase always fail with rhel3.9-32 guest Lucas Meneghel Rodrigues
2010-04-14 14:02 ` Lucas Meneghel Rodrigues
2010-04-16 14:03 ` David S. Ahern
2010-04-16 15:36 ` Lucas Meneghel Rodrigues
2010-04-16 19:08 ` [Autotest] " David S. Ahern
2010-04-18 4:09 ` Amos Kong
[not found] ` <20100418035704.GA2688@akong@redhat.com>
2010-04-18 4:55 ` [Autotest] " David S. Ahern
2010-04-18 18:26 ` Lucas Meneghel Rodrigues
2010-04-19 3:32 ` David S. Ahern
2010-04-19 18:56 ` Lucas Meneghel Rodrigues [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=1271703363.2505.15.camel@localhost.localdomain \
--to=lmr@redhat.com \
--cc=akong@redhat.com \
--cc=daahern@cisco.com \
--cc=kvm@vger.kernel.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