WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen domU networking problem Centos5

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen domU networking problem Centos5
From: Aero_nomad <nomad@xxxxxxxxxx>
Date: Fri, 22 Jun 2007 00:17:14 +0530
Delivery-date: Thu, 21 Jun 2007 11:46:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1182445194.3646.23.camel@PING6>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: bikenomads.com
References: <1182445194.3646.23.camel@PING6>
Reply-to: nomad@xxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
What does the following commands result in 

In Dom0 
     $  brctl show 
     $  ifconfig 
     $  route -n

In DomU
     $  ifconfig
     $  route -n

Perhaps the results will give a better insight.

Regards,
Soj

On Thursday 21 Jun 2007 10:29 pm, majid baruze wrote:
> Hi all,
>
> I have to assign one of two PCI Ethernet adapters of my Pc to use noly
> in domU. I try network-bridging without success.
>
> Anybody can help me with that?
>
> # lspci | grep Ethernet
> 05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet
> Controller (Copper) (rev 01) 05:00.1 Ethernet controller: Intel Corporation
> 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
>
> ------
> dom0: (grub config)
> ------
> title CentOS (2.6.18-8.el5xen)
>         root (hd0,0)
>         kernel /xen.gz-2.6.18-8.el5
>         module /vmlinuz-2.6.18-8.el5xen ro root=/dev/VGsystem/LVroot \
> rhgb quiet pci=routeirq pciback.permissive
>                          pciback.hide=(05:00.1)
>         module /initrd-2.6.18-8.el5xen.img
>
> ------
> my network-bridge script:
>
> #!/bin/sh
> # Exit if anything goes wrong.
> set -e
> #
> # First arg is the operation.
> OP=$1
> shift
> #
> script=/etc/xen/scripts/network-bridge
> #
> case ${OP} in
>  start)
>        $script start vifnum=0 bridge=xbr0 netdev=eth0
>        $script start vifnum=1 bridge=xbr1 netdev=eth1
>        ;;
>    stop)
>        $script stop vifnum=0 bridge=xbr0 netdev=eth0
>        $script stop vifnum=1 bridge=xbr1 netdev=eth1
>        ;;
>    status)
>        $script status vifnum=0 bridge=xbr0 netdev=eth0
>        $script status vifnum=1 bridge=xbr1 netdev=eth1
>        ;;
>    *)
>       echo 'Comando sconosciuto: ' ${OP}
>       echo 'Utilizza: start, stop, status'
>       exit 1
> esac
>
>
> -----
> domU: (domain config)
> -----
> name = "xen1"
> builder = "hvm"
> memory = "1000"
> disk = [ 'phy:/dev/VGsystem/Lvxen1,hda,w' ]
> pci = [ '05.00.1' ]
> vif = [ 'mac=00:16:3e:23:54:9b,bridge=xenbr1' ]
> uuid = "cd2eeef9-e079-e158-b10f-3e21914afcee"
> device_model = "/usr/lib/xen/bin/qemu-dm"
> kernel = "/usr/lib/xen/boot/hvmloader"
> vnc=1
> vncunused=1
> apic=1
> acpi=1
> pae=1
> vcpus=1
> serial = "pty" # enable serial console
> on_reboot   = 'restart'
> on_crash    = 'restart'
>
>
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

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

<Prev in Thread] Current Thread [Next in Thread>