thr3ads.net - Xen users - [Xen-users] Can''t get guest domain network working! [Jun 2009]

If this information is useful, please help other people find it:
Share via:

Donglai Zhang

2009-Jun-17 05:46 UTC

[Xen-users] Can''t get guest domain network working!

Hi, there:

I have installed xen(2.6.18.8-xen) and had
successfully started domU guests (one or two) from dom0. However, I am
not able to start the network for domU machines.

Following is the information from my linux box.
After the it is started:
$ ifconfig
eth1      Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
          inet addr:XXX.XXX.10.133  Bcast:XXX.XXX.10.255
Mask:255.255.255.0
          inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:196716 errors:0 dropped:0 overruns:0
frame:1
          TX packets:82301 errors:0 dropped:0 overruns:0
carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:91072761 (86.8 MiB)  TX bytes:15558692
(14.8 MiB)
          Interrupt:18

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6440 errors:0 dropped:0 overruns:0
frame:0
          TX packets:6440 errors:0 dropped:0 overruns:0
carrier:0
          collisions:0 txqueuelen:0
          RX bytes:55534272 (52.9 MiB)  TX bytes:55534272
(52.9 MiB)

////////////Start xend
#xend start
Nothing to flush.
Waiting for peth1 to negotiate link.
# ifconfig
eth1      Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
          inet addr:XXX.XXX.10.133  Bcast:XXX.XXX.10.255
Mask:255.255.255.0
          inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25 errors:0 dropped:0 overruns:0
frame:0
          TX packets:40 errors:0 dropped:0 overruns:0
carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3277 (3.2 KiB)  TX bytes:10992 (10.7 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6440 errors:0 dropped:0 overruns:0
frame:0
          TX packets:6440 errors:0 dropped:0 overruns:0
carrier:0
          collisions:0 txqueuelen:0
          RX bytes:55534272 (52.9 MiB)  TX bytes:55534272
(52.9 MiB)

peth1     Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
          inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:196767 errors:0 dropped:0 overruns:0
frame:1
          TX packets:82358 errors:0 dropped:0 overruns:0
carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:91080163 (86.8 MiB)  TX bytes:15574125
(14.8 MiB)
          Interrupt:18

/////////////The peth1 and eth1 are all available and check the bridge...
# brctl show
bridge name     bridge id               STP enabled     interfaces
eth1            8000.00a0c9d665db       no              peth1

///////////The name of the bridge is "eth1" and interface
"peth1" has been
added to the bridge.

///////////Configure the configuration file for the guest domain

************The content of XmGuest.conf*********
kernel = "/boot/vmlinuz-2.6.18.8-xen-U"
memory = 256
name = "ExampleDomain03"
vif = [ ''mac=00:16:3e:31:48:5f'',
''bridge=eth1'' ]  ###The bridge is given
name eth1
disk = [ ''phy:sda7,sda7,w'' ]
dhcp="off"
ip=''XXX.XXX.10.134''
netmask="255.255.255.0"
gateway="XXX.XXX.10.99" #The gateway is the same as the one used by
dom0
network.
hostname="helloworld"

root = "/dev/sda7 ro"
extra = "4"
extra = "xencons=tty"
***************XmGuest.conf finish here**********************

//////Copy /lib/modules/2.6.18.8-xen/ directory to the guest domain disk.
There are some exceptions
//////from guest domain if I don''t do this.

cp -r /lib/modules/2.6.18.8-xen/ /mnt/ubuntu_sda7/lib/modues/

//////Now start the guest domain

# xm create XmGuest.conf
Using config file "./XmGuest.conf".
Started domain ExampleDomain03 (id=11)

///////show xm domains
# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0   510     2     r-----
4443.7
ExampleDomain03                             11   256     1     -b----
9.3

/////////check bridge from dom0
# brctl show
bridge name     bridge id               STP enabled     interfaces
eth1            8000.00a0c9d665db       no              vif11.1

vif11.0

  peth1
///////////The bridge has bounded the guest interface.

////////////On domU guest

dlzhang@dlzhang-desktop:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3e:31:48:5f
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:365 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:28617 (28.6 KB)  TX bytes:1368 (1.3 KB)

eth1      Link encap:Ethernet  HWaddr 00:16:3e:08:da:f6
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:363 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:28085 (28.0 KB)  TX bytes:1368 (1.3 KB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

///////////The network has not been configured successfully.
///////////The eth0 Hardware address is set, but not the ip address

dlzhang@dlzhang-desktop:/etc$ ping XXX.XXX.10.133
connect: Network is unreachable


I have tried with different linux box and different domU, all got the
similar problem.


Would you please give some hints about what might go wrong?


Thanks a lot !

Donglai Zhang


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

Donglai Zhang

2009-Jun-17 05:59 UTC

head link

Re: [Xen-users] Can''t get guest domain network working!

Xen version is 2.6.18.8-xen.

regards,

Donglai




On Wed, Jun 17, 2009 at 3:26 PM, Pallab Chakrabarty <
pchakrabarty@spikesource.com> wrote:
>
> What''s of your Xen and OS make/ver?
>
> - regards
>    Pallab
>
>
>
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Donglai Zhang
> Sent: Wednesday, June 17, 2009 11:16 AM
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] Can''t get guest domain network working!
>
> Hi, there:
>
> I have installed xen(2.6.18.8-xen) and had
> successfully started domU guests (one or two) from dom0. However, I am
> not able to start the network for domU machines.
>
> Following is the information from my linux box.
> After the it is started:
> $ ifconfig
> eth1      Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
>          inet addr:XXX.XXX.10.133  Bcast:XXX.XXX.10.255
> Mask:255.255.255.0
>          inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:196716 errors:0 dropped:0 overruns:0
> frame:1
>          TX packets:82301 errors:0 dropped:0 overruns:0
> carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:91072761 (86.8 MiB)  TX bytes:15558692
> (14.8 MiB)
>          Interrupt:18
>
> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          inet6 addr: ::1/128 Scope:Host
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:6440 errors:0 dropped:0 overruns:0
> frame:0
>          TX packets:6440 errors:0 dropped:0 overruns:0
> carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:55534272 (52.9 MiB)  TX bytes:55534272
> (52.9 MiB)
>
> ////////////Start xend
> #xend start
> Nothing to flush.
> Waiting for peth1 to negotiate link.
> # ifconfig
> eth1      Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
>          inet addr:XXX.XXX.10.133  Bcast:XXX.XXX.10.255
> Mask:255.255.255.0
>          inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:25 errors:0 dropped:0 overruns:0
> frame:0
>          TX packets:40 errors:0 dropped:0 overruns:0
> carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:3277 (3.2 KiB)  TX bytes:10992 (10.7 KiB)
>
> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          inet6 addr: ::1/128 Scope:Host
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:6440 errors:0 dropped:0 overruns:0
> frame:0
>          TX packets:6440 errors:0 dropped:0 overruns:0
> carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:55534272 (52.9 MiB)  TX bytes:55534272
> (52.9 MiB)
>
> peth1     Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
>          inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:196767 errors:0 dropped:0 overruns:0
> frame:1
>          TX packets:82358 errors:0 dropped:0 overruns:0
> carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:91080163 (86.8 MiB)  TX bytes:15574125
> (14.8 MiB)
>          Interrupt:18
>
> /////////////The peth1 and eth1 are all available and check the bridge...
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> eth1            8000.00a0c9d665db       no              peth1
>
> ///////////The name of the bridge is "eth1" and interface
"peth1" has been
> added to the bridge.
>
> ///////////Configure the configuration file for the guest domain
>
> ************The content of XmGuest.conf*********
> kernel = "/boot/vmlinuz-2.6.18.8-xen-U"
> memory = 256
> name = "ExampleDomain03"
> vif = [ ''mac=00:16:3e:31:48:5f'',
''bridge=eth1'' ]  ###The bridge is given
> name eth1
> disk = [ ''phy:sda7,sda7,w'' ]
> dhcp="off"
> ip=''XXX.XXX.10.134''
> netmask="255.255.255.0"
> gateway="XXX.XXX.10.99" #The gateway is the same as the one used
by dom0
> network.
> hostname="helloworld"
>
> root = "/dev/sda7 ro"
> extra = "4"
> extra = "xencons=tty"
> ***************XmGuest.conf finish here**********************
>
> //////Copy /lib/modules/2.6.18.8-xen/ directory to the guest domain disk.
> There are some exceptions
> //////from guest domain if I don''t do this.
>
> cp -r /lib/modules/2.6.18.8-xen/ /mnt/ubuntu_sda7/lib/modues/
>
> //////Now start the guest domain
>
> # xm create XmGuest.conf
> Using config file "./XmGuest.conf".
> Started domain ExampleDomain03 (id=11)
>
> ///////show xm domains
> # xm list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0   510     2     r-----
> 4443.7
> ExampleDomain03                             11   256     1     -b----
> 9.3
>
> /////////check bridge from dom0
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> eth1            8000.00a0c9d665db       no              vif11.1
>
> vif11.0
>
> peth1
> ///////////The bridge has bounded the guest interface.
>
> ////////////On domU guest
>
> dlzhang@dlzhang-desktop:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:16:3e:31:48:5f
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:365 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:28617 (28.6 KB)  TX bytes:1368 (1.3 KB)
>
> eth1      Link encap:Ethernet  HWaddr 00:16:3e:08:da:f6
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:363 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:28085 (28.0 KB)  TX bytes:1368 (1.3 KB)
>
> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> ///////////The network has not been configured successfully.
> ///////////The eth0 Hardware address is set, but not the ip address
>
> dlzhang@dlzhang-desktop:/etc$ ping XXX.XXX.10.133
> connect: Network is unreachable
>
>
> I have tried with different linux box and different domU, all got the
> similar problem.
>
>
> Would you please give some hints about what might go wrong?
>
>
> Thanks a lot !
>
> Donglai Zhang
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.339 / Virus Database: 270.12.75/2182 - Release Date: 06/16/09
> 21:23:00
>


-- 
Donglai Zhang

Ph.D Candidate
School of Computer Science
University of Adelaide,
SA, Australia  5083

Tel: 0061 8 83036166


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

Donglai Zhang

2009-Jun-17 06:31 UTC

head link

Re: [Xen-users] Can''t get guest domain network working!

Hi,

Xen version : xen-3.4
and guest domain  OS Ubuntu 9.04
dom0 OS  Fedora release 7
The ethernet is: Intel EtherExpress Pro 100B
CPU:  Intel(R) Core(TM)2 CPU @2.13GHz.

Cheers,

Donglai

On Wed, Jun 17, 2009 at 3:32 PM, Pallab Chakrabarty <
pchakrabarty@spikesource.com> wrote:
>
>
> This is kernel no, I need xen ver , os make & h/w details..
>
> - regards
>    Pallab
>
>
>
>
> -----Original Message-----
> From: Donglai Zhang [mailto:dlzhangster@gmail.com]
> Sent: Wednesday, June 17, 2009 11:30 AM
> To: Pallab Chakrabarty; xen-users@lists.xensource.com
> Subject: Re: [Xen-users] Can''t get guest domain network working!
>
> Xen version is 2.6.18.8-xen.
>
> regards,
>
> Donglai
>
>
>
>
>
> On Wed, Jun 17, 2009 at 3:26 PM, Pallab Chakrabarty
> <pchakrabarty@spikesource.com> wrote:
>
>
>
> What''s of your Xen and OS make/ver?
>
> - regards
>   Pallab
>
>
>
>
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Donglai Zhang
> Sent: Wednesday, June 17, 2009 11:16 AM
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] Can''t get guest domain network working!
>
> Hi, there:
>
> I have installed xen(2.6.18.8-xen) and had
> successfully started domU guests (one or two) from dom0. However, I am
> not able to start the network for domU machines.
>
> Following is the information from my linux box.
> After the it is started:
> $ ifconfig
> eth1      Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
>         inet addr:XXX.XXX.10.133  Bcast:XXX.XXX.10.255
> Mask:255.255.255.0
>         inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
>         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>         RX packets:196716 errors:0 dropped:0 overruns:0
> frame:1
>         TX packets:82301 errors:0 dropped:0 overruns:0
> carrier:0
>         collisions:0 txqueuelen:1000
>         RX bytes:91072761 (86.8 MiB)  TX bytes:15558692
> (14.8 MiB)
>         Interrupt:18
>
> lo        Link encap:Local Loopback
>         inet addr:127.0.0.1  Mask:255.0.0.0
>         inet6 addr: ::1/128 Scope:Host
>         UP LOOPBACK RUNNING  MTU:16436  Metric:1
>         RX packets:6440 errors:0 dropped:0 overruns:0
> frame:0
>         TX packets:6440 errors:0 dropped:0 overruns:0
> carrier:0
>         collisions:0 txqueuelen:0
>         RX bytes:55534272 (52.9 MiB)  TX bytes:55534272
> (52.9 MiB)
>
> ////////////Start xend
> #xend start
> Nothing to flush.
> Waiting for peth1 to negotiate link.
> # ifconfig
> eth1      Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
>         inet addr:XXX.XXX.10.133  Bcast:XXX.XXX.10.255
> Mask:255.255.255.0
>         inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
>         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>         RX packets:25 errors:0 dropped:0 overruns:0
> frame:0
>         TX packets:40 errors:0 dropped:0 overruns:0
> carrier:0
>         collisions:0 txqueuelen:0
>         RX bytes:3277 (3.2 KiB)  TX bytes:10992 (10.7 KiB)
>
> lo        Link encap:Local Loopback
>         inet addr:127.0.0.1  Mask:255.0.0.0
>         inet6 addr: ::1/128 Scope:Host
>         UP LOOPBACK RUNNING  MTU:16436  Metric:1
>         RX packets:6440 errors:0 dropped:0 overruns:0
> frame:0
>         TX packets:6440 errors:0 dropped:0 overruns:0
> carrier:0
>         collisions:0 txqueuelen:0
>         RX bytes:55534272 (52.9 MiB)  TX bytes:55534272
> (52.9 MiB)
>
> peth1     Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
>         inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
>         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>         RX packets:196767 errors:0 dropped:0 overruns:0
> frame:1
>         TX packets:82358 errors:0 dropped:0 overruns:0
> carrier:0
>         collisions:0 txqueuelen:1000
>         RX bytes:91080163 (86.8 MiB)  TX bytes:15574125
> (14.8 MiB)
>         Interrupt:18
>
> /////////////The peth1 and eth1 are all available and check the bridge...
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> eth1            8000.00a0c9d665db       no              peth1
>
> ///////////The name of the bridge is "eth1" and interface
"peth1" has been
> added to the bridge.
>
> ///////////Configure the configuration file for the guest domain
>
> ************The content of XmGuest.conf*********
> kernel = "/boot/vmlinuz-2.6.18.8-xen-U"
> memory = 256
> name = "ExampleDomain03"
> vif = [ ''mac=00:16:3e:31:48:5f'',
''bridge=eth1'' ]  ###The bridge is given
> name eth1
> disk = [ ''phy:sda7,sda7,w'' ]
> dhcp="off"
> ip=''XXX.XXX.10.134''
> netmask="255.255.255.0"
> gateway="XXX.XXX.10.99" #The gateway is the same as the one used
by dom0
> network.
> hostname="helloworld"
>
> root = "/dev/sda7 ro"
> extra = "4"
> extra = "xencons=tty"
> ***************XmGuest.conf finish here**********************
>
> //////Copy /lib/modules/2.6.18.8-xen/ directory to the guest domain disk.
> There are some exceptions
> //////from guest domain if I don''t do this.
>
> cp -r /lib/modules/2.6.18.8-xen/ /mnt/ubuntu_sda7/lib/modues/
>
> //////Now start the guest domain
>
> # xm create XmGuest.conf
> Using config file "./XmGuest.conf".
> Started domain ExampleDomain03 (id=11)
>
> ///////show xm domains
> # xm list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0   510     2     r-----
> 4443.7
> ExampleDomain03                             11   256     1     -b----
> 9.3
>
> /////////check bridge from dom0
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> eth1            8000.00a0c9d665db       no              vif11.1
>
> vif11.0
>
> peth1
> ///////////The bridge has bounded the guest interface.
>
> ////////////On domU guest
>
> dlzhang@dlzhang-desktop:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:16:3e:31:48:5f
>         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>         RX packets:365 errors:0 dropped:0 overruns:0 frame:0
>         TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>         collisions:0 txqueuelen:1000
>         RX bytes:28617 (28.6 KB)  TX bytes:1368 (1.3 KB)
>
> eth1      Link encap:Ethernet  HWaddr 00:16:3e:08:da:f6
>         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>         RX packets:363 errors:0 dropped:0 overruns:0 frame:0
>         TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>         collisions:0 txqueuelen:1000
>         RX bytes:28085 (28.0 KB)  TX bytes:1368 (1.3 KB)
>
> lo        Link encap:Local Loopback
>         inet addr:127.0.0.1  Mask:255.0.0.0
>         UP LOOPBACK RUNNING  MTU:16436  Metric:1
>         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>         collisions:0 txqueuelen:0
>         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> ///////////The network has not been configured successfully.
> ///////////The eth0 Hardware address is set, but not the ip address
>
> dlzhang@dlzhang-desktop:/etc$ ping XXX.XXX.10.133
> connect: Network is unreachable
>
>
> I have tried with different linux box and different domU, all got the
> similar problem.
>
>
> Would you please give some hints about what might go wrong?
>
>
> Thanks a lot !
>
> Donglai Zhang
>
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.339 / Virus Database: 270.12.75/2182 - Release Date: 06/16/09
> 21:23:00
>
>
>
>
>
> --
> Donglai Zhang
>
> Ph.D Candidate
> School of Computer Science
> University of Adelaide,
> SA, Australia  5083
>
> Tel: 0061 8 83036166
>
>
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.339 / Virus Database: 270.12.75/2182 - Release Date: 06/16/09
> 21:23:00
>


-- 
Donglai Zhang

Ph.D Candidate
School of Computer Science
University of Adelaide,
SA, Australia  5083

Tel: 0061 8 83036166


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

Rustedt, Florian

2009-Jun-17 06:53 UTC

head link

AW: [Xen-users] Can''t get guest domain network working!

Von: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] Im Auftrag von Donglai Zhang
        Gesendet: Mittwoch, 17. Juni 2009 07:46

Did you try to setup the ip manual in the domU? Did you then try to ping
somewhere?

Cheers, Florian
**********************************************************************************************
IMPORTANT: The contents of this email and any attachments are confidential. They
are intended for the
named recipient(s) only.
If you have received this email in error, please notify the system manager or
the sender immediately and do
not disclose the contents to anyone or make copies thereof.
*** eSafe scanned this email for viruses, vandals, and malicious content. ***
**********************************************************************************************


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

Mike Brady

2009-Jun-17 07:10 UTC

head link

Re: [Xen-users] Can''t get guest domain network working!

On Wed, 2009-06-17 at 16:01 +0930, Donglai Zhang wrote:> Hi, 
> 
> Xen version : xen-3.4 
> and guest domain  OS Ubuntu 9.04
> dom0 OS  Fedora release 7 
> The ethernet is: Intel EtherExpress Pro 100B 
> CPU:  Intel(R) Core(TM)2 CPU @2.13GHz. 
> 
> Cheers,
> 
> Donglai 
> 
> On Wed, Jun 17, 2009 at 3:32 PM, Pallab Chakrabarty
> <pchakrabarty@spikesource.com> wrote:
>         
>         
>         This is kernel no, I need xen ver , os make & h/w details..
>         
>         - regards
>            Pallab
>         
>         
>         
>         
>         
>         -----Original Message-----
>         From: Donglai Zhang [mailto:dlzhangster@gmail.com]
>         Sent: Wednesday, June 17, 2009 11:30 AM
>         To: Pallab Chakrabarty; xen-users@lists.xensource.com
>         Subject: Re: [Xen-users] Can''t get guest domain network
>         working!
>         
>         Xen version is 2.6.18.8-xen.
>         
>         regards,
>         
>         Donglai
>         
>         
>         
>         
>         
>         On Wed, Jun 17, 2009 at 3:26 PM, Pallab Chakrabarty
>         <pchakrabarty@spikesource.com> wrote:
>         
>         
>         
>         What''s of your Xen and OS make/ver?
>         
>         - regards
>           Pallab
>         
>         
>         
>         
>         -----Original Message-----
>         From: xen-users-bounces@lists.xensource.com
>         [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of
>         Donglai Zhang
>         Sent: Wednesday, June 17, 2009 11:16 AM
>         To: xen-users@lists.xensource.com
>         Subject: [Xen-users] Can''t get guest domain network
working!
>         
>         Hi, there:
>         
>         I have installed xen(2.6.18.8-xen) and had
>         successfully started domU guests (one or two) from dom0.
>         However, I am
>         not able to start the network for domU machines.
>         
>         Following is the information from my linux box.
>         After the it is started:
>         $ ifconfig
>         eth1      Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
>                 inet addr:XXX.XXX.10.133  Bcast:XXX.XXX.10.255
>         Mask:255.255.255.0
>                 inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
>                 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>                 RX packets:196716 errors:0 dropped:0 overruns:0
>         frame:1
>                 TX packets:82301 errors:0 dropped:0 overruns:0
>         carrier:0
>                 collisions:0 txqueuelen:1000
>                 RX bytes:91072761 (86.8 MiB)  TX bytes:15558692
>         (14.8 MiB)
>                 Interrupt:18
>         
>         lo        Link encap:Local Loopback
>                 inet addr:127.0.0.1  Mask:255.0.0.0
>                 inet6 addr: ::1/128 Scope:Host
>                 UP LOOPBACK RUNNING  MTU:16436  Metric:1
>                 RX packets:6440 errors:0 dropped:0 overruns:0
>         frame:0
>                 TX packets:6440 errors:0 dropped:0 overruns:0
>         carrier:0
>                 collisions:0 txqueuelen:0
>                 RX bytes:55534272 (52.9 MiB)  TX bytes:55534272
>         (52.9 MiB)
>         
>         ////////////Start xend
>         #xend start
>         Nothing to flush.
>         Waiting for peth1 to negotiate link.
>         # ifconfig
>         eth1      Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
>                 inet addr:XXX.XXX.10.133  Bcast:XXX.XXX.10.255
>         Mask:255.255.255.0
>                 inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
>                 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>                 RX packets:25 errors:0 dropped:0 overruns:0
>         frame:0
>                 TX packets:40 errors:0 dropped:0 overruns:0
>         carrier:0
>                 collisions:0 txqueuelen:0
>                 RX bytes:3277 (3.2 KiB)  TX bytes:10992 (10.7 KiB)
>         
>         lo        Link encap:Local Loopback
>                 inet addr:127.0.0.1  Mask:255.0.0.0
>                 inet6 addr: ::1/128 Scope:Host
>                 UP LOOPBACK RUNNING  MTU:16436  Metric:1
>                 RX packets:6440 errors:0 dropped:0 overruns:0
>         frame:0
>                 TX packets:6440 errors:0 dropped:0 overruns:0
>         carrier:0
>                 collisions:0 txqueuelen:0
>                 RX bytes:55534272 (52.9 MiB)  TX bytes:55534272
>         (52.9 MiB)
>         
>         peth1     Link encap:Ethernet  HWaddr 00:A0:C9:D6:65:DB
>                 inet6 addr: fe80::2a0:c9ff:fed6:65db/64 Scope:Link
>                 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>                 RX packets:196767 errors:0 dropped:0 overruns:0
>         frame:1
>                 TX packets:82358 errors:0 dropped:0 overruns:0
>         carrier:0
>                 collisions:0 txqueuelen:1000
>                 RX bytes:91080163 (86.8 MiB)  TX bytes:15574125
>         (14.8 MiB)
>                 Interrupt:18
>         
>         /////////////The peth1 and eth1 are all available and check
>         the bridge...
>         # brctl show
>         bridge name     bridge id               STP enabled
>         interfaces
>         eth1            8000.00a0c9d665db       no              peth1
>         
>         ///////////The name of the bridge is "eth1" and interface
>         "peth1" has been
>         added to the bridge.
>         
>         ///////////Configure the configuration file for the guest
>         domain
>         
>         ************The content of XmGuest.conf*********
>         kernel = "/boot/vmlinuz-2.6.18.8-xen-U"
>         memory = 256
>         name = "ExampleDomain03"
>         vif = [ ''mac=00:16:3e:31:48:5f'',
''bridge=eth1'' ]  ###The
>         bridge is given
>         name eth1
>         disk = [ ''phy:sda7,sda7,w'' ]
>         dhcp="off"
>         ip=''XXX.XXX.10.134''
>         netmask="255.255.255.0"
>         gateway="XXX.XXX.10.99" #The gateway is the same as the
one
>         used by dom0
>         network.
>         hostname="helloworld"
>         
>         root = "/dev/sda7 ro"
>         extra = "4"
>         extra = "xencons=tty"
>         ***************XmGuest.conf finish here**********************
>         
>         //////Copy /lib/modules/2.6.18.8-xen/ directory to the guest
>         domain disk.
>         There are some exceptions
>         //////from guest domain if I don''t do this.
>         
>         cp -r /lib/modules/2.6.18.8-xen/ /mnt/ubuntu_sda7/lib/modues/
>         
>         //////Now start the guest domain
>         
>         # xm create XmGuest.conf
>         Using config file "./XmGuest.conf".
>         Started domain ExampleDomain03 (id=11)
>         
>         ///////show xm domains
>         # xm list
>         Name                                        ID   Mem VCPUs
>            State
>         Time(s)
>         Domain-0                                     0   510     2
>         r-----
>         4443.7
>         ExampleDomain03                             11   256     1
>         -b----
>         9.3
>         
>         /////////check bridge from dom0
>         # brctl show
>         bridge name     bridge id               STP enabled
>         interfaces
>         eth1            8000.00a0c9d665db       no
>          vif11.1
>         
>         vif11.0
>         
>         peth1
>         ///////////The bridge has bounded the guest interface.
>         
>         ////////////On domU guest
>         
>         dlzhang@dlzhang-desktop:~$ ifconfig
>         eth0      Link encap:Ethernet  HWaddr 00:16:3e:31:48:5f
>                 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>                 RX packets:365 errors:0 dropped:0 overruns:0 frame:0
>                 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>                 collisions:0 txqueuelen:1000
>                 RX bytes:28617 (28.6 KB)  TX bytes:1368 (1.3 KB)
>         
>         eth1      Link encap:Ethernet  HWaddr 00:16:3e:08:da:f6
>                 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>                 RX packets:363 errors:0 dropped:0 overruns:0 frame:0
>                 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>                 collisions:0 txqueuelen:1000
>                 RX bytes:28085 (28.0 KB)  TX bytes:1368 (1.3 KB)
>         
>         lo        Link encap:Local Loopback
>                 inet addr:127.0.0.1  Mask:255.0.0.0
>                 UP LOOPBACK RUNNING  MTU:16436  Metric:1
>                 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>                 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>                 collisions:0 txqueuelen:0
>                 RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>         
>         ///////////The network has not been configured successfully.
>         ///////////The eth0 Hardware address is set, but not the ip
>         address
>         
>         dlzhang@dlzhang-desktop:/etc$ ping XXX.XXX.10.133
>         connect: Network is unreachable
>         
>         
>         I have tried with different linux box and different domU, all
>         got the
>         similar problem.
>         
>         
>         Would you please give some hints about what might go wrong?
>         
>         
>         Thanks a lot !
>         
>         Donglai Zhang
Looks to me like this configuration file is trying to boot a Fedora Xen
DomU kernel on an Ubuntu image?  If so that would explain why you are
having to copy over the kernel module files.

I would suggest that you either copy the Ubuntu DomU kernel (and
possibly the initrd) to the Dom0 file system somewhere and specify that
in the kernel= line, or specifiy a 

bootloader="/usr/bin/pygrub"

line instead of the kernel= line so that Ubuntu Xen DomU kernel is
loaded from the guest file system.  The later is the better option in my
opinion.

It is odd that the DomU is showing 2 interfaces when only one is
defined, but lets make sure that the correct kernel/modules are loaded
first.

Regards

Mike


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

Donglai Zhang

2009-Jun-18 07:46 UTC

head link

Re: [Xen-users] Can''t get guest domain network working!

Hi, Rustedt:

I tried to setup the ip manually in domU and it works. But once the domU is
created by the xm command,  the ifcfg-eth0 turns into ifcfg-eth0.bak, but
there is no new ifcfg-eth0 under the network-script directory.

Donglai


On Wed, Jun 17, 2009 at 4:23 PM, Rustedt, Florian <
Florian.Rustedt@smartnet.de> wrote:
>        Von: xen-users-bounces@lists.xensource.com [mailto:
> xen-users-bounces@lists.xensource.com] Im Auftrag von Donglai Zhang
>        Gesendet: Mittwoch, 17. Juni 2009 07:46
>
> Did you try to setup the ip manual in the domU? Did you then try to ping
> somewhere?
>
> Cheers, Florian
>
>
**********************************************************************************************
> IMPORTANT: The contents of this email and any attachments are confidential.
> They are intended for the
> named recipient(s) only.
> If you have received this email in error, please notify the system manager
> or the sender immediately and do
> not disclose the contents to anyone or make copies thereof.
> *** eSafe scanned this email for viruses, vandals, and malicious content.
> ***
>
>
**********************************************************************************************
>
>

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

Fajar A. Nugraha

2009-Jun-18 07:59 UTC

head link

Re: [Xen-users] Can''t get guest domain network working!

On Thu, Jun 18, 2009 at 2:46 PM, Donglai Zhang
<dlzhangster@gmail.com>wrote:
> Hi, Rustedt:
>
> I tried to setup the ip manually in domU and it works. But once the domU is
> created by the xm command,  the ifcfg-eth0 turns into ifcfg-eth0.bak, but
> there is no new ifcfg-eth0 under the network-script directory.
>
Usually that''s because domU''s eth0 MAC address change. You
need to specify
static MAC. Something like this on domU config file:

vif =    [
    ''mac=00:16:3E:D9:D9:40, bridge=xenbr0'',
    ]


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

Donglai Zhang

2009-Jun-18 08:06 UTC

head link

Re: [Xen-users] Can''t get guest domain network working!

Hi,

Yes,  I also tested with centos it has the same problem, it turns out that
the two interfaces is a problem with
my configuration file,  I have changed that from:
vif = [ ''mac=00:16:3e:31:48:5f'',
''bridge=eth1'' ]

To:

vif = [ ''mac=00:16:3e:31:48:5f, bridge=eth0'' ]
and now it only show one interface in guest domain.


By copying the kernel and image file from Ubuntu to the dom0 and use them to
create a new guest domain got this message:
# xm create xm03dlzhang
Using config file "./xm03dlzhang".
Error: (2, ''Invalid kernel'', ''elf_xen_note_check:
ERROR: Will only load
images built for the generic loader or Linux images'').
Any idea?


Thanks,

Donglai



Looks to me like this configuration file is trying to boot a Fedora
Xen> DomU kernel on an Ubuntu image?  If so that would explain why you are
> having to copy over the kernel module files.
>
> I would suggest that you either copy the Ubuntu DomU kernel (and
> possibly the initrd) to the Dom0 file system somewhere and specify that
> in the kernel= line, or specifiy a
>
>
> bootloader="/usr/bin/pygrub"
>
> line instead of the kernel= line so that Ubuntu Xen DomU kernel is
> loaded from the guest file system.  The later is the better option in my
> opinion.
>
> It is odd that the DomU is showing 2 interfaces when only one is
> defined, but lets make sure that the correct kernel/modules are loaded
> first.
>
> Regards
>
> Mike
>
>

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

Apparently Analagous Threads

Search for more apparently analagous threads

Xen users - Jun 2009 - Can''t get guest domain network working!

[Xen-users] Can''t get guest domain network working!

Re: [Xen-users] Can''t get guest domain network working!

Re: [Xen-users] Can''t get guest domain network working!

AW: [Xen-users] Can''t get guest domain network working!

Re: [Xen-users] Can''t get guest domain network working!

Re: [Xen-users] Can''t get guest domain network working!

Re: [Xen-users] Can''t get guest domain network working!

Re: [Xen-users] Can''t get guest domain network working!

Apparently Analagous Threads