Re: [libvirt] how do I stop libvirt futzing with my network configuration?

On 28 Nov 2009, Ian Woodstock spake thusly: That's the mystery. I did it (directly via brctl, as it happens, 'cos I'm making several with particular properties and want to enforce them): spindle:/etc/libvirt/qemu# brctl show bridge name bridge id STP enabled interfaces linux-net 8000.06eb4e4985df no dummy0 [...] 52: linux-net: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN link/ether 06:eb:4e:49:85:df brd ff:ff:ff:ff:ff:ff inet 192.168.20.1/32 scope global linux-net (hm, the state UNKNOWN is sort of bizarre. It's up...) (dummy0 is a member of this bridge because I've previously noted that a bridge with no members at all isn't picked up by the GUI). It appears in the GUI, all right: as 'host device linux-net (not bridged)', greyed out and unselectable. Calling a bridge 'not bridged' is more than slightly bizarre. Perhaps the netcf thing means I'm *required* to stick stuff in /etc/sysconfig/network-scripts even though I'm not using RH so it would never otherwise be used? From my reading of the source, that's not so... I suppose I should just have it check for the bridge and rip out all this other stuff, but it seems bizarre that I have to do it. That's too late to run the installer if it needs to access the network :/ I suppose I could continue doing the VM installation qemu run by hand... There's no iptables at all on this particular box (at least not yet, although it may turn up later on when I put Windows guests on here: I'm not having *them* running around free).