bridge networking busted?

[Tom Horsley]

I got the latest updates (as far as I know), running
virt-manager-0.9.5-1.fc18.noarch

When I tried to install a minimal fedora 18 virtual
machine, virt-manager said "no network".

I've got 2 different bridges on my host, and it
wouldn't offer either one.

I had to install the machine and edit the xml
later to add a bridged network device.

Is this a known bug? Is it likely to get fixed
sometime? It is pretty irritating.

[Cole Robinson]

On 04/19/2013 10:08 AM, Tom Horsley wrote:
>  I got the latest updates (as far as I know), running
>  virt-manager-0.9.5-1.fc18.noarch
>  
>  When I tried to install a minimal fedora 18 virtual
>  machine, virt-manager said "no network".
>   
If you look at the drop down under 'advanced options' at the end of the new VM
wizard, there should be an option to manually enter a bridge. At least for a
temporary work around.

>  I've got 2 different bridges on my host, and it
>  wouldn't offer either one.
>  
>  I had to install the machine and edit the xml
>  later to add a bridged network device.
>  
>  Is this a known bug? Is it likely to get fixed
>  sometime? It is pretty irritating. 
What's the output of

sudo virsh --connect qemu:///system iface-list --all

- Cole

[Tom Horsley]

>  > When I tried to install a minimal fedora 18 virtual
>  > machine, virt-manager said "no network".
>  > 
>  
>  If you look at the drop down under 'advanced options' at the end of the new VM
>  wizard, there should be an option to manually enter a bridge. At least for a
>  temporary work around. 
Didn't bother to try advanced options since "no network"
seemed too final :-). I'll check it next time.

>  What's the output of
>  
>  sudo virsh --connect qemu:///system iface-list --all 
Name                 State      MAC Address
--------------------------------------------
bifrost              active     14:da:e9:72:9e:22
br0                  active     14:da:e9:72:9e:22
eth0                 inactive   
lo                   active     00:00:00:00:00:00
p6p1                 active     14:da:e9:72:9e:22

bifrost and br0 are bridges on two different vlans
(one of which has access to my local LAN and the other
of which only has access to the outside world
for use with dangerous browsing :-).

That listing doesn't mention the vlans p6p1.1 and p6p1.3.

[Cole Robinson]

On 04/20/2013 06:08 PM, Tom Horsley wrote:
> >> When I tried to install a minimal fedora 18 virtual
> >> machine, virt-manager said "no network".
> >>
> >
> > If you look at the drop down under 'advanced options' at the end of the new
> VM
> > wizard, there should be an option to manually enter a bridge. At least for a
> > temporary work around.
>  
>  Didn't bother to try advanced options since "no network"
>  seemed too final :-). I'll check it next time.
>  
> > What's the output of
> >
> > sudo virsh --connect qemu:///system iface-list --all
>  
>  Name                 State      MAC Address
>  --------------------------------------------
>  bifrost              active     14:da:e9:72:9e:22
>  br0                  active     14:da:e9:72:9e:22
>  eth0                 inactive   
>  lo                   active     00:00:00:00:00:00
>  p6p1                 active     14:da:e9:72:9e:22
>   
Not sure if eth0 being inactive here screws stuff up, could be virt-manager
error though. Next time you reproduce, please run with 'virt-manager --debug'
and post the output here.

Thanks,
Cole

[Tom Horsley]

On Sat, 20 Apr 2013 18:47:39 -0400
Cole Robinson wrote:

>  Not sure if eth0 being inactive here screws stuff up 
I don't even have an eth0. It apparently just made that up :-).

[Laine Stump]

On 04/20/2013 07:17 PM, Tom Horsley wrote:
>  On Sat, 20 Apr 2013 18:47:39 -0400
>  Cole Robinson wrote:
>
> > Not sure if eth0 being inactive here screws stuff up
>  I don't even have an eth0. It apparently just made that up :-). 
You must have an ifcfg-eth0 file left around from [some previous
adventure] in /etc/sysconfig/network-scripts. Interfaces can only be
listed by iface-list if they have an associated ifcfg file, and if they
are not attached to a bridge or a bond.

[Tom Horsley]

On Sun, 21 Apr 2013 14:48:19 -0400
Laine Stump wrote:

>  You must have an ifcfg-eth0 file left around from [some previous
>  adventure] in /etc/sysconfig/network-scripts. 
Yep, there is an ifcfg-eth0 file, but it doesn't show up
in ifconfig -a, and the HWADDR it lists doesn't exist.

It seems to be leftover from the way I installed f18,
copying a VM install to my hard disk partitions (since
the f18 installer was utterly impossible to decypher
or trust not to destroy my system :-).