From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fan, Huaxiang" Subject: RE: Xen enviroment consultation Date: Fri, 20 May 2011 10:54:16 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0116768733==" Return-path: In-Reply-To: Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: "Fan, Huaxiang" , "xen-users@lists.xensource.com" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org --===============0116768733== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_E71FC5D6F96C3C4B93FC8FF942D924C63799A7FESSDEXCH1Bwebsen_" --_000_E71FC5D6F96C3C4B93FC8FF942D924C63799A7FESSDEXCH1Bwebsen_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I use Debian6 to do the test. It turns out to be the same problem. I used xen4.0.1 and dom0/domu kernel2.6.32-5-xen-amd64, when I passthru Bro= adcom BCM5709 to the domu, the NIC is UP but not RUNNING (i.e., can not rec= eive/send packages) , What kind of NIC you guys passthru successfully under= xen4+kernel2.6.32? Thanks, Huaxiang From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists= .xensource.com] On Behalf Of Fan, Huaxiang Sent: Monday, May 16, 2011 12:57 PM To: xen-users@lists.xensource.com Subject: [Xen-users] Xen enviroment consultation Hi all, I were upgrading my system recently. But I met some difficult problems, the= biggest one is described in http://permalink.gmane.org/gmane.comp.emulator= s.xen.user/66971, unfortunately I got no answer yet. My original environment is xen3.4.2(64bit) + dom0 kernel 2.6.18-xen, and 4 = domus with kernel 2.6.18-xen, after first upgrade stage, I have Xen4.1.0(64bit)+dom0 kernel 2.6.32.39, and 4 domu with kernel 2.6.18-xen, i= t work fine after I solve an amount of issues. Now I am in the second upgra= de stage. I tried to upgrade one of 4 domus to 2.6.32.39, then I have the i= ssue described in the link above. ( I turn off iommu in xen and kernel) We are using Broadcom BCM5709/5716 Gigabit Ethernet cards and Intel 82571EB= Gigabit Ethernet cards, have anybody had these passthru NICs work on domu = with xen4.1.0 + kernel2.6.32.x for both dom0 and domu? Thanks, HUAXIANG FAN Software Engineer II WEBSENSE NETWORK SECURITY TECHNOLOGY R&D (BEIJING) CO. LTD. ph: +8610.5884.4327 fax: +8610.5884.4727 www.websense.cn Websense TRITON(tm) For Essential Information Protection(tm) Web Security | Data Security | Email Security Protected by Websense Hosted Email Security - www.websense.com Click here to report this= email as spam. --_000_E71FC5D6F96C3C4B93FC8FF942D924C63799A7FESSDEXCH1Bwebsen_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

I use Debian6 to do th= e test. It turns out to be the same problem.

I used xen4.0.1 and do= m0/domu kernel2.6.32-5-xen-amd64, when I passthru Broadcom BCM5709 to the d= omu, the NIC is UP but not RUNNING (i.e., can not receive/send packages) , = What kind of NIC you guys passthru successfully under xen4+kernel2.6.32?

Thanks,

Huaxiang

From: xen-user= s-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com= ] On Behalf Of Fan, Huaxiang
Sent: Monday, May 16, 2011 12:57 PM
To: xen-users@lists.xensource.com
Subject: [Xen-users] Xen enviroment consultation

Hi all,

I were upgrading my system recently. But I met some = difficult problems, the biggest one is described in = http://permalink.gmane.org/gmane.comp.emulators.xen.user/66971, unfortu= nately I got no answer yet.

My original environment is xen3.4.2(64bit) + dom= 0 kernel 2.6.18-xen, and 4 domus with kernel 2.6.18-xen, after first upgrad= e stage, I have

Xen4.1.0(64bit)+dom0 kernel 2.6.32.39, and 4 dom= u with kernel 2.6.18-xen, it work fine after I solve an amount of issues. N= ow I am in the second upgrade stage. I tried to upgrade one of 4 domus to 2= .6.32.39, then I have the issue described in the link above. ( I turn off iommu in xen and kernel)

We are using Broadcom BCM5709/5716 Gigabit Ethernet = cards and Intel 82571EB Gigabit Ethernet cards, have anybody had these pass= thru NICs work on domu with xen4.1.0 + kernel2.6.32.x for both dom0 and= domu?

Thanks,

HUAXIANG FAN
Software Engineer II

WEBSENSE NETWORK SECURITY TECHNOLOGY R&am= p;D (BEIJING) CO. LTD.
ph: +8610.5884.4327
fax: +8610.5884.4727
www.websense.cn

Websense TRITON™
For Essential Information Protection™
Web Security | = Data Security= | Email Security

=

Protected by Websense = Hosted Email Security — www.websense.com

Click here to report this email as spam.

--_000_E71FC5D6F96C3C4B93FC8FF942D924C63799A7FESSDEXCH1Bwebsen_-- --===============0116768733== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --===============0116768733==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: RE: Xen enviroment consultation Date: Fri, 20 May 2011 11:10:02 -0400 Message-ID: <20110520151000.GB10691@dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline 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: "Fan, Huaxiang" Cc: "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Fri, May 20, 2011 at 10:54:16AM +0000, Fan, Huaxiang wrote: > Hi All, > > I use Debian6 to do the test. It turns out to be the same problem. > > I used xen4.0.1 and dom0/domu kernel2.6.32-5-xen-amd64, when I passthru Broadcom BCM5709 to the domu, the NIC is UP but not RUNNING (i.e., can not receive/send packages) , What kind of NIC you guys passthru successfully under xen4+kernel2.6.32? It would be really helpful if you did provide some logs. Did you also pass in 'iommu=soft' in the PV guest? The NICs I've tried it on were .. hmm, I don't have the list in front of me, but I do remember these modules: e1000, igb, ixgb, tg3, sky2, and r8169. From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fan, Huaxiang" Subject: RE: RE: Xen enviroment consultation Date: Mon, 23 May 2011 08:54:19 +0000 Message-ID: References: <20110520151000.GB10691@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20110520151000.GB10691@dumpdata.com> Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Hi Konrad, Thanks, the problem solved when I pass in 'iommu=3Dsoft' in the PV guests. = Could you elaborate on the link between this option and the problem? And this option also raised another minor issue. For example, I have 4 domu= s, and the PCI passthru situation as below: Domu_name passthru_pci_number_in_dom0 1 04:00.0 04:00.1 2 02:00.0 02:00.1 3 01:00.1 4 I passed in 'iommu=3Dsoft' in 1,2,3 domu. The order I should boot the domus= is 1,2,3,4. Otherwise, the domu might fail to boot due to the error: Pciback 0000:04:00.1: device has been assigned to another domain! Over-writ= ing the ownership, but beware. Any idea about this? Thanks, Huaxiang -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists= .xensource.com] On Behalf Of Konrad Rzeszutek Wilk Sent: Friday, May 20, 2011 11:10 PM To: Fan, Huaxiang Cc: xen-devel@lists.xensource.com; xen-users@lists.xensource.com Subject: Re: [Xen-devel] RE: Xen enviroment consultation On Fri, May 20, 2011 at 10:54:16AM +0000, Fan, Huaxiang wrote: > Hi All, >=20 > I use Debian6 to do the test. It turns out to be the same problem. >=20 > I used xen4.0.1 and dom0/domu kernel2.6.32-5-xen-amd64, when I passthru B= roadcom BCM5709 to the domu, the NIC is UP but not RUNNING (i.e., can not r= eceive/send packages) , What kind of NIC you guys passthru successfully und= er xen4+kernel2.6.32? It would be really helpful if you did provide some logs. Did you also pass = in 'iommu=3Dsoft' in the PV guest? The NICs I've tried it on were .. hmm, I don't have the list in front of me= , but I do remember these modules: e1000, igb, ixgb, tg3, sky2, and r8169. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel To report this as spam, please forward to spam@websense.com. Thank you. Protected by Websense Hosted Email Security -- www.websense.com=20 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: RE: Xen enviroment consultation Date: Tue, 24 May 2011 09:54:53 -0400 Message-ID: <20110524135453.GC10926@dumpdata.com> References: <20110520151000.GB10691@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline 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: "Fan, Huaxiang" Cc: "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Mon, May 23, 2011 at 08:54:19AM +0000, Fan, Huaxiang wrote: > Hi Konrad, > Thanks, the problem solved when I pass in 'iommu=soft' in the PV guests. Could you elaborate on the link between this option and the problem? You mean why you need 'iommu=soft' when doing PCI passthrough in PV guests? I would suggest you google for Xen SWIOTLB. I probably wrote the explanation in one of those links - but I don't remember which one. > > And this option also raised another minor issue. For example, I have 4 domus, and the PCI passthru situation as below: > Domu_name passthru_pci_number_in_dom0 > 1 04:00.0 04:00.1 > 2 02:00.0 02:00.1 > 3 01:00.1 > 4 > > I passed in 'iommu=soft' in 1,2,3 domu. The order I should boot the domus is 1,2,3,4. Otherwise, the domu might fail to boot due to the error: > Pciback 0000:04:00.1: device has been assigned to another domain! Over-writing the ownership, but beware. Looks like a bug in the pciback code. It somehow things that you had 04:00.1 assigned to another domain and hadn't cleaned it up probably. For right I would ignore that - as it is not failing the bootup - just warning you. And are you using xen-pciback.hide as an option to "hide" the devices from Dom0?