From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: [kvm-ppc-devel] guest networking getting close
Date: Tue, 11 Mar 2008 20:25:34 +0000 [thread overview]
Message-ID: <1205267134.11765.23.camel@basalt> (raw)
From this guest boot log (with "ip=dhcp", bridged to the real physical
network), it looks like we actually are receiving packets and delivering
them to the guest properly. I enabled all the NETIF_MSG_* flags in the
8139cp driver, which is where all that eth0 output is coming from.
Unfortunately the guest still doesn't like the packets it's getting
(just times out with DHCP requests), so something's still not happy...
but we're getting closer.
...
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
PCI: Enabling device 0000:00:01.0 (0005 -> 0007)
eth0: RTL-8139C+ at 0xd1014000, 52:54:00:12:34:56, IRQ 28
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
eth0: enabling interface
eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
Sending DHCP requests .<7>eth0: tx queued, slot 1, skblen 590
eth0: intr, status 0004 cmd 0d cpcmd 002b
eth0: tx done, slot 0
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 0 status 0x31000040 len 60
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 1 status 0x31000040 len 60
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 2 status 0x31000040 len 60
.<7>eth0: tx queued, slot 2, skblen 590
eth0: intr, status 0004 cmd 0d cpcmd 002b
eth0: tx done, slot 1
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 3 status 0x31000040 len 60
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 4 status 0x31000040 len 60
.<7>eth0: tx queued, slot 3, skblen 590
eth0: intr, status 0004 cmd 0d cpcmd 002b
eth0: tx done, slot 2
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 5 status 0x31000040 len 60
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 6 status 0x31000040 len 60
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 7 status 0x31000040 len 60
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 8 status 0x31000040 len 60
eth0: intr, status 0001 cmd 0d cpcmd 002b
eth0: rx slot 9 status 0x31000040 len 60
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
reply other threads:[~2008-03-11 20:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1205267134.11765.23.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.