From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mario Subject: Re: PV networking issue in 2.6.38.6 and 2.6.39-rc7 pvops dom0 kernels Date: Tue, 17 May 2011 12:49:18 +0200 Message-ID: <4DD252AE.6080609@slackverse.org> References: <1305536377.31488.213.camel@zakaz.uk.xensource.com> <4DD0E85F.7070105@slackverse.org> <4DD104AB.8000401@slackverse.org> <1305550008.20907.8.camel@zakaz.uk.xensource.com> <4DD11EF5.1050203@slackverse.org> <1305550841.20907.10.camel@zakaz.uk.xensource.com> <4DD120EA.4060204@slackverse.org> <1305551216.20907.12.camel@zakaz.uk.xensource.com> <4DD12212.7020403@slackverse.org> <4DD12389.1020905@slackverse.org> <20110516132231.GS32595@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20110516132231.GS32595@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Ian Campbell , "todd.deshane@xen.org" , "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 05/16/2011 03:22 PM, Pasi K=E4rkk=E4inen wrote: > On Mon, May 16, 2011 at 03:15:53PM +0200, Mario wrote: >> 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 networkin= g on >>>>> PV guests, but HVM does? >>>> >>>> Yes, netback did not go upstream until 2.6.39 so PV networking (eith= er >>>> for PV or HVM guests with PV drivers) will not work on mainline kern= els >>>> 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 device= s >> blank screen when dom0 boots up. I have seen this happen mostly on old= er >> vga cards but its not a rule. Should i just keep on blacklisting kerne= l >> modules for those cards, or is there some kind of a more general >> solution? > > You could try "nomodeset" parameter to disable KMS modesetting.. > (and possibly adding "console=3Dtty0") > > Xen patches for DRM/KMS haven't been merged to upstream Linux yet. > > -- Pasi > nomodeset and/or nofb do not seem to help. console=3Dtty0 also does not seem to have any effect. Only way to successfuly boot dom0 is with one of these: CONFIG_FB=3Dn or echo "blacklist s3fb" > /etc/modprobe.d/blacklist-s3fb.conf As soon as fb device is modprobed, booting stops, and server freezes. Can anything else be done? Perhaps some setting for xen in kernel..?