Bugzilla Bug 194224

I couldn't get networking to work in domUs. See below.

Reproducible: Always

Steps to Reproduce:
emerge iproute2 with USE="minimal"
Actual Results:  
When creating a domU I always got

Error: Device 0 (vif) could not be connected. Could not find bridge device
xenbr0

Expected Results:  
Created and connected the virtual interface to the bridge (which was present in
ifconfig -a all the time).

So don't do it, what exactly are you expecting here?

I guess I could die on install if iproute2 was built with minimal, but I would
bet lots of random crap breaks in general when a system is built with the
minimal use flag.

> So don't do it, what exactly are you expecting here?

I had no clue what was wrong and came across the source of the problem by
accident. There should be a pointer somewhere that xen needs ip (or whatever)
to work correctly.

(In reply to comment #3)
> > So don't do it, what exactly are you expecting here?
> 
> I had no clue what was wrong and came across the source of the problem by
> accident. There should be a pointer somewhere that xen needs ip (or whatever)
> to work correctly.
> 

K, next time I update the ebuild I'll add a check and a big fat warning to
catch that.

In general I would recommend not using the minimal use flag unless you know
exactly what functionality it is stripping for a package and you are worried
about space (ie tiny embedded systems).

Okay, thank you :)

Alexander, this is not a 'major' bug. Stop making it one.

I think "major loss of function" is a pretty good description of not being able
to use networking with Xen and not knowing why. I bet I'm not the only one who
built a dom0 with USE="minimal".

Updated xen-tools-3.1.0-r1 to issue a warning if iproute2 was built with
USE=minimal. Closing.