[OpenNode-users] Networking issues with KVM machines made with virt-manager

[<ope...@li...>]

Greetings,

I'm trying to use virt-manager to create and manage KVM VMs on OpenNode.  virt-manager doesn't seem to be aware that bridged networking is setup and defaults to providing private DHCP addresses to the VMs one creates.  It seems that virt-manager is expecting one bridge setup in order to do public/static IPs and OpenNode sets up the bridging different.  Perhaps it is just a matter of using a particular bridge device name.  On my OpenNode machine I have two bridge devices:

vmbr0 - Has the public IP assigned by OpenNode
virbr0 - Has the private IP (192.168.122.1) setup by virt-manager

At least I think that is what is going on.

I realize that the OpenNode developers are working on a web-based management system... and that there are alternative management tools other than virt-manager... but it is installed and it would be nice if it was pre-configured in a working fashion.

I was able to create KVM VM just fine with virt-manager, it just has semi-functional networking because only private IPs and NATing works.

I don't know enough about the underlying config of virt-manager to fix it... other than creating a bridge device named br0 and giving it the public IP of the machine... bypassing the bridge device that OpenNode has created/configured.  I haven't done that yet but I assume it would work since that's what I do on other Red Hat-based distros with KVM/virt-manager (RHEL 5.4 and Fedora 9, 10, 11, and 12).

I also created an OpenVZ container with my own OS Template (rather than using those provided by OpenNode) and it worked fine.  I realize that if I try the fix mentioned in the previous paragraph I'd have to edit the /etc/sysconfig/network-scripts/ifcfg-venet0 file to tell it to use the br0 instead of venet0.

Any suggestions?

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]