User Tools

Site Tools


network_stuff:juniper:host-preparation

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
network_stuff:juniper:host-preparation [2020/01/19 13:29] jotasandokunetwork_stuff:juniper:host-preparation [2023/11/02 14:38] (current) – external edit 127.0.0.1
Line 1: Line 1:
 HOST PREPARATION:\\ HOST PREPARATION:\\
-[[https://www.juniper.net/documentation/en_US/vmx/topics/topic-map/vmx-installing-on-kvm.html#id-preparing-the-ubuntu-host-to-install-vmx]]+Combine the requirements below with the ones listed in the "Preparing the CentOS Host to Install vMX" in [[https://www.juniper.net/documentation/en_US/vmx/topics/topic-map/vmx-installing-on-kvm.html#id-preparing-the-ubuntu-host-to-install-vmx]]
 \\ \\
 +Verify that INTEL VT-d is enabled (note amd-v is not working for this!)
 +  cat /proc/cpuinfo | egrep -i vmx  # we Want this
 +  cat /proc/cpuinfo | egrep -i svm  # we Don't want this
 Disable KSM by setting KSM_ENABLED=0 in /etc/default/qemu-kvm: \\ Disable KSM by setting KSM_ENABLED=0 in /etc/default/qemu-kvm: \\
   systemctl disable ksm   systemctl disable ksm
Line 7: Line 10:
 \\ \\
 HUGEPAGES (x2 1G size)\\ HUGEPAGES (x2 1G size)\\
-[[https://oracle-base.com/articles/linux/configuring-huge-pages-for-oracle-on-linux-64]]+[[https://mycompany2-base.com/articles/linux/configuring-huge-pages-for-mycompany2-on-linux-64]]
 \\ \\
 +  * For hugepages:
 +    * determine whether our system is UEFI. If this exists, is uefi: "cat /sys/firmware/efi/"
 +
 +  vim /etc/default/grub
 +  # add this (one line):
 +  default_hugepagesz=1G hugepagesz=1G hugepages=number-of-numa-sockets intel_iommu=on"
 +  default_hugepagesz=1G hugepagesz=1G hugepages=50 intel_iommu=on"
 +  grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
 +  [root@networklab01.ash.oci.mycompany1.co.uk ~]# grep Hugepagesize /proc/meminfo
 +  Hugepagesize:    1048576 kB
 +  
 +APIC and KSM:
 +Apic  [[https://access.redhat.com/solutions/58790|info]]
 +
 +
 +  cat /etc/qemu-kvm/target-x86_64.conf
 +  options kvm_intel nested=1 enable_apicv=0
 +  KSM_ENABLED=0
 +
 +Or
 +  vim /etc/default/grub
 +  # add this:
 +  ... noapic"
 +  grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
 +  
 +  
 KVM INSTALL:\\ KVM INSTALL:\\
   * [[https://www.cyberciti.biz/faq/how-to-install-kvm-on-centos-7-rhel-7-headless-server/]]   * [[https://www.cyberciti.biz/faq/how-to-install-kvm-on-centos-7-rhel-7-headless-server/]]
 +
 +  yum update
 +  yum install -y qemu-kvm libvirt libvirt-python libguestfs-tools virt-install
 +  systemctl enable libvirtd
 +  systemctl start libvirtd
 +  lsmod | grep -i kvm 
 +  
 +
   * If we don't have root ssh access to the host, we need to add our user to the libvirt group so we can use virt-manager remotely:   * If we don't have root ssh access to the host, we need to add our user to the libvirt group so we can use virt-manager remotely:
  
Line 53: Line 90:
   EOF   EOF
  
-  virsh net-define vagrant-libvirt-net.xml+  virsh net-define /var/tmp/vagrant-libvirt-net.xml
   virsh net-start vagrant-libvirt   virsh net-start vagrant-libvirt
   virsh net-autostart vagrant-libvirt   virsh net-autostart vagrant-libvirt
Line 63: Line 100:
 \\ \\
 Before virt-install , add vagrant-libvirt network from  Before virt-install , add vagrant-libvirt network from 
-  restart libvirtd +  service libvirtd restart
 \\ \\
 For qemu permissions: [[https://github.com/jedi4ever/veewee/issues/996]]  For qemu permissions: [[https://github.com/jedi4ever/veewee/issues/996]] 
 +
 +
 +
 +  ssh-keygen # upload key to gitlab
 +  eval $(ssh-agent -s)
 +  ssh-add ~/.ssh/*
 +  git clone git@gitlab.mycompany2datacloud.com:jaime.santos.amandi/junos-vmx-vagrant-virtual-lab.git
 +  git clone git@gitlab.mycompany2datacloud.com:jaime.santos.amandi/junos-vqfx-vagrant-virtual-lab.gi
 +
network_stuff/juniper/host-preparation.1579440557.txt.gz · Last modified: (external edit)