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. In XML view set VNC password as: passwd=''. Start the VM. Attempt to connect to the VM using the web VNC client. Expected: Leave the password field blank and click on send password should establish the connection. Actual: The VNC client does not even try to authenticate if the password is empty. Bugs: 1) The VNC client should not make any validations on the provided password. Instead, whatever the user provides should be immediately forwarded to the server. 2) The form view section for the password should consist of 2 controls: checkbox and a textbox. Once the checkbox is checked, the attribute passwd should be added to the XML with value set to the contents of the textbox. Again, without any validation. Empty string is a valid password.
  2. On top of that, once you add password. You need to repetitively add the passwd='whatever' on every single edit to the XML because it gets removed. ARGH !!! At the moment neither form or xml view are fully usable. They should decide which view holds the truth. Since xml is feature complete, it would be good to have xml as source of truth. Next, if you edit the config in form view, they should start with the xml contents .... decide what they can handle and show it on screen. When clicking save, change ONLY the section of the xml that the user touched (instead of overwriting it). Finally, do something to have the passwd in the xml. It is VERY annoying and security risk to have to add it on every edit. Also, creating a new VM in XML view is completely useless as the initial xml is empty.
  3. Steps to reproduce: 1) Edit VM in XML view 2) Set CPU count to anything other than 1 (that is 2, 3, 4 ... ) - will refer to this count as X bellow 3) Remove the cputune section - no cpu pinning (maybe not needed to reproduce, but needed in my setup) 4) Set cpu topology to <topology sockets='X' cores='1' threads='1'/> (maybe not needed to reproduce, but needed in my setup) 5) Save the config 6) Edit the VM again, but this time in form view 7) Set VNC password 8 ) Save the config During second edit the CPU config has not been changed. Expected results: - CPU config should remain as configured in first edit Actual results: - CPU config is changed to <vcpu placement='static'>1</vcpu> <topology sockets='1' cores='1' threads='1'/> This might be an existing issue and not specific to this release. If the edits are reversed (first password, then cpu), the password is not present in the XML. I see two possibilities: 1) Allow the form view to specify CPU configuration without pinning and also topology or 2) If some section is not changed in form view, then don't update it when saving the VM config. But in the end, you are the experts.
  4. Regarding the line: "Primary vDisk Bus: IDE (needed to get past the error: "Setup did not find any hard disk drives installed in your computer")" Please try again using the sample I provided. You should be able to install the OS on virtio disks.
  5. Hello, When interacting with a VM using the web VNC client the keyboard shortcuts are not forwarded to the VM. As a result, pressing Win+L would lock the client instead of the VM. 1) Is it possible to configure the web VNC client to forward keyboard shortcuts to the VM? 2) How? 3) If the answer is no, then please add this feature. Regards!
  6. Hello, Please add support for Kata Containers. Gaming in a VM based container with HW passthrough seems promising. Regards!
  7. 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/
  8. Diagnostics in the attachment. nas-diagnostics-20181120-1258.zip
  9. 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.
  10. 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:
  11. 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.
  12. 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.
  13. Seems to be fixed in 6.6.5: "Improved Docker and VM settings consistency" Tested to be as expected. Thank you!