<div dir="ltr">On Fri, Aug 15, 2014 at 10:40 AM, CrankyOldBugger <span dir="ltr"><<a href="mailto:crankyoldbugger@gmail.com" target="_blank">crankyoldbugger@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div><div>virbr0 Link encap:Ethernet HWaddr ca:e3:65:49:dc:e4 </div>
<div> inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0</div><div> UP BROADCAST MULTICAST MTU:1500 Metric:1</div><div> RX packets:0 errors:0 dropped:0 overruns:0 frame:0</div>
<div> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0</div><div> collisions:0 txqueuelen:0 </div><div> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)</div><div><br></div></div><div><br></div><div>
Don't ask me why virbr0 is there. (Google tells me it's there because I started tinkering with KVM at some point but I never finished the task.) </div></div></blockquote><div><br></div><div>Yes, I have that too, and yes, it is caused by libvirt/kvm. And it is not from configuration in /etc/network/interfaces.<br>
</div><div dir="rtl"> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I want to start building virtual machines on this box, but before I do I would like to see the server using both NIC cards appropriately. </div>
</blockquote><div><br>You can make both cards work by putting something like this in your /etc/network/interfaces<br><br><br>auto eth0<br>iface eth0 inet dhcp<br><br>auto eth1<br>iface eth1 inet dhcp<br><br>The above will make both interfaces come up at boot, and configure themselves via DHCP, so the router assigns them an IP address, ...etc<br>
<br></div><div>Or you can assign that manually using something like:<br><br>auto eth0<br>iface eth0 inet static<br> address 192.168.0.2<br> netmask 255.255.255.0<br> network 192.168.0.0<br> broadcast 192.168.0.255<br>
gateway 192.168.0.1<br><br>auto eth1<br>iface eth1 inet static<br> address 192.168.0.3<br> netmask 255.255.255.0<br> network 192.168.0.0<br> broadcast 192.168.0.255<br> gateway 192.168.0.1<br>
<br></div><div>This means the first NIC will get 192.168.0.2 and the second will be .3, assuming that the router is at .1.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">By that I mean it will share the load between any future VMs between the two NICs, </div></blockquote><div><br></div><div>I am not sure what share the load means, or if there is a real answer to it as asked. So I will leave that to others who know more than me.<br>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">or at least reserve one NIC for the host server and one NIC for the VMs.<br>
</div></blockquote><div><br></div><div>This can be done in /etc/network/interfaces as well. Assuming you want the VMs to use only the 2nd network card, then you add:<br><br>auto br0<br>iface br0 inet dhcp<br> bridge_ports eth1<br>
<br></div><div>And when creating a VM, via libvirt, you say:<br><br></div><div>sudo virt-install --name vm_name ... --network bridge=br0 ...<br><br></div><div>This tells libvirt to use the bridge br0, which uses eth1, which you have configured separately.<br>
<br>I have not tried this specifically, but it "should work" (yeah, famous words!)<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>(I'm ashamed to say this is much easier in MS Hyper-V, but I would much rather learn how to do this in Linux CLI!)</div></div></blockquote><div><br></div><div>Tsk tsk tsk ... traitors and infiltrators in our midst ... ;-)<br>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>So I guess my question is two-fold:</div><div><br></div>
<div>a) how do I tame my NICs in preparation for setting up VMs, and</div></div></blockquote><div><br></div><div>See above.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div> b) what's the preferred method for setting up VMs in Ubuntu Server? Does anyone know of a good how-to link?</div></div></blockquote><div><br></div><div>If you have kvm capable server, then use libvirt. You create VMs using virt-install on the command line, and use virt-viewer to see the BIOS and console output, and manage them using virsh.<br>
<br></div><div>Or wait till November, when I will cover all this in a presentation for KWLUG.<br></div></div>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com" target="_blank">2bits.com</a>, Inc.<br>Fast Reliable Drupal<br>
Drupal optimization, development, customization and consulting.<br>Simplicity is prerequisite for reliability. -- Edsger W.Dijkstra<br>Simplicity is the ultimate sophistication. -- Leonardo da Vinci<br>For every complex problem, there is an answer that is clear, simple, and wrong." -- H.L. Mencken<br>
</div></div>