1) There isn't a paid support channel so far as I know of, so some people tend to look down on it. RHEL/RHEV, and Red Hat Storage Server while costing more, might make people feel more comfortable in the fact that they are going to have a number to call on if things are out of skew (or if you leave the business, and others need to support/maintain the project).
2) What I believe to be the normal route, and how I have configured our networking with KVM: you have N interfaces (usually N=8 for us), and you bond together N-1 (7 bonded together, and then connected to br0), then bridge that bond of interfaces. The last one you leave alone for management/physical host access. The red hat documentation online is a huge help in setting all of that up: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-Using_Channel_Bonding.html and https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html Hope that helps! On Mon, Dec 24, 2012 at 4:24 AM, Jamie Duncan <[email protected]>wrote: > https://access.redhat.com/knowledge/solutions/18734 > On Dec 23, 2012 10:01 PM, "CS DBA" <[email protected]> wrote: > >> Hi All; >> >> 2 questions: >> >> 1) I'm considering using KVM for Virtual Machines in a production >> environment. >> Good plan? Any drawbacks? better choices? >> >> >> 2) I've found many guides on the web for setting up the bridged networks >> but most seem incomplete or they do not work >> can someone help me understand end 2 end what I should do to create a >> new bridge interface and make it available for KVM's? >> >> >> Thanks in advance >> >
