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.
I have a xen server and need to setup a trunk allowing me to specify different IP's for each of the VM's connected. The port the dom0 is connected is already trunk aware.
What do I need to do to make this function properly? Are there any guides/walkthroughs?
Not following how making eth0 vlan aware would solve the problem though?
You basically want each VM virtual NIC to share your physical network card; but assign (either dynamic/static) different IP's to these. Bridging really isn't that difficult to do. All you'd need to do is to install bridge-utils and do a bit of interface config.
This link is for setting up KVM on Fedora 10; but I've used a similar way of doing it on F13/F14 and it works perfectly - this will give you an idea of how to setup the bridge.
Not following how making eth0 vlan aware would solve the problem though?
I want my switch to deal with intervlan communication, not the xen server. If my VM's have an obscure IP address, data will be forwarded out the virtual interface and sent to the dom0 interface which will push traffic to the switch to handle... I was hoping anyway. I've noticed when doing ifconfig -a that there's already - eth0, vif3.0 and xenbr0...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.