anchor.diff:  [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.
  +|*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:
  
positive.code: ... click #OK#
  ... click #Next#
  
  At this point the installation process will recognize the virtual disk and be able to continue with the installation process. In addition, Windows should automatically recognize and configure the network card. We can bypass the registration process until later. Select our "Home" network.
  
  === Step 3: Post Installation
  
  
negative.code: [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 workarounds and can continue with our journey.
  |===
  
  === Step 1: Create the VM
  