Jump to content

JonMikelV

Members
  • Content Count

    46
  • Joined

  • Last visited

Community Reputation

10 Good

About JonMikelV

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. @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?
  2. 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.
  3. 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.
  4. Have you created other VMs successfully? Are you able to ping the VM once it's started?
  5. 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.
  6. 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)?
  7. 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. :-)
  8. 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. 🙂
  9. 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? :-)
  10. 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.
  11. Welcome @BrazMan! 1. Not having used torguard myself I can't say for sure, but I suspect you can keep using torguard VPN but exactly how it's done will depend on how you decide to run Plex. Will it be in a Docker container or a VM (running Linux or Windows 10)? 2. I see ToGruard Docker containers at DockerHub so it's likely there is one for Unraid, but I haven't checked yet. 3. See answer #1 (how to set up remote Plex access will depend on whether Plex is running in a Docker or VM but consider watching Spaceinvader One's excellent video on containers and VPNs). 4. See #1 (setting up direct GPU use depends on if Plex is running in Docker or a VM). Probably the "easiest" for you to relate to would be to put Windows 10 in a VM passing your video card through for direct VM use, then just do everything the same way you have been. However, that would not necessarily be taking the most advantage of using Unraid. To do that you might want to consider running Plex in a Docker.
  12. Here's what ultimately worked for me. ~~~ VM Config: Unraid Share: /mnt/user Unraid Mount tag: user ~~~ Addition to /etc/fstab: #2020-04-14 Sample auto-mount via "Unraid Mount tag" user /mnt/user 9p trans=virtio,version=9p2000.L,_netdev,rw 0 0 I've read that 9p is actually pretty bad for performance but I've never been bothered enough to figure out an alternative. 🙂 Note that I got a pretty big speed boost by adding msize=262144: user /mnt/user 9p msize=262144,trans=virtio,version=9p2000.L,_netdev,rw 0 0 Of course I only tested with a simple dd command, so YMMV: dd if=/dev/zero of=/mnt/user/testfile bs=1G count=1 oflag=direct; rm ~/mnt/user/testfile
  13. JonMikelV

    Chrome OS

    I'm a glutton for punishment so looked anyway - I can't get past "Booting 'local image A'".
  14. JonMikelV

    Chrome OS

    Thanks for the link @sharpfork. I had read through that as well and decided it sounded like a lot more work than it probably needed to be - at least here 2 years later. 🙂 What I've tried so far is: - download the CloudReady image from https://www.neverware.com/freedownload - unzip the cloudready-free-74.4.57-32-bit.bin (or cloudready-free-74.4.58-64-bit.bin) file into my ISOs folder - Create a VM with: + Logical CPUs: 2 + Initial & Max Memoru: 2G [min. spec. for CloudReady] + Machine: Q35-2.1 + BIOS: OVMF + USB Controller: 3.0 (qemu XHCI) [boots faster than USB 2] + OS Install ISO: path to cloudready-free-74.4.58-64-bit.bin + OS Install CDRom Bus: USB + Primary vDisk Location: Auto [created as 16G drive - again min. spec. for CloudReady] + Primary vDisk Bus: SATA + Graphics Card: VNC + VNC Video Driver: Cirrus [If you left the default of QXL (best) I didn't see any of the boot screens mentioned below] + VNC Password: <blank> + VNC Keyboard: English-United States (en-us) + Sound Card: None + Network MAC: <whatever defaulted> + Network Bridget: br0 + USB Devices <none> + Other PIC Devices: <none> With those settings, I am able boot the VM and see: - the "TianoCore" logo screen for about 3 seconds - a blank screen for about 8 seconds - the CloudReady boot logo for about 1 second - the animated "Your system is repairing itself. Please wait." page for about 3 seconds - the whole process start over Eventually I have to force-stop the VM. Per the Neverware support pages, this sort of boot loop is usually indicative of unsupported hardware of some sort so I've decided there may be something about the specific hardware my Unraid is running on that CloudReady doesn't like. I might be wrong, but I haven't made time to play around with anything else (like the 27 partition process in the link you provided).
  15. JonMikelV

    Chrome OS

    I doubt you'll hear much about actual ChromeOS. As far as I know Google doesn't provide any self-install type options (such as an ISO). That being said, ChromeOS is Google's customized version of the open source ChromiumOS (just like the Chrome browser is Google's customized version of the the Chromium browser). And just like how there are other customized versions of the Chromium browser (such as Brave, among others) there are other customized versions of ChromiumOS. This website has a nice comparison of the most common ones: - https://www.electromaker.io/blog/article/flint-os-vs-chromium-os-vs-cloudready-which-chrome-os-is-best To summarize it - as of Jan. 2019: - ChromiumOS - 'the original', open source, not necessarily the most polished or feature packed, - FydeOS (formerly FlintOS) - many variants (such as for RaspberryPi), supports Android apps, etc. - CloudReady (also formerly FlintOS) - more enterprise focused, supports CloudReady Linux apps, etc. So you might want to do some searching for ChromiumOS, FydeOS, or CloudReady and consider trying one or more of those as VMs on your Unraid box. If you, come on back and share your own experiences and thoughts! 🙂