anchor.diff:  
   == 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)". 
  +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.
  
positive.code: [cols="1, 8a"]
  |===
  ^.^|image:/images/icons/lightbulb.png[icon="tip",size="4x",width=56]
  |*About That*: A zvol is an emulated "block device" provided by ZFS. By default, PVE creates one zvol for each VM-disk. Once we create our VM we can see our disks by running: `zfs list -t all -r tank`. The disks would be hidden in the tank folder, however they would be mapped as block devices which we can see if we run: `ll /sys/block/zd*`. It is important to note that PVE saves the disk size in our configuration file, however it also runs a command similar to `zfs create -V 128G tank/vm-disks/vm-100-disk-1` which also sets the zvol block device size in our zpool. Ensure you update your drive size in the PVE Web GUI so that they match up.
  |===
  
  .Restoring our backup:
  
negative.code: [cols="1, 8a"]
  |===
  ^.^|image:/images/icons/important.png[icon="tip",size="4x",width=56]
  |*Note*: While trying to restore, the PVE process generated an error and failed. Unfortunately, this process removes the original VM disk image and then tries to restore the backup, which meant that I had to repeat the installation process multiple times. However, this should be resolved when the production version of PVE is released. In the mean time, we can use the following manual process to backup and restore.
  |===
  
  We can also back the drive image directly from the command line. There are multiple ways to do this. Using the Unix command `link:https://en.wikipedia.org/wiki/Dd_(Unix)[dd^]`, we will duplicate the emulated zvol block device as a raw file in our zfs pool.
  