<div dir="ltr"><div>OK, so far so good..</div><div><br></div><div>I found I was having DNS issues with using DHCP, so I opted for static IPs:</div><div><br></div><div>cat /etc/network/interfaces<br></div><div><br></div><div>
# This file describes the network interfaces available on your system<br></div><div># and how to activate them. For more information, see interfaces(5).</div><div><br></div><div># The loopback network interface</div><div>
auto lo</div><div>iface lo inet loopback</div><div><br></div><div># The primary network interface</div><div>auto eth0</div><div>iface eth0 inet static</div><div> address 10.42.1.80</div><div> netmask 255.255.255.0</div>
<div> gateway 10.42.1.1</div><div> network 10.42.1.0</div><div> broadcast 10.42.1.255</div><div> nameserver 10.42.1.1</div><div> nameserver 209.222.18.222</div><div> nameserver 209.222.18.218</div><div> nameserver 8.8.8.8</div>
<div><br></div><div># secondary NIC card</div><div>auto eth1</div><div>iface eth1 inet static</div><div> address 10.42.1.81</div><div> netmask 255.255.255.0</div><div> network 10.42.1.0</div><div> broadcast 10.42.1.255</div>
<div> gateway 10.42.1.1</div><div> nameserver 10.42.1.1</div><div> nameserver 209.222.18.222</div><div> nameserver 209.222.18.218</div><div> nameserver 8.8.8.8</div><div><br></div><div># manual - to set 2nd NIC for VMs</div>
<div>#auto br0</div><div>#iface br0 inet dhcp</div><div># bridge_ports eth1</div><div><br></div><div># add bridge interface</div><div>iface br0 inet static</div><div>address 10.42.1.95</div><div>network 10.42.1.0</div>
<div>netmask 255.255.255.0</div><div>broadcast 10.42.1.255</div><div>gateway 10.42.1.1</div><div>dns-nameservers 10.42.1.1</div><div>dns-nameservers 209.222.18.222</div><div>dns-nameservers 209.222.18.218</div><div>bridge_ports eth1</div>
<div>bridge_stp off</div><div>auto br0</div><div><br></div><div><br></div><div>Then I made sure the router's port forwarding was good so I could access the machine from the office (I have to redirect the ports due to restrictions at work).</div>
<div><br></div><div>Before I could move to the KVM work I remembered that I neglected to mount the spare hard drives I had in the host box after the last time I installed Ubuntu Server, so I used fdisk to partition and prep a HDD for use as my VM storage area.</div>
<div><br></div><div>So now on to setting up KVM...</div><div><br></div><div>I had a copy of Ubuntu Server 14.04 on another server so I wanted to copy it over to the VM host. Being someone who's snuck by with the GUI, I wanted to learn to do this via CLI (yes, I've never SCP'd before...). So I had to appended the remote server's public key to the VM host, the do a scp copy as such:</div>
<div><br></div><div>scp root@10.42.1.71:/mnt/HD_a2/Downloads_Storage/OS_ISOs/LinuxOS/ubuntu-14.04-server-amd64.iso ~/iso/ubserver.iso</div><div><br></div><div>So this is how I installed KVM and built a VM (pretty much all of this was run with sudo, so you may want to flip over to 'su'):</div>
<div><br></div><div>aptitude -y install qemu-kvm libvirt-bin virtinst bridge-utils</div><div>modprobe vhost_net </div><div>lsmod | grep vhost</div><div><br></div><div>First we have to make the drive that the VM sits on (for lack of a creative spark, I'm going to name this test VM "europa"):</div>
<div><br></div><div>fallocate -l 100000M /var/lib/libvirt/images/europa.img</div><div><br></div><div>Next, you may need to install virt-install using apt-get.</div><div><br></div><div>The actual command to make the VM was:</div>
<div><br></div><div>virt-install -n europa -r 1024 -f /media/vms/europa/europa.img --cdrom /home/jeff/iso/ubserver.iso --accelerate --vnc --noautoconsole -v --network bridge:br0</div><div><br></div><div>I'm not 100% sure about using br0 as the network bridge. I may have messed that up...</div>
<div><br></div><div>So this is where I right now.. I know the VM is running because I can run:</div><div><br></div><div>virsh list --all</div><div> Id Name State</div><div>----------------------------------------------------</div>
<div> 2 europa running</div><div><br></div><div> </div><div>Now this is where I am stuck. Virt-manager is pretty much useless (you run it and it just goes away) and virt-viewer is crying about not being able to find the Display (I am running Ubuntu Server, which is CLI only. Is that the problem?)</div>
<div> </div><div>I'm still trying to get past this issue and actually see the VM. I'll let you know how that goes. If I knew europa's IP or something that I could connect to...</div><div> </div><div> </div><div>
<br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 15 August 2014 11:30, Khalid Baheyeldin <span dir="ltr"><<a href="mailto:kb@2bits.com" target="_blank">kb@2bits.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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.<span class="HOEnZb"><font color="#888888"><br></font></span></div></div><span class="HOEnZb"><font color="#888888">-- <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>
</font></span></div></div>
<br>_______________________________________________<br>
kwlug-disc mailing list<br>
<a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a><br>
<a href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org" target="_blank">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
<br></blockquote></div><br></div>