anchor.diff:  | Option | Details
   
   | allow_unsafe_interrupts=1
  -| For platforms without interrupt remapping support. Removes protection against link:http://invisiblethingslab.com/resources/2011/Software%20Attacks%20on%20Intel%20VT-d.pdf[MSI-based interrupt injection attacks^] by guests.  Only trusted guests and drivers should be run with this workaround.
  +| Interrupt remapping is designed to provide device isolation. This workaround is for platforms without interrupt remapping support. It removes protection against link:http://invisiblethingslab.com/resources/2011/Software%20Attacks%20on%20Intel%20VT-d.pdf[MSI-based interrupt injection attacks^] by guests.  Only trusted guests and drivers should be run with this configuration.
   
   | ids=*10de:1b80,10de:10f0*`
   | Assign the specified GPU to the virtual pci for use in our VM.
  
positive.code: :toc: macro
  :toclevels: 3
  
  In the link:/2017/04/23/Server-Virtualization-Management[previous post] we learned about ProxMox and outlined our plan to build a powerful "bang for the buck" home server for games _and_ other system-intensive pursuits. Now we begin.
  
  toc::[]
  
  == Installation
  
  https://forum.level1techs.com/t/proxmox-zfs-with-ssd-caching-setup-guide/97663
  https://pve.proxmox.com/wiki/Quick_installation
  
  Disconnect all the drives except the boot drive
  KVM
  
  == Post-Install
  
  === GPU Passthrough
  
  
negative.code: // :hp-image: /covers/cover.png
  
  = PVE: Virtualization for Work and Play (Getting Started)
  :hp-alt-title: Server Virtualization Management Part2
  :hp-tags: Blog, Open_Source, Technology
  :icons: image
  