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] no network to DomU in Ubuntu Hardy

Subject: Re: [Xen-users] no network to DomU in Ubuntu Hardy
From: Albert <forall@xxxxxxxxxxxxx>
Date: Fri, 09 May 2008 16:51:37 +0200
Cc: Xen mailinglist <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 09 May 2008 07:52:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.0.999999.0805091548580.19821@xxxxxxxxxxxxxxxxxxxx>
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>
References: <alpine.DEB.0.999999.0805091548580.19821@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (X11/20080505)
Longina Przybyszewska pisze:
Hi,
I just installed Xen in  Ubuntu Hardy.
DomU is not accessible either from Dom0 or external network.
I used default set up network-bridge/vif-bridge from xend-conf.sxp.

Bridge has got default name eth1 which is my default ethernet interface.

Before creating DomU:
root@jaguar-0:/home/longina# xm list
Name ID Mem VCPUs State Time(s)
Domain-0                                     0  1887     2     r-----24.6

root@jaguar-0:/home/longina# brctl show
bridge name     bridge id               STP enabled     interfaces
eth1            8000.0060085f963e       no              peth1

After creating DomU's image and starting it up:

xen-create-image --hostname=jaguar --mac=00:16:3e:00:00:04 --ip=10.110.4.201 --force xm create jaguar.cfg

root@jaguar-0:/home/longina# xm list
Name ID Mem VCPUs State Time(s)
Domain-0                                     0  1496     2     r-----29.4
jaguar                                       1   512     1     r-----4.1

root@jaguar-0:/home/longina# brctl show
bridge name     bridge id               STP enabled     interfaces
eth1            8000.0060085f963e       no              peth1
                                                        vif1.0
root@jaguar-0:/home/longina# brctl showmacs eth1
port no mac addr                is local?       ageing timer
  1     00:0a:b8:00:be:0a       no                 0.84
  1     00:10:db:ff:26:d0       no                 0.00
  2     00:16:3e:00:00:04       no                38.40
  1     00:60:08:5f:96:3e       yes                0.00
  2     fe:ff:ff:ff:ff:ff       yes                0.00

root@jaguar-0:/home/longina# ping 10.110.4.201
PING 10.110.4.201 (10.110.4.201) 56(84) bytes of data.
From 10.110.4.20 icmp_seq=1 Destination Host Unreachable

Any ideas?

Thanks in advance!

Longina
Hi

In the original kernel hardy heron is a problem with networking support.
If the work is to use the kernel of:

http://www.il.is.s.u-tokyo.ac.jp/%7Ehiranotaka/

Albert

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

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