Jump to content
We're Hiring! Full Stack Developer ×

bastl

Members
  • Posts

    1,267
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by bastl

  1. If you passthrough an NVME the best choice is to passthrough the entire controller and not the by-id. Check my config at the bottom you can find an entry "boot order 1". This is the controller for the NVME. Also using SCSI for the other SSD can give you slightly lower latency and less overhead. I think there is also a SpaceInvader video about how to passthrough an NVME controller. Also you can see in my configs a couple tweaks especialy for TR4 where the CPU is reported as Epyc to make the OS aware of the real amount of L2 and L3 cache of the CPU. Another note, you have set the emulatorpin to cores from node0. I've got better results having it set to the node the cores i'am giving to the VM.

     

    <?xml version='1.0' encoding='UTF-8'?>
    <domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
      <name>01_W10</name>
      <uuid>ab84a67e-428e-36f9-5a88-3c02ffe6f93a</uuid>
      <metadata>
        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
      </metadata>
      <memory unit='KiB'>16777216</memory>
      <currentMemory unit='KiB'>16777216</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>14</vcpu>
      <iothreads>1</iothreads>
      <cputune>
        <vcpupin vcpu='0' cpuset='9'/>
        <vcpupin vcpu='1' cpuset='25'/>
        <vcpupin vcpu='2' cpuset='10'/>
        <vcpupin vcpu='3' cpuset='26'/>
        <vcpupin vcpu='4' cpuset='11'/>
        <vcpupin vcpu='5' cpuset='27'/>
        <vcpupin vcpu='6' cpuset='12'/>
        <vcpupin vcpu='7' cpuset='28'/>
        <vcpupin vcpu='8' cpuset='13'/>
        <vcpupin vcpu='9' cpuset='29'/>
        <vcpupin vcpu='10' cpuset='14'/>
        <vcpupin vcpu='11' cpuset='30'/>
        <vcpupin vcpu='12' cpuset='15'/>
        <vcpupin vcpu='13' cpuset='31'/>
        <emulatorpin cpuset='8,24'/>
        <iothreadpin iothread='1' cpuset='8,24'/>
      </cputune>
      <numatune>
        <memory mode='strict' nodeset='1'/>
      </numatune>
      <resource>
        <partition>/machine</partition>
      </resource>
      <os>
        <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/ab84a67e-428e-36f9-5a88-3c02ffe6f93a_VARS-pure-efi.fd</nvram>
      </os>
      <features>
        <acpi/>
        <apic/>
        <hyperv>
          <relaxed state='on'/>
          <vapic state='on'/>
          <spinlocks state='on' retries='8191'/>
          <vpindex state='on'/>
          <synic state='on'/>
          <stimer state='on'/>
          <reset state='on'/>
          <vendor_id state='on' value='none'/>
        </hyperv>
      </features>
      <cpu mode='custom' match='exact' check='full'>
        <model fallback='forbid'>EPYC</model>
        <topology sockets='1' cores='7' threads='2'/>
        <cache level='3' mode='emulate'/>
        <feature policy='require' name='topoext'/>
        <feature policy='disable' name='monitor'/>
        <feature policy='require' name='hypervisor'/>
        <feature policy='disable' name='svm'/>
        <feature policy='disable' name='x2apic'/>
      </cpu>
      <clock offset='localtime'>
        <timer name='hypervclock' present='yes'/>
        <timer name='hpet' present='no'/>
      </clock>
      <on_poweroff>destroy</on_poweroff>
      <on_reboot>restart</on_reboot>
      <on_crash>restart</on_crash>
      <devices>
        <emulator>/usr/local/sbin/qemu</emulator>
        <disk type='block' device='disk'>
          <driver name='qemu' type='raw' cache='none' io='threads' discard='unmap'/>
          <source dev='/dev/disk/by-id/ata-Samsung_SSD_850_EVO_1TB_S2RFNX0J606029L'/>
          <backingStore/>
          <target dev='hdc' bus='scsi'/>
          <boot order='3'/>
          <alias name='scsi0-0-0-2'/>
          <address type='drive' controller='0' bus='0' target='0' unit='2'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/Linux/pop-os_19.04_amd64_nvidia_4.iso'/>
          <backingStore/>
          <target dev='hdb' bus='sata'/>
          <readonly/>
          <boot order='2'/>
          <alias name='sata0-0-1'/>
          <address type='drive' controller='0' bus='0' target='0' unit='1'/>
        </disk>
        <controller type='scsi' index='0' model='virtio-scsi'>
          <alias name='scsi0'/>
          <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
        </controller>
        <controller type='sata' index='0'>
          <alias name='ide'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
        </controller>
        <controller type='pci' index='0' model='pcie-root'>
          <alias name='pcie.0'/>
        </controller>
        <controller type='pci' index='1' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='1' port='0x10'/>
          <alias name='pci.1'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
        </controller>
        <controller type='pci' index='2' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='2' port='0x11'/>
          <alias name='pci.2'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
        </controller>
        <controller type='pci' index='3' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='3' port='0x12'/>
          <alias name='pci.3'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
        </controller>
        <controller type='pci' index='4' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='4' port='0x13'/>
          <alias name='pci.4'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
        </controller>
        <controller type='pci' index='5' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='5' port='0x14'/>
          <alias name='pci.5'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
        </controller>
        <controller type='pci' index='6' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='6' port='0x15'/>
          <alias name='pci.6'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/>
        </controller>
        <controller type='pci' index='7' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='7' port='0x16'/>
          <alias name='pci.7'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/>
        </controller>
        <controller type='pci' index='8' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='8' port='0x8'/>
          <alias name='pci.8'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
        </controller>
        <controller type='virtio-serial' index='0'>
          <alias name='virtio-serial0'/>
          <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
        </controller>
        <controller type='usb' index='0' model='nec-xhci' ports='15'>
          <alias name='usb'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
        </controller>
        <interface type='bridge'>
          <mac address='52:54:00:65:2d:ab'/>
          <source bridge='br0'/>
          <target dev='vnet0'/>
          <model type='virtio'/>
          <alias name='net0'/>
          <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
        </interface>
        <serial type='pty'>
          <source path='/dev/pts/0'/>
          <target type='isa-serial' port='0'>
            <model name='isa-serial'/>
          </target>
          <alias name='serial0'/>
        </serial>
        <console type='pty' tty='/dev/pts/0'>
          <source path='/dev/pts/0'/>
          <target type='serial' port='0'/>
          <alias name='serial0'/>
        </console>
        <channel type='unix'>
          <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-01_W10/org.qemu.guest_agent.0'/>
          <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
          <alias name='channel0'/>
          <address type='virtio-serial' controller='0' bus='0' port='1'/>
        </channel>
        <input type='tablet' bus='usb'>
          <alias name='input0'/>
          <address type='usb' bus='0' port='3'/>
        </input>
        <input type='mouse' bus='ps2'>
          <alias name='input1'/>
        </input>
        <input type='keyboard' bus='ps2'>
          <alias name='input2'/>
        </input>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x43' slot='0x00' function='0x0'/>
          </source>
          <alias name='hostdev0'/>
          <rom file='/mnt/user/Backup/vbios/Strix1080ti/AsusStrix1080TI_dump_edit.rom'/>
          <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x43' slot='0x00' function='0x1'/>
          </source>
          <alias name='hostdev1'/>
          <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x0a' slot='0x00' function='0x3'/>
          </source>
          <alias name='hostdev2'/>
          <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x41' slot='0x00' function='0x0'/>
          </source>
          <boot order='1'/>
          <alias name='hostdev3'/>
          <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
          </source>
          <alias name='hostdev4'/>
          <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x046d'/>
            <product id='0xc246'/>
            <address bus='5' device='2'/>
          </source>
          <alias name='hostdev5'/>
          <address type='usb' bus='0' port='1'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x1b1c'/>
            <product id='0x1b50'/>
            <address bus='5' device='3'/>
          </source>
          <alias name='hostdev6'/>
          <address type='usb' bus='0' port='2'/>
        </hostdev>
        <memballoon model='none'/>
      </devices>
      <seclabel type='dynamic' model='dac' relabel='yes'>
        <label>+0:+100</label>
        <imagelabel>+0:+100</imagelabel>
      </seclabel>
      <qemu:commandline>
        <qemu:arg value='-global'/>
        <qemu:arg value='pcie-root-port.speed=8'/>
        <qemu:arg value='-global'/>
        <qemu:arg value='pcie-root-port.width=16'/>
      </qemu:commandline>
    </domain>

     

    • Like 1
  2. This isn't a specific Ryzen issue. It's more like a Win7 issue thats around for ages. It usually only happens during the first setup of Win7. After the install and the first boot you should be able to shutdown the VM and add more cores without issues. What you can try is to try to use the machine type Q35 instead. If you are planing to passthrough devices like GPU audio mouse keyboard etc, first set it up without any devices.

  3. @danyg I noticed something strange in my docker config. I had 2 paths configured pointed to the same source. The config path (called host path in my old docker) and the override path both pointed to "/mnt/user/appdata/netdata". I guess this caused the issue overriding the files. I completly removed the docker and the config and redownloaded the docker image. Only one path left with the new config and the files i create stay in place. I can't remember ever touch the config before. The container I use for almost 2 years now. Maybe with an update the paths changed and in my config instead of replacing the old declaration the update added a second path.

     

    BUT at first I couldn't find any sensor informations after adding your tweaks. After double and triple checking the config files I think I found the issue. A single space in front of the "sensors: yes" in the python.d.conf caused the issue to not showing up the sensor informations in NetData. 😣

     

    On 9/16/2019 at 9:16 AM, bastl said:

    (remove the # at the beginning of that line)

    AND the space between '#' and 'sensors' 😂

  4. @Rick Sanchez Check the xml of the VM at the bottom are all the passed through USB devices listed. It should be looking like this

     

        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x04fc'/>
            <product id='0x0003'/>
          </source>
          <address type='usb' bus='0' port='1'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x0a12'/>
            <product id='0x0001'/>
          </source>
          <address type='usb' bus='0' port='2'/>
        </hostdev>

    In my case one is the usb mouse and the the second one is the bluetooth dongle for my keyboard. Compare it to the normal config view and check if all the devices also listed there.

     

    grafik.png.696c25202e1ecb1f2408f80cacd999d5.png

     

    If you for some reason disconnect the passed through USB device before starting up the VM you get the exact message you posted above.

  5. From all that I've read so far about the x570 boards is, that in most cases the IOMMU groups are horrible. Tons of stuff are grouped together and can't be split and a couple things under linux aren't stable yet. Even Wendel reported it in one of his videos that this platform isn't suggested yet for virtualisation. Not sure if newer BIOS/Agesa versions released the last weeks already fixed passthrough issues. I remember the first gen Threadrippers had nearly the same problems. 3 months or so after release the plattform became stable. Until that I had the same issues, random crashes, freezes, GPU passthrough not fully functional, terrible IOMMU groupings. Fingers crossed that your issues get solved soon.

  6. @frodr I use the following user script running once a day someone posted here on the forum. Can't find the source right now. It saves the xml and the NVRAM files in a zip file in the path you have to set at the top. Backups older than 30 days gets cleaned out with every run.

     

    #!/bin/bash
    #backs up
    #change the location below to your backup location 
    backuplocation="/mnt/user/Backup/vm_settings/"
    
    # do not alter below this line
    timestamp=`date '+%Y-%m-%d__%H-%M-%S'`
    dir="$backuplocation"vm_settings/"$timestamp"
    # dont change anything below here
    if [ ! -d $dir ] ; then
     
    			echo "making folder for todays date $timestamp"
    
    			# make the directory as it doesnt exist
    			mkdir -vp $dir
    		else
    			echo "As $dir exists continuing."
    			fi
    
    echo "Saving vm xml files"
    rsync -a --no-o /etc/libvirt/qemu/*xml $dir/xml/
    echo "Saving ovmf nvram"
    rsync -a --no-o /etc/libvirt/qemu/nvram/* $dir/nvram/
    chmod -R 777 $dir
    
    		echo "information: creating ZIP-archive and cleaning up old data"
        zip -r -9 "$backuplocation"vm_settings/"$timestamp".zip "$backuplocation"vm_settings/"$timestamp" && rm -r "$backuplocation"vm_settings/"$timestamp" 
    
    		# Amendmend to the original script of danioj by Deeks 2017
    		# Delete all backups older than 2 days ONLY if newer files exist
    		# Two remarks for quick and easy testing 
    		# 1. Line 148 : Set parameter --> actually_copy_files="0"
    		# 2. Lines 1068 & line 1070 : Use parameter -mmin in stead of -mtime to test with minutes rather than days
    		
    		# Credits for this code to JBRELAND on https://tinyurl.com/ycrrbobv
    
    		echo "information: cleaning out backups older than 30 days in location ONLY if newer files exist" $backuplocation/
    		for j in $backuplocation/
    		do
    		  if [[ -n $(find "$j" -type f -mtime -29) ]]; then
    		    #echo "debug: valid criteria to enter loop"
    		    find "$j" -type f -mtime +30 -exec rm -f {} \;
    		  fi 
    		  #echo "debug: ended if sequence after loop"
    		done
    
    sleep 5
    exit

     

  7. Just a question, are you even allowed to use the internet for private stuff on your work machine? Depending on which industry you're working, I can understand why the admins wanna prevent their user to accessing personal stuff with portable browsers. One single click on the wrong page or an personal email and the desaster is there.

  8. Ok. If it's a machine connected to a domain your profil with all it's settings might sync in the backround from a company server. Usually with every logoff or reboot this profil should sync back to the server and save any changes you made. Not actual sure if it's possible to setup by the admin in a way that login credentials are only allowed to add and change and disallowed to remove. I know for fileshares it's possible to set it up this way. The user is allowed to ad files, change existing files but aren't allowed to remove them. Sounds stupid, i know but there might be usecases for this. Not actual sure if it's possible for the credential store. Another possibility is that your companies firewall/proxy configuration caches all sorts of cookies and session information and kinda Man-In-the-Middle checks all the traffic from the clients. Lots of enterprise equipment still intercepts the connections to analyse for bad traffic and often breaks logins and webservices on non company networks.

     

    Have you tried to use a portable version of a browser like firefox? No need to install, everything is stored in a single folder, let's say on the desktop. If you don't need it anymore, delete it, an everything is gone. Sure this isn't the solution for your main problem to delete the stored credentials but maybe helps to prevent future issues.

  9. Are you using a Windows user account or a local account? The Microsoft account syncs all kind of stuff. I wouldn't be surprised if  it syncs all the login credentials you maybe have saved on an old installation. Just an idea.

     

    Best solution might be to stop using the Internet Explorer 😂 Btw. does it still get's updates? I think I've read something that MS will stop the support for it with the ongoin development and implementation of Edge.

  10. Change the boot order in this part from 1 to 2

        <disk type='block' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source dev='/dev/sdd1'/>
          <backingStore/>
          <target dev='hdc' bus='sata'/>
          <boot order='1'/>
          <alias name='sata0-0-2'/>
          <address type='drive' controller='0' bus='0' target='0' unit='2'/>
        </disk>
        

    and than search for the right entry for your NVME controller. Under tools > system devices search for your NVME controller and which bus/slot/function is shown.

     

    41:00.0 in my example:

    IOMMU group 45:	[144d:a804] 41:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961

    Now search your xml file for that number (source adress)

          <source>
            <address domain='0x0000' bus='0x41' slot='0x00' function='0x0'/>
          </source>

    and add the boot order tag as shown below from my setting.

        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x41' slot='0x00' function='0x0'/>
          </source>
          <boot order='1'/>
          <alias name='hostdev3'/>
          <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
        </hostdev>

    The bus, slot and function number will be different in your case. Make sure you get the correct one from your listed system devices. If you change the VM settings in the UI you might loose this custom edit. Keep that in mind.

     

    Another hint, try to avoid using core 0 and it's HT core for a VM. Unraid will always use this cores for it's own to handle stuff in the background. This can cause some hickups inside the VM if Unraid is doin stuff.

    • Like 1
    • Thanks 1
  11. 21 hours ago, danyg said:

    HOW TO TEMPERATURES VOLTAGES FANS

     

    - Go to http://unraid:19999/netdata.conf (change unraid for your unraid servername or ip, my case is called unraid)

    - Paste the contents in a text editor

    - Find the [plugins] section

    - Change the line where says # python.d = yes for python.d = yes (so remove the # at the beginning of that line)

    - Copy the content of your text editor and paste the content in a new file called netdata.conf in /mnt/user/appdata/netdata (or wherever you have configured the data of your unraid)

    - Now copy and paste the content of this: https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/python.d.conf in a text editor

    - Find the line # sensors: yes and change it for sensors: yes (remove the # at the beginning of that line)

    - Save this file as python.d.conf in /mnt/user/appdata/netdata

    - Create a folder python.d in /mnt/user/appdata/netdata

    - Copy the contents of https://raw.githubusercontent.com/netdata/netdata/master/collectors/python.d.plugin/sensors/sensors.conf in a text editor

    - Check the lines that starts with types:  and add a # at the beginning of each sensor that you DON'T want to have in netdata

    - Save this file as sensors.conf in /mnt/user/appdata/netdata/python.d

    - Restart the Docker of netdata, and you will see a new section called Sensors and there all your temperatures and voltages and more

     

    If after all of this, still not works, I recommend to install Dynamix System Temperature and configure it properly, you should be able to see temperatures in the footer of unraid admin web, as that tool configures the command sensors to work as expected and therefore the plugin for netdata can read those sensors too.

     

    Hope this Helps

     

    First of all, thanks for the tutorial. I've noticed today that the sensors section is gone for me in netdata. It's the first time this happened since I use that docker. That section was there as default since I can remember using this docker, without doin anything special with adding plugins.

     

    I followed your tutorial created all the files, with the changes you mentioned and as soon as I start the container the files become empty. Do I have to change something else? Any idea?

  12. 15 hours ago, fluisterben said:

    What do you mean by that?

    With "sitting on the cache drive" I mean depending on how the share is setup, the vdisk file is stored on ether the cache, the array or an unassigned device. It only can sit on one underlying source and not mixed/split like file shares. It's a single file. With "Prefer cache" as soon as the cache gets full or reaches the a certain threshold new writes will go directly to the array. BUT this is only true for single files writen to the share, not files writen inside a vdisk file. Let's say your cache has 10GB free and you transfer a file with 20GB to a share, it will be directly written to the array. If let's say you write that file inside the VM to your vdisk, the vdisk get's bigger until the cache drive get's full and the copy process will either pause, abort or the VM will crash completly. There is no way for unraid to transfer a part of the vdisk to the array to keep the cache free for a couple GB. Unraid sees the vdisk as a single file and can't split it like "oh thats some files on that vdisk the user not often use, let's put that on the array and keep the rest on the fast cache". That's not how it works.

     

    15 hours ago, fluisterben said:

    Isn't each write within the VM routed to cache either way?

    No it's not. If the vdisk is on an unassigned device or on the array, the writes within that file will directly writen to the underlying storage, where you basically see the raw or close to raw performance of that storage device.

     

    15 hours ago, fluisterben said:

    Why would it perform better for the entire image to be stored there? Only at start/boot and at shutdown that would save you a second or something, not?

    Depending on the usecase of a VM you should store the vdisk in most scenarios on the fastest storage possible. Not even starting up the VM benefits from it, also starting programs and working with them heavily see a positive affect of the underlying storage.

     

    Setup a VM with a vdisk on the array or a spinning drive and compare the performance with a VM vdisk on a ssd/nvme device and you will see huge huge performance differences in starting/using and working within that VM.

  13. I checked my setup where I never used IE before. The default path for the cache is "C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\". Did you tried the option in the settings to remove the cache and history by closing the IE? There is an extra Option for "allow caches and databases for websites" which is ticked by default. Sry, german UI but it looks like the following:

     

    IE.png.fa9ef9ceb76e454579f2617c78992cf9.png

     

    Maybe there are some other places storing logins and cookies.

     

  14. First google search came up with the following:

     

    Quote

    Add, remove, edit, backup, restore Stored User Names and Passwords in Windows 10

    The Stored User Names and Passwords in Windows lets you securely manage user names and passwords as a part of your profile. It lets you automatically enter saved user names and passwords for various network resources, servers, websites and applications, to authenticate yourself. In this post we will see how to add, remove, edit, backup, restore Stored User Names and Passwords & Credentials in Windows 10/8/7.

    rundll32.exe keymgr.dll,KRShowKeyMgr

    https://www.thewindowsclub.com/stored-user-names-and-passwords-windows

  15. "/mnt/user/domains/vmname/vdisk1.img" is the default and I don't know why you should change that. What is your main problem? Full cache drive? How big is the cache? Having a VM with an vdisk size bigger than the cache size sooner or later will end up with problems and propably data loss. You know that, right?

     

    For performance reasons it's prefered to have the VM vdisks sit on the cache drive if it's a SSD/NVME or on an unassigned drive. On default the "domain" share is sitting on the cache drive. So fine so far. It's on the user and the specific configuration how he set's up the VM. If you have a small cache SSD, let's say 128GB and you use it for caching your shares you should know how many data you put on your cache before the mover kicks in to transfer data to the array or of the share is cache only. You can overprovision a vdisk so for the VM itself it looks like a 128GB disk, where it's actually maybe only uses 30GB space. As soon as you fill up the VM's vdisk from inside the VM you more and more use space on the cache drive up to the point where used space by shares on cache + docker + vmdisk reaches the max amount possible even if Windows thinks 50 still free inside the VM and your VM will pause or crash. You should be aware of this.

×
×
  • Create New...