anchor.diff:  [cols="1, 8a"]
   |===
   ^.^|image:/images/icons/important.png[icon="tip",size="4x",width=56]
  -|*Note*: This post took a bit longer than planned. This is a result of the beta status of the PVE version we are using combined with the newness of the Ryzen platform. This means that not all of the kinks are guaranteed to be sorted, yet. As a result, there were some interesting issues with UEFI, ZFS, and the backup/restore process that needed to be resolved. That said, we have some work-arounds and can continue with our journey.
  +|*Note*: This post took a bit longer than planned. This is a result of the beta status of the PVE version we are using combined with the newness of the Ryzen platform. This means that not all of the kinks are guaranteed to be sorted, yet. As a result, there were some interesting issues with UEFI, ZFS, and the backup/restore process that needed to be resolved. That said, we have some workarounds and can continue with our journey.
   |===
   
   === Step 1: Create the VM
  
positive.code: 
  == Next Steps
  
  At this point, we should have our Windows installation running on our Ryzen server as-if it were running on a Haswell machine, at near native performance. Our NVidia drivers should be installed, however the "Display Adapter" status will likely show as: "This device cannot find enough free resources that it can use. (Code 12)". 
  
  Considering that Ryzen is a new platform, the system bios and Linux Kernel support are not quite at 100% yet. AMD recently released an link:https://community.amd.com/community/gaming/blog/2017/05/25/community-update-4-lets-talk-dram[AGESA Update^] that should make it into a bios update over the next few weeks. This should improve virtualization support for PCI Express Access Control Services (ACS). The ACS support also needs to make it into the Linux kernel. After these updates are ready, we should be able to finish enabling full GPU Passthrough to our VM.
  
negative.code: 
  This is a great time to save our work. In case something goes haywire, we should have a backup so that we don't go through that whole process again, right? In addition, wouldn't it be nice to have a clean slate in case of a virus or worm? We are talking about Windows after all.
  
  Backing up our VM is easy to do with PVE. First, we shutdown Windows. Next, on our PVE Web GUI, we select the "Summary" tab of our Windows VM and confirm the Status is "Stopped". Finally, we select the "Backup" tab, click "Backup Now" and then click "Backup". Then we need to be patient until it completes.
  
  ```
  INFO: transferred 137438 MB in 515 seconds (266 MB/s)
  