ks2016

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.

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.

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.

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.

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).

After each restart of the Windows 10 VM, the Nvidia VGA drivers are marked with error code 43. Please note that this is only after restart. If I shut down, then start the VM all seems to be fine. This makes me think that the VGA on restart is in some inconsistent state causing the error code 43.

1) Create a VM with VNC VGA. 2) Copy the XML of the VM (XML-1). 3) Configure VGA passthrough. 4) Copy the XML of the VM (XML-2). 5) Remove the VGA passthrough (go back to VNC). 6) Copy the XML of the VM (XML-3). Expectation: XML-1 = XML-3 Actual: 1) XML-1 != XML-3 2) More devices are present in the XML-3. 3) Initialization is much slower for the VM with XML-3, leading to "the device still has not initialized display" in VNC viewer. Replacing the VM config (XML-3) with the contents of XML-1 makes the initialization as fast as original. XML-1.xml XML-3.xml

In VM settings, I set PCIe ACS override to BOTH. Then, I have stubbed 3 devices as preparation for passthrough. pci-stub.ids=10de:1c03,10de:10f1,1033:0194 > lspci -k 01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 6GB] Kernel driver in use: pci-stub 01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) Subsystem: eVga.com. Corp. GP106 High Definition Audio Controller Kernel driver in use: pci-stub 09:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) Kernel driver in use: pci-stub So far it seems the devices are stubbed. Issue: When Unraid starts it outputs the command line text on the stubbed graphics card and there is no output on the onboard one (non-stubbed). 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) Subsystem: ASRock Incorporation HD Graphics 530 Kernel modules: i915 When I try to start a VM configured to use the discreet VGA there is only garbage on the screen.

I have 2 networks defined on the server: - 1x Gb port on the mainboard - 4x Gb ports on add-on card configured with link aggregation (802.3ad). These ports are connected to Zyxel 1900-24E. The switch is configured to handle the aggregated ports. I make sure all is configured and working on the server, then reboot the server. On next reboot, only the on-board port is working. The other are down. Issues: - Non-main ports participating in LAG group in state DOWN have "Port Down" as text on the button. Expected: the text should be "Port Up" as the port is already down. - Clicking "Port Down" on a port in LAG group has no effect. - Clicking "Port Up" on main port in LAG group brings only the main port UP. This in combination with the above results in complete inability to change status of participating port. At this point I have to disable the LAG so I can bring participating ports UP. But, first I need to stop VM Manager. Once VM manager is stopped and the LAG disabled, I can bring the ports up. After couple of UP-DOWN-UP, I enable the LAG and then VM Manager. I had the same setup with same hardware on old USB (last Unraid version there was 6.5.3). I hadn't encountered this issue then. It is VERY frustrating to go through this procedure, please help.

It is not possible to customize the USB if local zip is selected. As a result, if UEFI boot is needed, the image must be downloaded every time.