Unraid out of memory problems again!!


Recommended Posts

1 hour ago, dlandon said:

You have some strange vdisk and CDROM mappings.  Why is your primary vdisk mapping in the configuration twice?

 

Why are you mapping the vdisk directly to a disk?  Set it to cache disk or other disk in the array or Unassigned Disk device.

 

Once the Windows 10 VM is installed, remove the CDROM mappings.  The drivers are not needed any longer.

 

This is more of what I would expect as a Windows VM mapping.

2082787346_VMMappings.png.026ae1bec5414d712db059a6b17cc638.png

 

Other suggestions:

  • Make VM changes xml changes.  You have some strange settings.
  • Cut down the CPU usage to: 4/10 and 5/11 for Windows 10 and 2/8 and 3/9 for Ubuntu.  Neither one should require that many CPUs.  Change later if desired once system is stable.
  • Cut down memory to 4 to 6 GB for Windows.  Cut own Ubuntu to memory to 4 to 6 GB.  Adjust later once system is stable.  I think you are over committing memory.
  • Install the Tips and Tweaks plugin and adjust the disk caching as suggested.

Hi, I followed Spaceinvaderone's guide to be able to boot from a separate drive? I've added my XML as the screenshots I copied the drive mapping twice it actually is only mapped once! I have just tried to map the drive as unassigned, it seems the drive has to be mounted for the system to see it but the form hangs on updating and doesn't do anything?

 

Tips and Tweaks plug-in already installed and adjusted as suggested.

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Windows 10</name>
  <uuid>032e02b4-0499-0511-6306-3d0700080009</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='8'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='9'/>
    <vcpupin vcpu='4' cpuset='4'/>
    <vcpupin vcpu='5' cpuset='10'/>
    <vcpupin vcpu='6' cpuset='5'/>
    <vcpupin vcpu='7' cpuset='11'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-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/032e02b4-0499-0511-6306-3d0700080009_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='4' threads='2'/>
  </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='writeback'/>
      <source dev='/dev/disk/by-id/ata-KINGSTON_SA400S37240G_50026B768284793D'/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:36:ca:92'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc05b'/>
      </source>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0d8c'/>
        <product id='0x0014'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1a2c'/>
        <product id='0x0c21'/>
      </source>
      <address type='usb' bus='0' port='3'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
</domain>

 

Link to comment

Please follow my suggestions until you get stability.

  • Cut down the memory on both your VMs to 4 to 6 GB.  You can increase it later once you achieve stability.  I think you are over committing memory.
  • Assign only 4 VCPUs to the VM.  You are way over committing CPUs and a Windows VM doesn't need that much.  If you do really need more CPUs, you can add them later.

Tips and Tweaks disk cache should be like this:

536307414_TispandTweaksSettings.png.66fd8b712766df559718352aecb54231.png

It would be better to mount the disk in UD and then assign the vdisk to that.

Link to comment
59 minutes ago, dlandon said:

Please follow my suggestions until you get stability.

  • Cut down the memory on both your VMs to 4 to 6 GB.  You can increase it later once you achieve stability.  I think you are over committing memory.
  • Assign only 4 VCPUs to the VM.  You are way over committing CPUs and a Windows VM doesn't need that much.  If you do really need more CPUs, you can add them later.

Tips and Tweaks disk cache should be like this:

536307414_TispandTweaksSettings.png.66fd8b712766df559718352aecb54231.png

It would be better to mount the disk in UD and then assign the vdisk to that.

Ok  I've done everything you suggest except mounting the drive through UD because when I select it the form hangs on updating?

Link to comment
1 hour ago, MothyTim said:

Ok  I've done everything you suggest except mounting the drive through UD because when I select it the form hangs on updating?

I don't have much experience with using a disk directly, but I suspect the format is not a vdisk file, but a NTFS file system and that's why it won't work with UD.  As long as the VM works, you should be good to go.

 

Now monitor and see if you have memory issues again.  Only make one change at a time to see if you can find out what is causing the problem if it still exists.

Link to comment

If memory issues still linger, go to a command line and type 'df' to see the file system usage.  Post the results.

 

1 hour ago, bastl said:

@MothyTim Does it happen if you dissable all your docker?

That's the next thing to do if the memory issue is not solved.  Disable all Dockers and re-enable them one at a time.  A mis-configured Docker can consume a lot of memory in the ram file system.

Link to comment
1 hour ago, dlandon said:

If memory issues still linger, go to a command line and type 'df' to see the file system usage.  Post the results.

 

That's the next thing to do if the memory issue is not solved.  Disable all Dockers and re-enable them one at a time.  A mis-configured Docker can consume a lot of memory in the ram file system.

Diabling docker made no difference so I ran the command with everything running!

 

Linux 4.19.43-Unraid.
root@Tower:~# df
Filesystem         1K-blocks       Used  Available Use% Mounted on
rootfs               8065616     782840    7282776  10% /
tmpfs                  32768        308      32460   1% /run
devtmpfs             8093164          0    8093164   0% /dev
tmpfs                8177476          0    8177476   0% /dev/shm
cgroup_root             8192          0       8192   0% /sys/fs/cgroup
tmpfs                 131072        368     130704   1% /var/log
/dev/sdf1            7608512     452288    7156224   6% /boot
/dev/loop0              8832       8832          0 100% /lib/modules
/dev/loop1              6016       6016          0 100% /lib/firmware
/dev/md1          2928835740 2727639880  201195860  94% /mnt/disk1
/dev/md2          2928835740 2536558692  392277048  87% /mnt/disk2
/dev/md3          1952560688 1599520824  353039864  82% /mnt/disk3
/dev/sdh1          244198552  131603744  112011472  55% /mnt/cache
shfs              7810232168 6863719396  946512772  88% /mnt/user0
shfs              8054430720 6995323140 1058524244  87% /mnt/user
/dev/loop3           1048576      17588     925484   2% /etc/libvirt
//TIMS-IMAC/LaCie  976426672  838674548  137752124  86% /mnt/disks/TIMS-IMAC_LaCie
/dev/loop2          20971520   13311948    6536900  68% /var/lib/docker
shm                    65536          0      65536   0% /var/lib/docker/containers/5979b4bcfbfea0f8623ab4dffc815a684a1a37b30a652cd5f84cb12090fdb137/mounts/shm
shm                    65536          0      65536   0% /var/lib/docker/containers/34ba8b2b0e34d95ef94450f800a8537b139933a667ad3b55313313449acc0fc9/mounts/shm
shm                    65536          4      65532   1% /var/lib/docker/containers/843681987d72d49eb84ab4ab0697f682f4049142a4fdc4d4daea22cb12508b30/mounts/shm
shm                    65536          4      65532   1% /var/lib/docker/containers/9b64dfef3d6bf7fb75bc84248e43cead6e83db2d05b225afd2704bbaacca4505/mounts/shm
shm                    65536          4      65532   1% /var/lib/docker/containers/1e4af7eca0a742825257653caff23d640081d9663ff1304337bcab9c99acbbd6/mounts/shm
shm                    65536          0      65536   0% /var/lib/docker/containers/4d84190c20a0c6c6d89cad52a3019445e8b1635598f72b0ac764728516432d34/mounts/shm
shm                    65536          0      65536   0% /var/lib/docker/containers/a47f0c2767e689fe66c6b74603530fa52145a5978ffce5e588e505d6fb2fe92e/mounts/shm
shm                    65536          0      65536   0% /var/lib/docker/containers/2cce694be62bc90ac9c217888e4bf0d88b5d087c5a80a7ce5b7574e6babf8ecc/mounts/shm
shm                    65536          0      65536   0% /var/lib/docker/containers/84d6163c0e7e7fa233896769c0b5acb49d30211051ab899af4085ed84e86f2ea/mounts/shm
shm                    65536          8      65528   1% /var/lib/docker/containers/5d85f3de267ab5d7d72d3bb673a02437a329237016fada7e705a5e531f12f0f5/mounts/shm
shm                    65536          0      65536   0% /var/lib/docker/containers/489ce636aedca20b29d92bf83f87f66071cf2750e72e5cb813fe99f9d156bcad/mounts/shm
shm                    65536          0      65536   0% /var/lib/docker/containers/dd752b98ea8d1a145e558e4e51eb7cd561ab77eed505d08c16b7df1c4a0ecce8/mounts/shm
root@Tower:~# 

 

Link to comment

Ok so because Windows 10 is unusable on Unraid I thought I'd try Windows 7 as I have a licensed version unused! What a mistake! I guess Unraid just can't cope with running Windows!! First, it would hang on starting Windows screen not even launch the installer, so I searched the forum for clues and found out that you need to pin only one CPU! So I did that and set a low amount of memory and VNC graphics, the installer then ran ok! Now I'm trying to increase the CPU pinning and memory and pass through my Nvidia GPU, but whatever I change it hangs on boot! Before I throw the whole thing out the window anyone had this issue and know how to get around it?

 

My Windows 7 XML, it'll boot like this but not if I add anything!

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Windows 7</name>
  <uuid>64f05ecc-7793-25b0-3b55-34c65d97c91e</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 7" icon="windows7.png" os="windows7"/>
  </metadata>
  <memory unit='KiB'>6291456</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>1</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-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/64f05ecc-7793-25b0-3b55-34c65d97c91e_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='1' threads='1'/>
  </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='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Windows 7/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows7HP_SP1_64.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.171.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:df:2b:21'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-gb'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

Link to comment
1 hour ago, johnnie.black said:

You have other problems, I have 3 Windows VM always running on one of my servers, Windows Server 2012 R2, Windows 8.1 and WIndows 10, as many other users also have various Windows VMs.

Good to know! What are your settings compared to mine? Any obvious differences?

Link to comment

Given up with Windows 7 as no matter what I do I can not get a working install! I've just spent 3 days wasting a lot of time it seems! Now wish I'd spent that time wiping the whole system and giving FreeNAS a try! It's frustrating because the docker side of Unraid is so good! I tried installing with OVMF but had to reduce the CPU pinning down to 1 and use VNC for the install to start! Then no matter what I did I couldn't increase the CPU's or add my Nvidia GTX1050 GPU as passthrough without getting Windows has failed to load screen! So I tried SeaBIOS I could then pin as many CPU's as I wanted, but GPU passthrough would result in Error 43! Spent a whole day on that one! There are many posts both here and else where with lots of ideas tried them all and nothing worked! Then tried changing the install to OVMF and converting the system from MBR to GPT, deleting the MBR partition adding a EFI one and then rebuilding the boot as EFI but was back to needing the install disk to repair the install and that only runs with one CPU and no passthrough! So I was back where I started! 

 

A separate issue also fed up with timemachine failing every few weeks and wanting to do a new backup! This is meant to be a NAS at heart and it's not even able to do backups properly! Haven't tried switching to SMB this is possibly the moment to try that!

 

 

Link to comment

@MothyTim

 

Definitely sorry to see that you are having difficulties with your setup, but Unraid is not the issue here.  There are countless demonstrations (videos/testimonials) out there leveraging our software without the issues you're experiencing.

 

The vast majority of the time when users are having issues with virtual machines, it can be traced back to something with the hardware.  The easiest way to verify this is to simply remove all the physical device assignments from your virtual machines.  That means no GPUs, Sound Cards, Storage Controllers, Firewire devices, etc.  Get rid of ALL of them from your VMs.  Now try running them for a bit and see if you run into problems.  If not, start slowly adding them back one at a time until you start getting OOM errors again.  In addition, I would move to a completely stock configuration of Unraid both for plugins and your VMs.  Don't use your unassigned device to store the vdisk (for now) just to rule out any outliers on the issue.

 

In addition, once those memory problems start occurring, reboot the system into terminal mode (not the GUI), and using a local monitor, mouse, and keyboard, login to the console and type the following command:

 

tail /var/log/syslog -f

 

This will start printing the system log to the screen in real time.  Once a hang/crash occurs, take a picture of what's on the screen and post it back here for us to review.  This is the best way to figure out what process is causing the problems.

Link to comment

I think you need to be scientific in eliminating possible causes to identify the issue (e.g. following jonp's advice above).

 

Out of memory error is so generic that there's no choice but to go through everything one by one until you find the cause.

Just to illustrate, I myself have had out of memory errors due to:

  • A handbrake docker doesn't like a file it's transcoding and eats up a ton of memory. Linux (i.e. NOT just Unraid) doesn't know what is causing the OoM, it will usually just kick the process that currently eats up the most RAM, which just happens to be the VM in most cases.
  • Running 2 VMs that are not supposed to be run together (so use more RAM than I have available).
  • Using up memory too quickly on a single node (despite having plenty free RAM on the other node) - this is a Threadripper / multiple-CPU specific problem.
  • A (presumably) loose memory stick. Why "presumably"? Memtest passed for 48 hours and theoretically a loose memory stick should catastrophically crash the system and not scream "out of memory". Yet, the issue disappeared after I reseated all the sticks. This scars me enough that ever since, I have been re-pressing my RAM sticks down every time I open the case.
Edited by testdasi
Link to comment

@jonp

 

Hi Jon, thanks for the suggestions! Not sure but I may have progress! This morning I removed everything from my existing Win 10 VM inc the GPU (something I hadn't tried before) and then connected with RDP first I tried a bit of simple video editing in pinnacle studio 22 and then exported the video to mp4 this would always hang at around 27%, but this time completed with no errors! So I then moved on to try some music tagging with an auto-tagging and album art program, this would give an ooM error after about 4000 songs usually. Today it tagged 20,000 before the ooM error! This time though Windows remained responsive and I was able the end task the tagging program and shut Windows down normally! So windows has remained stable all day which is a novelty for me! I can't decide if the problem was Windows or if the Tagger just isn't that great! I think tomorrow I will try a clean install of Windows 10 in a normal vdisk as you suggested just to make sure there is nothing going on with the UD interface! Although not going to be able to test the tagger as only have about 8,000 songs to go!

 

I should say that while I was doing these tests in Windows everything else on the server was running as I need it to be and had no issues, so that's my small Debian VM running my PBX and 9 dockers inc Plex!

 

I would also like to achieve a Windows 7 VM as well at some point, but can't find any guides specific to that?

 

Link to comment
Ok, so it seems I spoke too soon! Just clicking start on the Windows 10 VM crashed the Unraid GUI!!! Really getting beyond fed up with this!! System wouldn't shutdown cleanly and had to do a hard reset! I really hate having to do that and almost never had to when it was running Ubuntu as server!
tower-diagnostics-20190609-1421.zip
Were you running a Windows 10 VM on your Ubuntu server?

Quick scroll through the thread and it all seems to be indicating an issue with virtualisation of a Windows 10 install to me.

Have you tried all the things people have suggested above? Specifically reducing the amount of RAM allocated to VMs?

Sent from my Mi A1 using Tapatalk

Link to comment
On 6/9/2019 at 5:23 PM, CHBMB said:

Were you running a Windows 10 VM on your Ubuntu server?

Quick scroll through the thread and it all seems to be indicating an issue with virtualisation of a Windows 10 install to me.

Have you tried all the things people have suggested above? Specifically reducing the amount of RAM allocated to VMs?

Sent from my Mi A1 using Tapatalk
 

Hi, sorry for the delay replying (work got in the way!).  Yes, I was running Windows 10 and 7 on Ubuntu and also a small Debian VM for my PBX! Debian ran all the time and I booted Whichever version of Windows as needed, which wasn't that often as I'd use the Ubuntu desktop for most things! I had docker for only UNMS and Tautulli. Plex, UNIFI etc were installed directly into the OS. Also had Ubuntu configured as a TimeMachine! All worked fine certainly no out of memory errors! There were annoyances mostly running out of disk space for media etc. The machine had an i3 and 8GB RAM at the time, I upgraded the CPU to an i7 and added another 8GB RAM when I upgraded to Unraid. Which is why I started this thread and am fed up with the memory issues being as I doubled the amount!

 

Yes Windows 10 VM is the main issue, I couldn't get Windows 7 to install with GPU pass through. But have got XP to install and works fine, although haven't tried GPU pass through as my graphics card is too new for XP!

 

Yes, I've tried everything suggested and thought I was getting somewhere until the random system crash on Sunday! It was strange as it's fine today and I've been experimenting and added back one by one my pass-throughs all still ok so a bit puzzled now! 

Cheers,

Tim

Link to comment

@jonp @testdasi

 

So I've found the problem! It seems it was the SATA card! Very hard to work out as it was only a problem when moving or dealing with large files! I realized that it only happened when I was accessing the 500gb hard drive (D drive in windows) that I use for capturing video and other large files that I don't need on the array or where I want speed of access. It is connected to a SATA card that I have passed through to the VM's. I was again trying to make a USB stick installer and it kept failing, crashing the whole system. I realised that the downloads folder was on the D drive so I tried it on the C drive and it worked fine! So I've swapped out the card and works fine from the D drive as well now!

 

I've also added a swap file, which also seems to have made a difference! I have a stable system at last!

 

Thanks for everyone's help and sorry for all my rants of frustration!! :)

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.