Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About pederm

  • Rank
  • Birthday 09/28/1959


  • Gender

Recent Profile Visitors

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

  1. I faced a similar problem on my Asus x370 board after a BIOS update. According to Spaceinvader Ones excellent video, please ensure that the IOMMU setting in BIOS is changed from Automatic to Enabled. After that when setting pcie_acs_override, the hardware passed through as before.
  2. Installed 6.5.3-rc1 on my Ryzen system, apparently no change to boot-time of my Ubuntu Bionic VM with GTX1050-passthrough.
  3. @AhmedI changed the ip-address to the host-name in the remote line of the ovpn-file and it started working.
  4. Running Ryzen, I at some point got the impression, that turning off address space layout randomization (ASLR) would provide a more stable environment. I have therefore added this to the go script: echo 0 | tee /proc/sys/kernel/randomize_va_space I actually dont know whether this (still) is a good idea. Also it seems to provide a more stable Ryzen system when adding the rcu-nocbs option (substitute the number of cores minus one for 11): label unRAID OS kernel /bzimage append rcu_nocbs=0-11 initrd=/bzroot
  5. After several hours of VM usage, no trouble closing it down. The qemu issues indeed seems to have been fixed.
  6. Ran an Ubuntu VM for more than 30 minutes and closed it down. No trouble, it worked fine and the qemu process exited as expected. Afterwards I was able to start a new session. I will runn this session for a couple of hours and hopefully be able to close it with no trouble also.
  7. The Ubuntu VM closes down, all looks ok. But in htop, the qemu process is marked with a red D in the S column, and a new start of the VM gives an error stating the VM is already running. I have recreated the problem, but the diagnostics file does not show much as far as I can judge. asus-diagnostics-20171230-1137.zip
  8. The problem seems to persist for my installation. The Ubuntu VM with passthrough Nvidia GTX 1050Ti and a USB 3.0 hub runs fine for hours, but never closes down properly.
  9. Still the same trouble, Ubuntu VM runs fine for hours and shuts down normally. But libvirtd never cleans it out, and it is not possible to start a new instance, only Unraid reboot works.
  10. A quick successful restart of my Ubuntu VM with Nvidia passthrough on an Asus x370 Prime Pro seems to confirm that the problem with hanging VM's have disappeared. Edit: Unfortunately, my VM once again did not shut down, requiring a server reboot. It had been running for many hours, and the symptoms were the same as before.
  11. I experience the same as sarf reports here. VM's run fine, but libvirt hangs during shutdown of a VM. My system is an Asus Prime Pro x370 with Ryzen 1600x. Only seen after upgrade to kernel 4.14.
  12. I PCIEX16_1 is an old AMD Redwood graphics card, which is exclusively used by Unraid. In the PCIEX_2 slot is the Nvidia 1050Ti located. A dedicated mouse and keyboard is also used exclusively by Unraid.
  13. On my Asus Prime x370 Pro, I have updated BIOS to the latest 3203, and in this BIOS I enable SVM in order to allow Virtual Machines to run. In the Unraid syslinux.cfg I specify two options for my Ryzen 1600x: rcu_nocbs=0-11 processor.max_cstate=1. With the latest beta of Unraid 6.4, it runs with my Nvidia 1050Ti as passthrough for any OS. For Windows 10, I use OVMF and No to Hyper-V.
  14. I had to disable C-states in BIOS in order to avoid freezes with my Ryzen 1600X. It is called AMD CBS on my Asus Prime x370. Previously I also had to disable multithreading (SMT) and Nested Page Tables (NPT), but it is not necessary with the 6.4 prerelease based on Linux 4.13.
  15. With the release of kernel 4.12, it might be a god idea to get a rc7 based on 4.12? Perhaps the IOMMU changes will benefit those of us doing hardware passthrough?