[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] newbie: suse enterprise 10 SP1 domU network problem


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Regis Bourdet" <bourdet.r@xxxxxxxxx>
  • Date: Wed, 7 May 2008 17:45:54 +0200
  • Delivery-date: Wed, 07 May 2008 08:46:29 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=GOuoX0pP5LB4B1efBYji+p8yPy3HV3y73slk5pa+lJIIrQv8cwbobl/LzDBTjZ8Ww7V5Oupo+gI7sFDP9CVWPptfg2KxDVTm6Y/nySaep+C4CCXB5StXjJ0pP73DPh/8hfSvX92WGVHPL0lX+0b5Wo9D+6lhbR/tcpnHLB8TPbM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

After the start of xend I only see the bridge xenbr0 along with eth0 (apart eth1 which is not in use at all).
Networking on dom0 is ok.

Starting a domU (a windows 2003 server) produces a vifx.0 successfully, but I can't reach any network and ping with domU.
(and I didn't touch any scripts in /etc/xen...)

Here is what I have on dom0 before lunching any domU
# brctl show xenbr0
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.000000000000       no

Here is what U have after domU is lunched
# brctl show xenbr0
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.1a57276c440e       no              vif1.0
                                                                            tap0

Since I am new to xen, I may miss somthing crucial,
SuseFirewall is turned off, I switched IP_FORWARDING from off to on.

Any idea are welcome,

Thanks
--
Régis Bourdet
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.