On Tue, Aug 4, 2009 at 11:23 AM, Michael Goldishmgold...@redhat.com wrote:
Looks like there really are only 3 lines to read.
Telnet is printing those lines, not windows. It's just indicating
that it successfully connected. Windows is saying nothing.
This is a little weird, because:
- It can
For making it more clear here are the timoeout debug prints
14:31:04 INFO | ('DEBUG: timeout in read_until_output_matches =%d', 30)
14:31:04 INFO | ('DEBUG: internal_timeout in read_until_output_matches
=%d', 3.5)
{sorry with little syntax typo :( }
On Tue, Aug 4, 2009 at 12:12 PM, sudhir
Maybe the problem is related to how you implemented TAP support in
your tree. You're obviously not using user mode networking because
the guest's IP address is 10.0.99.100. I'm not sure exactly what the
problem is, so can you print the connection command in remote_login()?
Add something like
On Tue, Aug 4, 2009 at 5:01 PM, Michael Goldishmgold...@redhat.com wrote:
Maybe the problem is related to how you implemented TAP support in
your tree. You're obviously not using user mode networking because
I do not understand what do you mean here. Yes the setup is a tap
network and I can
On Tue, Aug 4, 2009 at 10:06 PM, Michael Goldishmgold...@redhat.com wrote:
- sudhir kumar smalik...@gmail.com wrote:
On Tue, Aug 4, 2009 at 5:01 PM, Michael Goldishmgold...@redhat.com
wrote:
Maybe the problem is related to how you implemented TAP support in
your tree. You're
- sudhir kumar smalik...@gmail.com wrote:
On Tue, Aug 4, 2009 at 10:06 PM, Michael Goldishmgold...@redhat.com
wrote:
- sudhir kumar smalik...@gmail.com wrote:
On Tue, Aug 4, 2009 at 5:01 PM, Michael
Goldishmgold...@redhat.com
wrote:
Maybe the problem is related to how you
Hi,
I am seeing a telnet failure in autotest to a win2k8 DC 64 bit guest.
I have tried some debugging and came to a conclusion that
read_nonblocking() is reading only 3 lines. let me first print the
output of manual login
# telnet -l Administrator 10.0.99.100 23
Trying 10.0.99.100...
Connected
Looks like there really are only 3 lines to read.
Telnet is printing those lines, not windows. It's just indicating
that it successfully connected. Windows is saying nothing.
This is a little weird, because:
- It can happen when the telnet server isn't running at all,
but it seemed to be
