From: Brad Plant <bplant@iinet.net.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pvops netconsole
Date: Sat, 13 Feb 2010 11:05:55 +1100 [thread overview]
Message-ID: <20100213110555.2a41df12@daedalus> (raw)
In-Reply-To: <4B75DF98.3070307@goop.org>
[-- Attachment #1.1: Type: text/plain, Size: 877 bytes --]
On Fri, 12 Feb 2010 15:09:12 -0800
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> On 02/04/2010 04:15 PM, Brad Plant wrote:
> > Initialising Xen virtual ethernet driver.
> > blkfront: xvda1: barriers enabled
> > netconsole: local port 11111
> > netconsole: local IP 10.20.40.2
> > netconsole: interface eth1
> > netconsole: remote port 9514
> > netconsole: remote IP 10.20.50.2
> > netconsole: remote ethernet address 00:16:3e:00:50:02
> > netconsole: eth1 doesn't support polling, aborting.
> > netconsole: cleaning up
> >
>
> The xen-netfront device doesn't support the polling interface that
> netconsole relies on. It probably wouldn't be too hard to add that
> capability if you want to. It's independent of the backend and/or the
> actual underlying hardware device.
I like the sound of that. I'll give it a crack :-)
Cheers,
Brad
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-02-13 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 0:15 pvops netconsole Brad Plant
2010-02-05 16:34 ` Konrad Rzeszutek Wilk
2010-02-05 20:21 ` Brad Plant
2010-02-12 23:09 ` Jeremy Fitzhardinge
2010-02-13 0:05 ` Brad Plant [this message]
2010-02-14 2:28 ` Brad Plant
2010-02-14 3:56 ` Jeremy Fitzhardinge
2010-02-14 4:56 ` Brad Plant
2010-02-16 1:22 ` Jeremy Fitzhardinge
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=20100213110555.2a41df12@daedalus \
--to=bplant@iinet.net.au \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
/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.