snolly

Nope. Never did, not even when this VM was Win10. With Win10 no freezes whatsoever.

Used to when I first posted in here. Now on 6.11.1. Freezes occur in both versions.

Freezes with i440 here. One thing that might worth mentioning is that I have 6 out of 8 cores pinned to the VM. If I isolate all 6 cores in Unraid then the freeze occurs in a matter of minutes. If I isolate 4 out of 6 the freeze might occur after hours.

My windows VM is freezing so I think the issue is related to the thread This is part of my original post I now updated to the latest Unraid 6.11.1 and the latest Virtio-FS drivers. Freezes still occur. What I noticed (and that may help to figure out what is causing this) is this: My CPU is 8 plain cores (no HT). 0,1 are pinned to all docker containers. 2-7 are pinned to the Windows VM. If I isolate all 2-7 cores then Windows VM freezes in a couple of minutes. If I isolate 4-7 and I leave 2,3 free (still pinned to the VM) then Windows do not seem to freeze. Still, performance is better than no isolated cores at all but I would prefer to isolate 6 cores and pin them exclusively to my Windows VM. If you need any configuration or log files please let me know. Cheers.

Hello all, I am facing the exact same issue. Recently updated to Windows 11, in the first days all was OK. Then I learned that for my framedrops and audio stutters that I had since started using Unraid KVM the solution is to isolate the cores that I feed to the VM. That made a huge performance difference (in a good way) but at the same time the freezes started occuring. Same symptoms as the rest of the guys. I can see the Windows screen but it's unresponsive (I can't even move the mouse). Some things I did in the past few days: Isolated 6 out of the 8 cores of my Intel Core-i7 9700 CPU and used those for the VM. Unraid uses 0,1 and the VM 2,3,4,5,6,7 I pass through my Nvidia 3060 Ti, a USB pcie controller and an NVME SSD for extra storage. My vdisk is in the Unraid cache. I updated to the latest virtiofs (using the cd image) I changed my Win11 Virtual Memory from the vdisk to the directly attached nvme I am still on 6.10 btw I was about to create a new thread here asking for help and then I noticed this one, so here I am. As the rest of the people no useful logs show up about the freezes. Any help would be greatly appreciated.

Thanks for the swift reply. Why does this is reported then? === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. It makes things so confusing. It should say FAILED instead of PASSED. No?

Unraid disabled my Parity drive. Any SMART tests I run report PASS. I am not that good in reading these. I attach diagnostics and smart test results. Can you please help me? New drives are expensive, I want to buy one only if I really have to. Thanks earth-diagnostics-20220823-1952.zip earth-smart-20220823-1933.zip

Nope, it didn't. I managed to sell it and bought an NVidia 1050 ti Card instead. I don't like using custom unraid versions and patched kernels. I am hearing that 6700XT does not suffer from the reset bug, so when and if GPUs become reasonally priced again I might buy a flaghip GPU again.

In my case, when the 5700XT was on board the mobo would disable the iGPU if no monitor was attached to it. I had to use a dummy HDMI plug to keep it active in order to pass it to the Plex container.

So, today I started once again from scratch. I deleted macinabox related: ISOs Domains Docker AppData Docket Template Custom OVF Then reinstalled macinabox with default settings (Catalina, download method 1). This installed properly (as the previous time) and I reached the macOS Catalina desktop. I shut down the VM and took a copy of the vdisk. I then booted it up again and upgraded to big sur from system preferences. After a couple of restarts I ended up in the Big Sur desktop. Note that I never completed the SpaceInvaderOne video guide (involving opencore connfigurator etc). I will do that tomorrow now that I am in Big Sur. So, maybe natively updating to Big Sur breaks the VM after all the boot modifications described in Space Invader Video Guide.

I just installed catalina, kept a copy of the vdisk and now I am upgrading to big sur. Will let everyone know if that works.

To answer my own question, I did this and it works fine.

Hello all, I have watched the video carefully, I have deleted everything and started from scratch like 10 times, and I still cannot install Big Sur. I managed to install Catalina. What I do to retry: 1. delete docker container macinabox 2. delete container template 3. delete macinabox in appdata 4. delete downloaded isos 5. delete macOS vms 6. delete macos domains Issues that I face. - Scripts only installed if Catalina is selected - Big Sur with method 1 in download will always download Catalina - If method 2 is selected and VM is created when I run it I can see a black screen with a mouse cursor on the upper left corner. I cannot move that cursor and that's pretty much it. - At some point I managed to reach the installation process (with horrendous mouse offset), did all the UI navigation with keyboard and reached a point where installation would complain about network error and could not proceed further (I did not note down the error). I am pretty much stuck, I think if I try again Catalina with method 1 will succeed but my hands are tied as far as Big Sur is concerned. Any help, guideline or something would be appreciated. Cheers to spaceinvaderone for his tremendous efforts. There would be no Unraid without him. EDIT: I redid everything, Now at first VM start I get "guest has not initialized the display yet". Please note that I have a Windows 10 VM with GPU passthrough that I tried controlling again with VNC instead of the GPU and I get the same error there (GPU works). I am reading around that once you pass through a GPU, VNC gets broken. I thought that was the case for the specific VM, is it possible that it breaks VNC altogether? EDIT 2: Reducing VM memory by 500MB brought back the black screen with the cursor stuck on upper left corner.

Well, title says all, if anyone know whether this is possible please let me know

I bought myself a Pentium G5400 for 70 euros and it can HW transcode 4K HEVC without breaking a sweat. Awesomeness. Now if only plex would fix the washed out colors on HDR->SDR transcodes

Hello, does this work with 9th Gen Intel CPUs?

Has anyone managed to make an HP printer that is listed as "hpcups requires proprietary plugin". I can't make mine print.

Hello all, I have a radarr, sonarr, bazarr setup going on and up to yesterday I could not figure out why most of my hard drives in the array would not spin down (or spinning up all the time). I have: Dynamix Cache plugin so filesystem structure / folder and file names are stored in RAM to avoid disk spin up Plugin that logs which files were accessed (cannot remember its name) Disabled "ignore subs with wrong fps" in Bazarr because I guessed that it will need to access the actual movie file in order to figure the fps. Disabled "check for embedded subs" for the same reason as above. No matter the settings in Bazarr when search for subtitles is running, media files are accessed and disks spin up. One cannot change the interval of the search and the default is 3 hours. Having both English and a secondary (rare) language as wanted, this means that every 3 hour interval subtitle search will search for subtitles for tons of media and spin up most of my disks. I know Bazarr uses subliminal for the actual subtitle search and download. I shut down Bazarr container last night, spun down all my disks, woke up this morning and all disks are still spun down. Any feedback to have subtitle search that will not wake up my disks would be greatly appreciated! Cheers.