On 04/29/2011 06:26 PM, Teck Choon Giam wrote:
> On Sat, Apr 30, 2011 at 6:08 AM, Digimer <linux@xxxxxxxxxxx> wrote:
>> Hi all,
>> While trying to sort out/test some patches, I was told that it's best
>> to create bridges manually in
>> /etc/sysconfig/network-scripts/ifcfg-xenbr*. I did this, commented out
>> (network-script network-bridge) and restarted the network and Xen.
> Yes, using system network configuration will be better. Which
> distribution is this? CentOS/RHEL 5?
> You commented out (network-script network-bridge)? If you are using
> system network configuration to configure your bridge, have you try
> the following instead of commented out?
> (network-script /bin/true)
That was the ticket. I was able to provision a new VM with two
interfaces, however, the vifs were at MTU 1500 so I still have work to
>> With the bridges manually in place, and no longer having 'pethX'
>> devices, I tried to provision a VM and it failed with:
>> # virt-install --connect xen --name vm0002_pppoe --ram 2048 --arch
>> x86_64 --vcpus 1 --cpuset 1-7 --location http://10.255.0.1/f9/x86_64/img
>> --os-type linux --os-variant rhel5.4 --disk
>> path=/dev/drbd_x4_vg0/vm0002_1 --network bridge=xenbr0 --network
>> bridge=xenbr2 --vnc --paravirt --debug
> brctl show outout?
> Is your manual ifcfg-xenbr0 a bridge to ifcfg-eth0 and ifcfg-xenbr2 a
> bridge to ifcfg-eth2?
> Where is your ifcfg-eth1 and ifcfg-xenbr1? Normal network
> configuration will have ifcfg-eth* in order... ...
I use eth1 on the dom0's as storage-only interfaces. As such, they'll
never be used by a domU, so I don't bother bridging them.
> It is hard to tell what went wrong without seeing the following outputs:
> brctl show
> ip link
> Kindest regards,
> Giam Teck Choon
If I run into more problems, I'll be sure to include the output from
those. Thanks again, that /bin/true was the ticket. :)
Node Assassin: http://nodeassassin.org
Xen-users mailing list