Jump to content

jonp

Administrators
  • Content Count

    5971
  • Joined

  • Last visited

  • Days Won

    17

jonp last won the day on July 15

jonp had the most liked content!

Community Reputation

314 Very Good

About jonp

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • URL
    http://lime-technology.com
  • Location
    Chicago, IL

Recent Profile Visitors

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

  1. David literally JUST beat me to the punch on this. Thanks @david279! This is exactly what the user needs to do and should resolve the issue. Generally speaking, AMD hardware can be more problematic than Intel for various reasons, so if you want to have a smoother experience in the future, switch to Intel and NVIDIA.
  2. I will have to consult with someone else running xenserver but don't believe they are running what you are exactly. The tough part with NFS is that there are often times client-specific issues that can come up which seems to be the case here. Unfortunately without anyone else running this environment, it would be difficult for us to support this as a one off configuration. We will do what we can, but it may take some time. Stay current on the RC releases and let us know if this changes with updates we make there. Sent from my Pixel 3 XL using Tapatalk
  3. Maybe... [emoji57] Sent from my Pixel 3 XL using Tapatalk
  4. What about a bios update? Sent from my Pixel 3 XL using Tapatalk
  5. The answer definitely lies somewhere in the bios. Got a link to the manual? Sent from my Pixel 3 XL using Tapatalk
  6. Anyone else using this setup that can confirm issues? Sent from my Pixel 3 XL using Tapatalk
  7. Read through this thread and it sounds like the long and short of it is that if you don't pass through / use the USB C controller on the GPU, the lockups don't occur. Unfortunately with any type of hardware passthrough using KVM, this is a possibility. Hardware passthrough today works fairly well, but relies on a combination of the right firmware in the device and the right quirks in the kernel/KVM/QEMU. Over time, these things may improve, but for now, we lack the ability to provide any type of resolution on these hardware-specific issues.
  8. Try upgrading to a current version of XenServer. I have contacts that utilize XenServer 7 and later over NFS that do not report these issues. In general, NFS issues can occur when older clients try to connect to newer ones.
  9. This issue has been resolved. It came down to a script for auto renewal hitting an outdated endpoint on our provider. It's since been resolved. Let us know if anyone has any more issues at checkout.
  10. I see the same issue as you. We will get this resolved ASAP but given that it's nearly 4AM here, we will need to wait until our team is back online to address the issue. We appreciate your patience.
  11. Hi there, We don't officially "support" any OS. The way virtualization works, the underlying guest OS has to support the virtual drivers required by the hypervisor. There is nothing that we can do to change that. Please contact FreeBSD and ask them to add driver support for virtio or any other supported virtual network interface supported by KVM.
  12. Hi there, Upgrading a CPU won't cause Unraid not to boot. The software will run against any x86_64 processor. This is definitely a hardware issue. I don't know what you mean by group(0,0). Can you get any other OS to load or boot off USB? You'll need to figure out the hardware issues before we can provide any support.
  13. Changed Status to Open Changed Priority to Minor
  14. I can confirm this bug as I was able to recreate it today.
  15. Hi Carlos, Can I ask if you ever witness any negative impact as a result of this or is this more of just a "hey I'm seeing these messages and don't know why?"