[virt-tools-list] Several problems with the management of network interface. (virsh iface-define, virsh iface-start and with virt-manager)

[Cole Robinson]

cc-ing netcf-devel

On 06/05/2011 11:09 AM, Lionel Schaub wrote:
> I have already post this bug here
> https://bugzilla.redhat.com/show_bug.cgi?id=709734
> 
> but I did not answer.
> 
>  
> 
>  
> 
> Description of problem:
> 
> 1. The execution of the command "virsh iface-start br1" (br1 interface is
> 
> obtained with "virsh iface-define") takes 10 minutes.
> 
> 2. After restarting the machine, the interface does not start automatically
> 
> even though I specified the parameter <start mode="onboot"/>. I have to
> 
> manually run the command "virsh iface-start br1".
> 
>  
> 
> If I create the interface with virt-manager, I have the same problems and
> the
> 
> process takes about 20 minutes.
> 
>  
> 
>  
> 
> Version-Release number of selected component: 
>  I have found the 0.8.8 version of libvirt and virsh in this repository:
> <https://fedoraproject.org/wiki/Virtualization_Preview_Repository>
> https://fedoraproject.org/wiki/Virtualization_Preview_Repository.
>  I use this version because the 0.8.3 has a third bug.
> 
> Fedora 14
> 
> Linux Kernel 2.6.35.13-91.fc14.x86_64
> 
> libvirt 0.8.8
> 
> virsh 0.8.8
> 
> virt-manager 0.8.7
> 
> bridge-utils 1.2
> 
>  
> 
>  
> 
> Steps to Reproduce:
> 
> 1. Create the file bridgeInterfaceConfig.xml (change interface, ip and mac
> to
> 
> correspond to your configuration)
> 
>   <interface type='bridge' name='br1'>
> 
>     <start mode="onboot"/>
> 
>     <protocol family='ipv4'>
> 
>       <ip address='192.168.1.15' prefix='24'/>
> 
>     </protocol>
> 
>     <bridge>
> 
>       <interface type='ethernet' name='eth2'>
> 
>         <mac address='00:1b:21:43:36:b0'/>
> 
>       </interface>
> 
>     </bridge>
> 
>   </interface>
> 
> 2. launch "virsh iface-define bridgeInterfaceConfig.xml"
> 
> 3. launch "iface-start br1". this step take 10 minutes.
> 
> 4. restart the computer and see that the br1 interface no longer exists.
> 
> 5. you can do the same with virt-manager.
>