From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Subject: Re: PV HVM Linux drivers fail Date: Mon, 2 Aug 2010 15:48:16 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1461297174==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org --===============1461297174== Content-Type: multipart/alternative; boundary=0015175cdfaa1653e9048cdeff10 --0015175cdfaa1653e9048cdeff10 Content-Type: text/plain; charset=ISO-8859-1 The code from 2.6.35-rc5-pvhvm-v6 works well! Thanks! I can access /dev/hda created by blkfront. However, the netfront driver still can't detect the MAC address of the nic if I unplug it. (If I don't unplug it, 8139cp works with the device just fine) And this code there seems to be no dependency on the loading order of platform-pci and netfront/blkfront. Leo On Fri, Jul 30, 2010 at 10:24 AM, Leo wrote: > Hi Stefano, > > Great. I will test the new code this weekend. I will also try to figure > how exactly the module initialization fails when all three are compiled in. > > As for the network MAC address problem, the card is working just fine if I > don't unplug it and let 8139cp take over the device. So the bridge is set > up correctly, isn't it? > > > Thanks! > > Leo > > > On Fri, Jul 30, 2010 at 7:34 AM, Stefano Stabellini < > stefano.stabellini@eu.citrix.com> wrote: > >> On Thu, 29 Jul 2010, Leo wrote: >> > Thanks for the info Stefano. >> > >> > When I compile-in the three devices, it always get into the XENBUS wait >> loop. Drivers loading order has always been a >> > mystery to me (though I haven't spent much time on that.) >> > >> >> I took some time to read the code again and do few tests: it seems to me >> that everything is working just fine in all cases. I am not sure what's >> wrong with your setup but I can boot my guest with all three components >> built-in or modules. >> >> > I am waiting for the new branch for the fix then. >> >> the new branch is ready, please give it a try and let me know. >> >> > Does the bug also affect netfront to not able to get the MAC address? >> > It's also what I'm seeing as well, described near the end of my message. >> > >> >> do you have a bridge correctly configured in your testbox? > > > --0015175cdfaa1653e9048cdeff10 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The code from 2.6.35-rc5-pvhvm-v6 works well!=A0 Thanks!=A0 I can access /d= ev/hda created by blkfront.=A0 However, the netfront driver still can't= detect the MAC address of the nic if I unplug it.=A0 (If I don't unplu= g it, 8139cp works with the device just fine)=A0 And this code there seems = to be no dependency on the loading order of platform-pci and netfront/blkfr= ont.


Leo

On Fri, Jul 30, 2010 at 10:24= AM, Leo <fenc= ingleo@gmail.com> wrote:
Hi Stefano,

Great.=A0 I will test the new code this weekend.=A0 I wi= ll also try to figure how exactly the module initialization fails when all = three are compiled in.

As for the network MAC address problem, the c= ard is working just fine if I don't unplug it and let 8139cp take over = the device.=A0 So the bridge is set up correctly, isn't it?


Thanks!

Leo


On Fri, Jul 30, 2010 at = 7:34 AM, Stefano Stabellini <stefano.stabellini@eu.citrix.c= om> wrote:
On Thu, 29 J= ul 2010, Leo wrote:
> Thanks for the info Stefano.
>
> When I compile-in the three devices, it always get into the XENBUS wai= t loop.=A0 Drivers loading order has always been a
> mystery to me (though I haven't spent much time on that.)
>

I took some time to read the code again and do few tests: it seems to= me
that everything is working just fine in all cases. I am not sure what's=
wrong with your setup but I can boot my guest with all three components
built-in or modules.

> I am waiting for the new branch for the fix then.=A0

the new branch is ready, please give it a try and let me know.

> Does the bug also affect netfront to not able to get the MAC address?= =A0
> It's also what I'm seeing as well, described near the end of m= y message.
>

do you have a bridge correctly configured in your testbox?


--0015175cdfaa1653e9048cdeff10-- --===============1461297174== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1461297174==--