Note that this is the case for the standard VMware ESX vSwitch. However, the Cisco Nexus 1000v,
which is an optional virtual switch for ESX, does appear to provide (guest) VM firewall capabilities.
See for example the section on "isolation and protection" and ACLs in the link below:
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/dmz_virtualization_vsphere4_nexus1000V.pdf
In terms of interfaces, the 1000v claims a CLI (likely similar to physical Cisco switches), support for SNMP
and an XML API.
Thanks,
Dimitrios
Matthias Bolte ---01/13/2010 05:43:41 PM---2010/1/13 Stefan Berger <stefanb@xxxxxxxxxx>: >
 From: | Matthias Bolte <matthias.bolte@xxxxxxxxxxxxxx> |
To: | Stefan Berger/Watson/IBM@IBMUS |
Cc: | Gerhard Stenzel <gerhard.stenzel@xxxxxxxxxx>, libvir-list@xxxxxxxxxx, Vivek Kashyap/Beaverton/IBM@IBMUS |
Date: | 01/13/2010 05:43 PM |
Subject: | Re: [libvirt] [RFC] Proposal for introduction of network traffic filtering capabilities for filtering of network traffic from and to VMs |
Sent by: | libvir-list-bounces@xxxxxxxxxx |
2010/1/13 Stefan Berger <stefanb@xxxxxxxxxx>:
>
> Daniel Veillard <veillard@xxxxxxxxxx> wrote on 01/13/2010 12:03:22 PM:
>
>> On Mon, Jan 11, 2010 at 12:55:27PM -0500, Stefan Berger wrote:
>> > Hello!
>> >
> [...]
[...]
>> other case of limitiations could be found. Also this may not map well
>> for other kind of hypervisors like VMWare, right ?
>
> I don't know much about the API that VMWare is exposing. Maybe only a
> certain subset of what would be possible with this XML could be applied
> to their API, if such functionality exist. Otherwise, if libvirt
> can run ebtables and iptables commands on their management VM and
> all traffic passes through VM=specific network interface (tap) in that VM,
> it *should* work as well.
VMware ESX hosts allow to configure the host level firewall via the
remote VI API. But AFAIK there is no virtual machine level firewall.
You're not supposed to do something like that in the service console,
doing anything in the service console is not supported in general.
Also there is no libvirtd in the service console because of that and
because it is not necessary. The ESX driver does everything using the
remote VI API.
Matthias
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list