[libvirt] Network Interface: How to disable virbr0 correctly?

[Jake Xu]

On Tue, Mar 8, 2011 at 11:20 AM, Matthias Bolte <
matthias.bolte at googlemail.com> wrote:

> 2011/3/8 Jake Xu <jake at demonwaremail.net>:
> > Hi Cole,
> > Thanks for the wiki link. It would be so useful if the ESX driver
> supported
> > those commands. It seems like the ESX driver does not support most of the
> > network or interface configuration.
>
> What do you mean by " those commands"?
>
> The problem with implementing ESX networking support in libvirt is
> that ESX's and libvirt's network model don't match directly and it's
> not entirely clear how two map those two in a useful way.
>
> Can you be more specific about what you need in terms of network
> management?
>
> Sorry if I did not make it clear. For commands, I meant the net-list,
net-destroy, etc commands in virsh.

I am actually using the libvirt Python-bindings to write scripts which
automate the VM creation process. All I need in terms of network management
is that I want it to have two interfaces eth0 and eth1 with static ip
addresses(gateway, subnet, etc), so I don't need any other extra
configuration such as virtbr0 provided by libvirt/libvirtd daemon. Is there
any way to prevent libvirtd daemon being installed on the guest VM?


> > Regarding the eth1 interface, I am not sure why the autostart.xml could
> > affect bringing up eth1. Before I made changes to the autostart.xml or
> > renamed the folder completely, the VMs have all interfaces installed:
> eth0,
> > eth1, virbr0 (even though the virbr0 and its iptable rules seem to be a
> bit
> > difficult to get rid of). After I renamed the autostart folder, I was
> able
> > to remove the virbr0 interface and iptable rules, but the eth1 can't be
> > brought up successfully as described in the opening post.
> > Thanks,
> > Jake
>
> Are you installing libvirt inside the VMs and running libvirtd? Why
> are you doing that?
>
> Matthias
>
> No. I am running libvirt with its Python-bindings on a Ubuntu PC, and
remotely creating VMs on ESX server. Since I am creating VMs on ESX server,
I don't really need libvirtd. It would be nice if I can disable libvirtd
before it's being installed on VMs.

Thanks so much for your help,

Jake

> On Tue, Mar 8, 2011 at 6:31 AM, Cole Robinson <crobinso at redhat.com> wrote:
> >>
> >> On 03/07/2011 04:32 PM, Jake Xu wrote:
> >> > Hi all,
> >> >
> >> > Recently, I have been using libvirt to create virtual machines on ESX
> >> > servers. It has been very well until to the point where I couldn't
> find
> >> > any
> >> > way to disable/remove the virbr0 interface properly.
> >> >
> >> > We use static configuration for VMs on ESX so we do not need to use
> >> > virbr0
> >> > interface and we do not want libvirt to configure iptables as a result
> >> > of
> >> > the newly created virbr0 interface.
> >> >
> >> > I have tried to remove/rename the
> >> > /etc/libvirt/qemu/networks/autostart.xml
> >> > file, and that prevents virbr0 being installed.
> >> >
> >>
> >> Here is how to properly remove steps virbr0 (the default virtual
> network):
> >>
> >>
> >>
> http://wiki.libvirt.org/page/FAQ#How_can_I_make_libvirt_stop_using_iptables.3F
> >>
> >> > However, that also seems to prevent the second interface eth1 being
> >> > configured properly. After libvirt defines a VM, eth0 and eht1 are
> both
> >> > installed, but only eth0 is configured properly.
> >> >
> >> > The eth1 does not appear in the
> /etc/sysconfig/network-script/ifcfg-xxx
> >> > file. It seems to me that the 'autostart.xml' file interrupts the
> >> > configuration of the eth1 interface.
> >> >
> >>
> >> Not sure why autostarting a virtual network would also bring up eth1, so
> >> no ideas there.
> >>
> >> - Cole
> >
> >
> > --
> > libvir-list mailing list
> > libvir-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/libvir-list
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20110308/e2179333/attachment-0001.htm>