Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
docker_notes:vm-container [2024-12-24 Tue wk52 08:42] – [KVM versus Proxmox] baumkpdocker_notes:vm-container [2025-01-11 Sat wk02 08:50] (current) – [KVM versus Proxmox] baumkp
Line 12: Line 12:
 As my old router became too unreliable to use circa November 2024, I have ordered a replacement.  ++My old router tl;dr|My previous router basic failed to operated reliably circa October 2024 had an Intel N3700 CPU, maximum 8GB ram, procured in 2016, which in 2024 is becoming slow to use, but still functions well as a sub gb/s router.  I also run a VM with Docker containers for a backup Bind9 DNS and backup Kea DHCP on this machine.  As my current (WAN) internet speed is about 265Mb/s down and 23Mb/s up this router is still suitable for purpose. I suspect it will not be limiting until the available WAN speeds are above 1000Mbps. <fs small>(I am currently 2023/2024 eyeing an Intel i5-1335U or N305 as a possible replacement, this is much fast overall and should easily handle multi Gb/s internet traffic, as well as more complex resource intensive Docker instances.)</fs>  Sadly the N3700 AS2400 BMS seem to be unreliable now. I can only login to the BMS after a long shutdown and the machine often fails to reboot reliably.  Due to the age of the hardware it is not worth the cost to repair.  I will need to get a replacement.++ As my old router became too unreliable to use circa November 2024, I have ordered a replacement.  ++My old router tl;dr|My previous router basic failed to operated reliably circa October 2024 had an Intel N3700 CPU, maximum 8GB ram, procured in 2016, which in 2024 is becoming slow to use, but still functions well as a sub gb/s router.  I also run a VM with Docker containers for a backup Bind9 DNS and backup Kea DHCP on this machine.  As my current (WAN) internet speed is about 265Mb/s down and 23Mb/s up this router is still suitable for purpose. I suspect it will not be limiting until the available WAN speeds are above 1000Mbps. <fs small>(I am currently 2023/2024 eyeing an Intel i5-1335U or N305 as a possible replacement, this is much fast overall and should easily handle multi Gb/s internet traffic, as well as more complex resource intensive Docker instances.)</fs>  Sadly the N3700 AS2400 BMS seem to be unreliable now. I can only login to the BMS after a long shutdown and the machine often fails to reboot reliably.  Due to the age of the hardware it is not worth the cost to repair.  I will need to get a replacement.++
  
-My main home server is based upon an Intel Atom C3750 server, this is still currently adequately meeting my needs. I have upgraded with a 2.5Gb/s PCIe card.  ++tl;dr|I have not been able to find a good replacement for this machine at this time.  It was designed as a server, again an i5-1335U is in many ways superior, CPU cores and threads, CPU and memory speed and bandwidth, however memory is not ECC and memory is limited to 64GB, neither of which is probably a problem for me, as I am currently only using 32GB. Power consumption is similar. The biggest problem is that I have not been able to date find an i5-1335U motherboard with 4+ SATA ports and PCIE expansion slot, most are laptop boards, router boards or industrial embedded type boards that do not have the functionality that I am after.++  I also still operate an older Intel Atom C2750 as a back-up server. This gets started by the main server once a week to run a Restic back-up with a Python script I wrote.+My main home server is based upon an Intel Atom C3750 server, this is still currently adequately meeting my needs. I have upgraded with a 2.5Gb/s PCIe card.  ++tl;dr|I have replaced with a i3-305 based machine, with 2x modern 2.5GB/s NICs and 2 x 10GB/s NICs, all RJ45 type with 10GB/S NICs able to operate reliably and low power at all main speeds down to 10MB/s.++  I also still operate an older Intel Atom C2750 as a back-up server. This gets started by the main server once a week to run a Restic back-up with a Python script I wrote.
  
  
Line 18: Line 18:
 I use Linux KVM with libvirt, virsh and qemu. I use Linux KVM with libvirt, virsh and qemu.
   * Install standard Debian files. See [[https://wiki.kptree.net/doku.php?id=home_server:home_server_setup:kvm&s[]=libvirt#kvm_setup|kvm setup]]   * Install standard Debian files. See [[https://wiki.kptree.net/doku.php?id=home_server:home_server_setup:kvm&s[]=libvirt#kvm_setup|kvm setup]]
-    * I simply do not normally need a GUI. Where convenient I may separately install a GUI that can be accessed via VNC.  I often in stall on my main VM host, but not router host.+    * I simply do not normally need a GUI. Where convenient I may separately install a GUI that can be accessed via VNC.  I often install on my main VM host, but not router host.
   * Add user to libvirt and libvirt-qemu, e.g. ''sudo usermod -a -G libvirt-qemu baumkp''   * Add user to libvirt and libvirt-qemu, e.g. ''sudo usermod -a -G libvirt-qemu baumkp''
   * If you are ssh'ing into the host machine remember to add the ssh key to allow password-less login.  e.g. ''ssh-copy-id 192.168.1.21'' from the host machined where ''192.168.1.21'' is the remote machine.  If you do not do this the VM installer can ask for password continuously to the point of making use non-functional.   * If you are ssh'ing into the host machine remember to add the ssh key to allow password-less login.  e.g. ''ssh-copy-id 192.168.1.21'' from the host machined where ''192.168.1.21'' is the remote machine.  If you do not do this the VM installer can ask for password continuously to the point of making use non-functional.
Line 41: Line 41:
 #iface enp1s0 inet dhcp #iface enp1s0 inet dhcp
  
-auto br0 +auto enp1s0 
-iface br0 inet static +iface enp1s0 inet static
-  bridge_ports enp1s0+
   address 192.168.1.2/24   address 192.168.1.2/24
   gateway 192.168.1.1         #Do not use on a router   gateway 192.168.1.1         #Do not use on a router
-  dns-nameservers 192.168.1.14 192.168.1.2  #Your LAN DNS server(s) +  dns-nameservers 192.168.1.14 192.168.1.2  #Your LAN DNS server(s)</code>
-  bridge_stp off  # disable Spanning Tree Protocol </code> +
 ++++ ++++
 +
 +Note that Docker does not need to operate on a machine with bridge network, which affords some benefits with operating a KVM.
 ====Reference==== ====Reference====
   *[[https://linuxconfig.org/how-to-use-bridged-networking-with-libvirt-and-kvm|How to use bridged networking with libvirt and KVM]]   *[[https://linuxconfig.org/how-to-use-bridged-networking-with-libvirt-and-kvm|How to use bridged networking with libvirt and KVM]]