On Wed, Apr 11, 2012 at 9:51 AM, Ben Pfaff <b...@nicira.com> wrote: > On Tue, Apr 10, 2012 at 02:32:48PM -0700, Ansis Atteka wrote: > > Add documentation on how to use OVS integration > > with the upcoming Libvirt 0.9.11 release. > > Thanks for writing this! > > Here, you might consider adding something like "or you installed Open > vSwitch from distribution packaging such as a .deb or .rpm", since > that's usually the easiest way to get OVS going: > > +scripts. This document assumes that you followed INSTALL.Linux to get > Open > > +vSwitch setup on your Linux system and have libvirt 0.9.11 or later > > +installed. The Open vSwitch support is included by default in Libvirt. > > +Consult www.libvirt.org for instructions on how to build the latest > Libvirt. > > I'd write "for" instead of "per" here: > > +Lookup in the Domain XML file the <interface> section. There should be > one > > +such XML section per each interface the VM has. > > Assuming this is just regular XML, it would save the user a bit of > typing to, instead of: > > + <virtualport type='openvswitch'> > > + </virtualport> > to write: > <virtualport type='openvswitch'/> > > Do we know of any common problems that we could explain how to solve > in the Troubleshooting section? > As of now, it's hard to tell what exactly could be confusing to users who would like to try this new feature. I added Troubleshooting section so that they would be encouraged to also look into libvirt errors.
One possible issue I see is that if ovs-vsctl is not in the system path (e.g. user started OVS immediately after "make" and didn't do "make install") Another issue could be with VM migration, where the other hypervisor does not have ovsbr bridge (I haven't tried this). All of Kyle's feedback sounds good to me too. (Thanks Kyle!) >
_______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
