On Wed, Apr 20, 2011 at 06:48:18AM -0700, Decker, Schorschi wrote: > As we continue to automate (current) version of virt-manager, what would > be the best method to establish volumes and network connectivity? > > Obviously we can automate the creation of a physical NIC bridge, which > is our desired method for VM connectivity outside of the KVM host, and > we can reference said bridge interface as we build VMs. However, are > there any side-effects to this method we should know about?
The only immediate thing I can think of is the firewall rules the libvirtd adds. You'd want to check that libvirtd is (or is not?) creating the right rules for you. Also note that if you restart the firewall, all the libvirtd rules get thrown out and your guests can't talk to each other (RHBZ#227011). > Same basic question for mount points to shared storage between KVM > hosts. We plan to use NAS/NFS initially, some day we might use SAN > infrastructure. Creating the mount points is straight forward from an > automation perspective, but to get virt-manager to see these volumes, > any issues we should be aware of? Take into consideration? I can't think of any issues. > Anyone that has done this before? Figure we can benefit from lessons > learned? As always thanks for the assistance. If you want precise control over how guests are created, use virt-install or even create/edit libvirt XML directly from your scripts. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top _______________________________________________ virt-tools-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-tools-list
