From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Benzi Waisman" Subject: physical network interfaces limitation Date: Mon, 29 Oct 2007 18:13:21 +0200 Message-ID: <001f01c81a46$a00b7f00$222f1dc2@ad.checkpoint.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0614359721==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0614359721== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0020_01C81A57.63944F00" This is a multi-part message in MIME format. ------=_NextPart_000_0020_01C81A57.63944F00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, Does someone know how to overcome the 4 physical network interfaces limitation? Is it a simple change in the open source code to allow more than 4 physical interfaces? Is this limitation comes from the XenSource admin utilities (which are not open source? Are there any implications to this change? Thanks, Benzi. ------=_NextPart_000_0020_01C81A57.63944F00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

Does someone know how to overcome the 4 physical = network interfaces limitation? = Is it a simple change in the open source code to allow more than 4 physical interfaces? Is this = limitation comes from the XenSource admin utilities (which are not open source? = Are there any implications to this change?

Thanks,

Benzi.

------=_NextPart_000_0020_01C81A57.63944F00-- --===============0614359721== 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 --===============0614359721==--