Bug 224024 - netconsole doesn't work under xen kernel
netconsole doesn't work under xen kernel
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel-xen (Show other bugs)
6
All Linux
medium Severity medium
: ---
: ---
Assigned To: Xen Maintainance List
Brian Brock
:
Depends On: 224023
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-23 13:16 EST by Jeff Layton
Modified: 2014-06-18 03:35 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-02-16 12:50:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Layton 2007-01-23 13:16:20 EST
+++ This bug was initially created as a clone of Bug #224023 +++

When you try to start netconsole under a xen kernel, you get:

netconsole: local port 6665
netconsole: local IP 172.16.59.133
netconsole: interface eth0
netconsole: remote port 6666
netconsole: remote IP 172.16.57.196
netconsole: remote ethernet address 00:16:35:36:af:1e
netconsole: eth0 doesn't support polling, aborting.

The same operation works fine on the same hardware with a non xen kernel.

Ethernet interface is:

06:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
Comment 1 Stephen Tweedie 2007-01-24 10:19:48 EST
It should work fine if you start it before xend, or if you use peth0 instead of
eth0 after xend is running.  Does that help?
Comment 2 Jeff Layton 2007-02-16 12:50:07 EST
We don't ship startup scripts for netconsole alone, but we do ship one for
netdump and you can set it up to just start netconsole by just setting
$NETLOGADDR and not $NETDUMPADDR. When I configured this and chkconfig'ed it on
at boot time, it started it before xend and did work as expected.

I think we can probably close this as NOTABUG. I'll go ahead and do that...

Note You need to log in before you can comment on or make changes to this bug.