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

[Xen-users] Bridging with 2 network interfaces - Fedora 8 Kickstart installation


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Caron, Chris" <caronc@xxxxxxxxxxxx>
  • Date: Tue, 26 Feb 2008 14:03:25 -0500
  • Delivery-date: Tue, 26 Feb 2008 11:04:17 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Ach4qkL3ZPnE9uUVSZmvE+549tA5CA==
  • Thread-topic: Bridging with 2 network interfaces - Fedora 8 Kickstart installation

Hello everyone,

 

I can’t seem to figure out why when I specify a kick-start; the network can never be found on a dual bridged xen setup…

However if I do the installation manually it works smoothly….

 

My configuration;

Xen version 3.1.0-rc7-2950.fc8

running on Fedora 8

 

The command I’m using to do the kickstart install is:

virt-install -n test -r 256 \

  -f /var/xen/default/test-default.dsk -s 5 \

  -f /var/xen/default/test-swap.dsk -s 5 \

  -p --location=http://10.1.1.1/cldn \

  --nographics \

  --bridge=eth0 --mac=00:16:3e:00:00:00 \

  --bridge=eth1 --mac=00:16:3e:00:00:01 \

  --os-type='linux' \

  --vcpus=1 \

  -x "ks=http://10.1.1.1/cldn01-ks.cfg"

 

(even without reference to the second bridge it doesn’t work)

In the kickstart file; I set the address I want the virtual machine to assume (for ethernet 0)

If I do a manual install and specify these entries, everything seems to work… but this link (supposedly automating the install) does not work:

 

network --bootproto=static --device=eth0 --ip=10.1.1.2 --netmask=255.255.255.0--gateway=10.1.1.250 -- --hostname=cldn01.c1

 

First I get stuck on this screen (with the kickstart)

------

 

Welcome to Fedora for i386

 

 

 

                   +---------+ Networking Device +----------+

                   |                                        |

                   | You have multiple network devices on   |

                   | this system. Which would you like to   |

                   | install through?                       |

                   |                                        |

                   |      eth0 - Xen Virtual Ethernet       |

                   |      eth1 - Xen Virtual Ethernet       |

                   |                                        |

                   |      +----+             +------+       |

                   |      | OK |             | Back |       |

                   |      +----+             +------+       |

                   |                                        |

                   |                                        |

                   +----------------------------------------+

 

 

 

 

  <Tab>/<Alt-Tab> between elements  | <Space> selects | <F12> next screen

 

 

After I choose eth0 (as this is the network I install from the http server) it hangs forever here…

Welcome to Fedora for i386

 

 

 

 

 

 

 

 

           +-------------------------------------------------------+

           |                                                       |

           | Sending request for IP information for eth0...        |

           |                                                       |

           +-------------------------------------------------------+

 

 

 

 

 

 

 

 

 

  <Tab>/<Alt-Tab> between elements  | <Space> selects | <F12> next screen

… I specifically set the bootproto to ‘not’ use dhcp yet it still persists to run…

 

Here is my network information:

 

eth0      Link encap:Ethernet  HWaddr 00:22:43:EB:15:79

          inet addr: 10.1.1.1  Bcast: 10.1.1.255  Mask:255.255.255.0

          inet6 addr: fe80::211:43ff:feeb:1579/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1780014 errors:0 dropped:0 overruns:0 frame:0

          TX packets:825913 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:437644968 (417.3 MiB)  TX bytes:572632433 (546.1 MiB)

 

eth1      Link encap:Ethernet  HWaddr 00:22:43:EB:15:7A

          inet addr:172.1.0.2  Bcast:172.1.255.255  Mask:255.255.0.0

          inet6 addr: fe80::211:43ff:feeb:157a/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1084056 errors:0 dropped:0 overruns:0 frame:0

          TX packets:160 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:344078469 (328.1 MiB)  TX bytes:11698 (11.4 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:1563262 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1563262 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:3170783887 (2.9 GiB)  TX bytes:3170783887 (2.9 GiB)

 

peth0     Link encap:Ethernet  HWaddr 00:11:43:EB:15:79

          inet6 addr: fe80::211:43ff:feeb:1579/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1821237 errors:0 dropped:0 overruns:0 frame:0

          TX packets:826115 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:472306027 (450.4 MiB)  TX bytes:575959158 (549.2 MiB)

          Interrupt:18

 

peth1     Link encap:Ethernet  HWaddr 00:11:43:EB:15:7A

          inet6 addr: fe80::211:43ff:feeb:157a/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1125669 errors:0 dropped:0 overruns:0 frame:0

          TX packets:166 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:366268811 (349.3 MiB)  TX bytes:14656 (14.3 KiB)

          Interrupt:19

 

 

My bridges appear to be in place as well:

 

$>brctl show

bridge name     bridge id               STP enabled     interfaces

eth0            8000.001143eb1579       no              peth0

eth1            8000.001143eb157a       no              peth1

 

 

This is my custom bridge script:

#!/bin/sh

dir=$(dirname "$0")

"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=eth0

"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=eth1

 

 

 

Perhaps my problem is related to the fact that netdev = the bridge?

 

eth0 and eth1 have aliases in my etc/modprob.conf… could they be conflicting?

Originally I was having problems using the xenbr0 and xenbr1 bridges…. It was always leaving a tmpbridge in my network and never setting up the bridges properly.

 

What am I doing wrong?

 

Chris

 

_______________________________________________
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®.