From: Mario <mario@slackverse.org>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "todd.deshane@xen.org" <todd.deshane@xen.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>,
"Pasi Kärkkäinen" <pasik@iki.fi>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Subject: Re: PV networking issue in 2.6.38.6 and 2.6.39-rc7 pvops dom0 kernels
Date: Mon, 16 May 2011 15:15:53 +0200 [thread overview]
Message-ID: <4DD12389.1020905@slackverse.org> (raw)
In-Reply-To: <4DD12212.7020403@slackverse.org>
On 05/16/2011 03:09 PM, Mario wrote:
> On 05/16/2011 03:06 PM, Ian Campbell wrote:
>> On Mon, 2011-05-16 at 14:04 +0100, Mario wrote:
>>> So you are telling me that 2.6.38 does not have a working networking on
>>> PV guests, but HVM does?
>>
>> Yes, netback did not go upstream until 2.6.39 so PV networking (either
>> for PV or HVM guests with PV drivers) will not work on mainline kernels
>> before that.
>>
>> Emulated HVM networking does not use netback so that will work on
>> earlier kernels (it depends on qemu)
>>
>> Ian.
>>
>
> Ok, thanks, it all makes more sense now. :-)
Ian, while i have your attention, any idea why some framebuffer devices
blank screen when dom0 boots up. I have seen this happen mostly on older
vga cards but its not a rule. Should i just keep on blacklisting kernel
modules for those cards, or is there some kind of a more general solution?
next prev parent reply other threads:[~2011-05-16 13:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DCFC8BB.9030201@slackverse.org>
[not found] ` <20110515155322.GM32595@reaktio.net>
[not found] ` <4DCFF8FA.8020409@slackverse.org>
[not found] ` <20110515161203.GN32595@reaktio.net>
[not found] ` <4DCFFE2B.4040302@slackverse.org>
[not found] ` <20110515163444.GO32595@reaktio.net>
[not found] ` <4DD00235.1090207@slackverse.org>
[not found] ` <20110515170345.GP32595@reaktio.net>
[not found] ` <20110515172030.GQ32595@reaktio.net>
[not found] ` <4DD00C66.7080100@slackverse.org>
2011-05-16 6:51 ` PV networking issue in 2.6.38.6 and 2.6.39-rc7 pvops dom0 kernels Pasi Kärkkäinen
2011-05-16 7:58 ` [Xen-users] " Ian Campbell
2011-05-16 8:56 ` Mario
2011-05-16 8:59 ` Ian Campbell
2011-05-16 9:03 ` Mario
2011-05-16 11:04 ` Mario
2011-05-16 12:46 ` [Xen-users] " Ian Campbell
2011-05-16 12:56 ` Mario
2011-05-16 13:00 ` [Xen-users] " Ian Campbell
2011-05-16 13:04 ` Mario
2011-05-16 13:06 ` Ian Campbell
2011-05-16 13:09 ` Mario
2011-05-16 13:15 ` Mario [this message]
2011-05-16 13:22 ` Pasi Kärkkäinen
2011-05-17 10:49 ` Mario
2011-05-17 11:04 ` Pasi Kärkkäinen
2011-05-17 11:20 ` Mario
2011-05-17 12:09 ` Pasi Kärkkäinen
2011-05-17 12:14 ` Ian Campbell
2011-05-17 14:23 ` Konrad Rzeszutek Wilk
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=4DD12389.1020905@slackverse.org \
--to=mario@slackverse.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=pasik@iki.fi \
--cc=todd.deshane@xen.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).