User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
foss:wikishelf [2015/05/01 23:31] external edit
foss:wikishelf [2015/07/14 22:05] (current)
Jean-Christophe Berthon Add section on virtualisation
Line 137: Line 137:
 # exit</​code>​ # exit</​code>​
 +===== Virtualization =====
 +==== KVM ====
 +I'm using virt-manager to create, launch and maintain 2 VMs on my little HP MicroServer. This MicroServer is running a dual-core AMD Turion CPU with AMD-V instructions but no IO-MMU (or AMD-VI), it was upgraded with 8GB RAM and a second Gigabit NIC with 2 Ethernet ports.
 +I have the host using one NIC port, and each VM is using a dedicated NIC port using MacVTap. Either because I'm using kernel 3.19 on the host or because I have each VM with a dedicated NIC, but host is able to communicate with the guests using this configuratino.
 +To make this work, I've done the following configurations.
 +=== Host Configuration ===
 +The host is running Ubuntu 15.04 and I have the file ''/​etc/​network/​interfaces''​ with the following configuration (Note: em1 is used by the host and p1p1 and p1p2 are used by the VMs):
 +<​code>​auto em1 p1p1 p1p2
 +iface em1 inet dhcp
 +iface p1p1 inet manual
 +iface p1p2 inet manual</​code>​
 +This brings up automatically on boot the 3 NICs but only assign an IP to the one used by the host.
 +=== VMs Configuration ===
 +The VMs configuration in virt-manager are using a NIC based on MacVTap with VEPA and virtio. The guest OSes are using simply dhcp on the network interface (eth0 in my case).
 +If you feel like editing the XML configuration directly, simply add anew interface in the ''<​devices>''​ section:
 +<​code> ​   <​interface type='​direct'>​
 +      <source dev='​p1p1'​ mode='​vepa'/>​
 +      <model type='​virtio'/>​
 +    </​interface></​code>​
foss/wikishelf.txt · Last modified: 2015/07/14 22:05 by Jean-Christophe Berthon