May 5, 20179 yr Community Expert 6 minutes ago, DDock said: BTRFS Then don't now why it's not working for you, you are the first to report it didn't work.
May 5, 20179 yr Author Could it be something else about the Windows 7 template that these machines are running off of? Is it possible to change the template to the Windows 10 one without screwing a bunch of stuff up?
May 5, 20179 yr Community Expert 7 minutes ago, DDock said: Could it be something else about the Windows 7 template that these machines are running off of? Is it possible to change the template to the Windows 10 one without screwing a bunch of stuff up? Doubtful, you can create a new win10 VM and check if it works there, if it does you now the problem is the existing VMs.
May 5, 20179 yr Author 1 hour ago, johnnie.black said: Doubtful, you can create a new win10 VM and check if it works there, if it does you now the problem is the existing VMs. When setting up the VM disk, should it be raw or qcow2?
May 5, 20179 yr Community Expert 1 minute ago, DDock said: When setting up the VM disk, should it be raw or qcow2? Raw performs better.
February 16, 20188 yr Hi, I recently set up my first Win10 vm and came across this thread. Are you still sure that a SSD is detected by Windows as and HDD when run in a vm? Because when I wanted to turn off the optimization schedule in disk defragment settings the media type of my vdisk was automatically shown as SSD. Anyone else recognized this? Edited February 16, 20188 yr by Marv
February 16, 20188 yr I saw this thread for first time today. I have a question about changing the controller to virtio-scsi. 1 - How is this different than making the disk img into a sparse file? I've seen instructions on re-sparsifying an .img file posted. 2 - If basically the same result, which is better method? 3 - If there is plenty of free space on the SSD, is there any big benefit of releasing the blocks to trim? 4 - I have had problems with sparse files confusing standard commands (even cp and 7zip), and abandoned using them. Is this strongly recommended? Or just an option if your SSD size is tight. @Marv - I am seeing same thing. Below is my defrag schedule. The C: drive is a .img located on an NVMe showing solid state The D: drive is a .img file located on a hard disk (unassigned device) showing hard disk. The Recovery and bottom one (volume faa...) - I have no idea what they are used for, but they are also showing solid state. So there seems some info is being communicated from KVM on the nature of the underlying media containing the IMG. This is unexpected but pretty cool. I wonder if you moved the .IMG file to a hard disk and tried to use it, if it would show it was now on a hard disk?? Assuming yes.
February 16, 20188 yr Community Expert 7 hours ago, Marv said: Are you still sure that a SSD is detected by Windows as and HDD when run in a vm? Not sure, this was done for v6.2, there are likely changes since then, if it's already detected as an SSD trim will work, not sure if it will still unmap the unused space, because with that change the disks are detected as "thin provisioned drive", not SSD.
February 17, 20188 yr Community Expert 16 hours ago, SSD said: 1 - How is this different than making the disk img into a sparse file? I've seen instructions on re-sparsifying an .img file posted. Using the virtio-scsi controller keeps the image as small as possible, i.e., any deleted blocks are unmapped (trimmed) automatically, no need to manually re-sparsify. 16 hours ago, SSD said: 2 - If basically the same result, which is better method? auto vs manual 16 hours ago, SSD said: 3 - If there is plenty of free space on the SSD, is there any big benefit of releasing the blocks to trim? If the VM detects the vdisk as an SSD it should trim it so if space it's not a problem it should be the same. 16 hours ago, SSD said: 4 - I have had problems with sparse files confusing standard commands (even cp and 7zip), and abandoned using them. Is this strongly recommended? Or just an option if your SSD size is tight. Don't know about this, never had issues nor remember reading about similar problems in the forum, but if space is not an issue and the SSD is being trimmed I see no problems using a thick-provisioned vdisk.
October 2, 20187 yr I have to give this post a bump. Been using a Windows 10 VM on my cache drive since I built my unraid server last December and kept getting annoyed that it was taking up too much space leaving not much for unraid stuff. Changed the settings based on this post and bam, thin provisioned and now my cache drive is nice and clean. Thank you!
Archived
This topic is now archived and is closed to further replies.