Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About ks2016

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Hello, Please add support for Kata Containers. Gaming in a VM based container with HW passthrough seems promising. Regards!
  2. Windows XP is listed in the VM templates, but not fully supported. In order to have better support for this OS, the following needs to be done: 1) Add support for floppy drives in the VM gui. Sample resulting xml: <disk type='file' device='floppy'> <source file='/path/to/your/viostor-31-03-2010-floppy.img'/> <target dev='fda'/> </disk> 2) In VM settings similar to virtio ISO image add possibility to download floppy image from: https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/
  3. Diagnostics in the attachment. nas-diagnostics-20181120-1258.zip
  4. I must admit you were correct when you wrote: "I have to say, they do make rather good motherboards" After initial stubbornness, they did provide the fix quite fast.
  5. They actually did fix it. I’m sorry for late reply. About the display under UEFI mode, we found other vendors have the same symptom too. After checking with the AMI, it’s a known behavior. However, our R&D team still helps to provide a solution for you. Please update the attached BETA BIOS P7.50G to check the result. I have tested the Asrock fix and confirmed it is working as expected. However, there seems to be another issue (this time with Unraid). I created a new report for that:
  6. 1) Boot in UEFI. 2) On boot menu select Unraid OS GUI Mode. 3) Wait for the boot process to complete. Expected: GUI is shown on host display. Actual: Black screen with blinking cursor is shown. Note: The WEB GUI is still working as expected and the system is perfectly usable. However, in case something would need to be done, it is not possible to interact directly with the host.
  7. 1) Open any existing VM in XML view. 2) Change icon. 3) Click Update button. Expectation: Icon is changed. Actual: Icon is not changed. Note: Doing the exact same procedure in Form View does work as expected.
  8. Seems to be fixed in 6.6.5: "Improved Docker and VM settings consistency" Tested to be as expected. Thank you!
  9. Using tabbed interface in Unraid. Go to any of the following: - Main->Cache Devices or - Main->Boot Device Click refresh on the browser. Expected: After refresh the active tab is the same as before. Actual: The active tab is changed to Array Devices. Also note that tabs: - Main->Unassigned Devices - Main->Array Operation Work as expected (they stay on same tab on refresh).
  10. After more than 10 days of ping-pong with Asrock. There is finally some light at the end of the tunnel: Thank you so much for providing the video to us. Finally, we got the point and can see the same symptom in our lab. I reported this bug to our relate team.
  11. Works like a charm. VM's with passthrough devices have memballoon=none. VM's without passthrough devices have the standard memballoon. Windows 10 VM is rock solid just by not having the memballoon when using dedicated VGA. Thanks for the assistance.
  12. Exactly as you describe it. However, when you get that response after a 2 page step-by-step explanation that should make an idiot understand it. .... It gets me out of my skin.
  13. Proof that stupidity is limitless (Asrock response bug report regarding this issue): Thank you for sharing the result. The BIOS has two different mode called Legacy and UEFI. In the new generation of the BIOS, it’s all support the UEFI now, Intel Z170 platform also using the UEFI BIOS. There still have a lot of older devices on the marketing. Therefore, the UEFI BIOS build an option CSM (compatibility support module) to support legacy devices. That’s why the CSM function will influence your system.