RE: Xen enviroment consultation

RE: Xen enviroment consultation

[Fan, Huaxiang]

[-- Attachment #1.1: Type: text/plain, Size: 2201 bytes --]

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?

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.emulators.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, it work fine after I solve an amount of issues. Now 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 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<http://www.websense.cn>

Websense TRITON(tm)
For Essential Information Protection(tm)
Web Security<http://www.websense.com/content/Regional/SCH/WebSecurityOverview.aspx> | Data Security<http://www.websense.com/content/Regional/SCH/DataSecurity.aspx> | Email Security<http://www.websense.com/content/Regional/SCH/MessagingSecurity.aspx>


Protected by Websense Hosted Email Security - www.websense.com


Click here<https://www.mailcontrol.com/sr/kx3v7MIIIL3TndxI!oX7UgVuQEctqoeeibXEkDczIW9I0BMhn34!oDHZr!vQ4Qak0+EvhqRAbnUd5rLFZ!o!pA==> to report this email as spam.

[-- Attachment #1.2: Type: text/html, Size: 7702 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Re: RE: Xen enviroment consultation

[Konrad Rzeszutek Wilk]

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.

RE: RE: Xen enviroment consultation

[Fan, Huaxiang]

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?

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           <none>

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.

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,
> 
> 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.

_______________________________________________
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 

Re: RE: Xen enviroment consultation

[Konrad Rzeszutek Wilk]

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           <none>
> 
> 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?