Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Having built a Centos server using eth0 as the wan and eth1 mapped to br1 as the lan for KVM the firewall prevents Samba from being recognised by other clients on br1. I've tried firestarter, shorewall and the inbuilt firewall within Centos - all have trouble with the bridging of eth1 to br1 in that they need to be turned off for it to work. Setting the rules for Samba has no effect. The virtualized guest is either Win 2003 server or Win XP pro configured for the correct workgroup netbios name. It seems iptables can't handle the complexity of the bridge. Anyone else had this problem or knows of a workaround?
Rebuilding the machine has fixed the problem. I can only put this down to the many differing howtos that were tried in getting KVM configured in bridge mode in the first place. Using the Package Manager to just install KVM (not Virtualization) was a start.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.