JonMikelV

Members
  • Posts

    51
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

JonMikelV's Achievements

Rookie

Rookie (2/14)

17

Reputation

  1. Wow - your patience with idiots like me is incredible! Turns out I've spent HOURS (days?) trying to find (or create) the "extra parameters" field in "Show more settings..." when I really just needed to toggle the "Basic View" / "Advanced View" switch in the upper right of the page. D'Oh! I wonder if I was confusing myself with the Docker overview page "Advanced View" (that shows the CPU & memory) thinking it was the the Docker *EDIT* page "Advanced View" that I needed. Either way, all resolved - thanks!
  2. Hmm... I'm sure I'm not confusing the CPU percentage shown above the line with the memory usage shown below it. I guess trying to explain what I was thinking of just made my post more confusing, not less. 😞 I must be incorrectly using the --memory parameter from: I've tried this test as EXTRA_PARAMETERS and standalone Variable values with & without double-dashes but still see max memory in the usage column: Resulting in: Sorry for turning this into a standard Docker question - am I able to move the discussion out of Feature Requests?
  3. On the Docker tab, the "Advanced View" helpfully shows memory load as "currently used" / "system memory". But if this is truly memory LOAD should it reflect usage of the "--memory" parameter? For example, if I have a container using 8G of memory on a 32G server it shows as "8.00 GiB / 32.00 GiB" which suggests 25% usage, but if the container were run with a "--memory=10G" parameter then the container would actually be at 80% usage. On a related note, it might be nice to include a total docker numbers - like the total CPU & memory used by ALL dockers.
  4. I've played with a few VMs created from scratch without (much) issue, but in testing migrating a physical box to a VM I'm running into super slow disk IO (like 100-200 KB/s max). I'm wondering if because the .img file was created outside of my no-COW "domains" folder, maybe it "carried in" the C attribute when I moved it under "domains"? I tried lsattr on the file but end up getting an "lsattr: Inappropriate ioctl for device while reading flags" error. Does anybody have any suggestions on how to check Copy On Write attribute for a file in Unraid or know if it is removed when a file is moved (or copied) into a no-COW folder?
  5. @Zudnic, did you create the `/mnt/user/ubuntudata` folders before running the `mount` command?
  6. @pmeth, intuerrupts is a good thought - are you passing through any hardware (even USB ports) that might be getting grabbed by the first machine then appear unavaiable to the second?
  7. I've recently started having issues where No VNC connections to my VMs randomly lock up after anywhere from 10 min. to 10 days. The VM page shows them still running and I can ping the machines, but any No VNC connection (not matter from what 'client') just connects but shows the VM screen from the time of the lockup (based on the clock). I have been getting around it by force-quitting and restarting the VM but would prefer to figure out how to diagnose and resolve this. The only VMs I use long enough to notice the issue are both Ubuntu based, if that is likely to matter.
  8. I'm no good at reading the diagnostics, but does the issue go away if you allocate specific CPUs to specific VMs? I've run into similar issues VM crashing issues if I run multiple VMs where the sum of the allocated memory is too close to actual system memory.
  9. Have you created other VMs successfully? Are you able to ping the VM once it's started?
  10. it looks to me like you CAN create the VMs and they do boot, but the installs "fail out" when trying to do network access during the installation? If that's the case, sounds like one of your listed changes (probably not Letsenrypt) might be the culprit. Is your Jitsi IP range in the 192.168.86.xx address space seen in the second image? I'm wondering if your VMs are connecting to the IP range and not finding a DHCP server to give them an IP address.
  11. I assume you're not attempting any video card pass through? As @Vannie suggested, ports might be an issue - does the built in Unraid VM page "VNC Remote" feature give the same issues as standalone viewers? When you get the blank screen are you still able to ping the VMs (or even connect to any shares that might exist)?
  12. JonMikelV

    Chrome OS

    Thanks for sharing! I may give PrimeOS a try one of these days, but a while ago I gave in and picked up a cheap Chromebook at a holiday sale to play with. Figured it was cheaper than all the time I was spending fighting with the VM. :-)
  13. Why the bashing? Just because I don't know Proxmox doesn't mean I don't know VMs. (Plus you confirmed it's not supported - seems a solid suggestion to me.) One person's "bullshit" is another's avoidance of technical details about drive exposure until sure the audience is ready for it. You shouldn't feel the need to apologise for your opinion, it's just as valid as anybody else's! Plus, thanks to you I know more about Proxmox use that I did before. 🙂
  14. Installing Unraid would replace Win 10. If you don't need Win 10 functionality you could run Plex in Docket container in Unraid. This is likely the most effective way to do it. If you still want Win 10 on the box then you'd have to create A VM and install Windows in that VM. At that point you could run Plex in the Win 10 VM instead of (or in addition to) an Unraid Docker container. If using a VM then performance will vary depending on what physical hardware you pass through (dedicate) to the VM. For example, a default VM see a generic video card which means if you wanted something running in the VM to use you the GPU on your physical video card you would have to pass it through to the VM. Does that answer your questions or did I make things worse? :-)
  15. If you're planning to play with Unraid under Proxmox that should be fine but I wouldn't recommend it for long term use. I know little of Proxmox but I would guess that Unraid wouldn't have the right kind of drive access to safely "do it's thing" if running in a Proxmox VM.