Tom3

You probably need to create a bridge object in Docker that references the VLAN. There are 3 different things called bridges in Docker, so this gets confusing. See:

There's an updated version of libffi include in Nerdpack. Many thanks, that fixes the problem ! How does one mark this as SOLVED ? -- Tom

Hopefully this is the correct place to put this issue (per @Squid recommendation). -- Tom

I've installed iftop and iotop using nerdpack. iftop runs fine. Have rebooted since installing iotop, error doesn't change. UNRAID version 6.8.0 Trying to run iotop, yields the following error: root@Tower:~# iotop libffi.so.7: cannot open shared object file: No such file or directory To run an uninstalled copy of iotop, launch iotop.py in the top directory I am unable to find iotop.py: root@Tower:~# find / -name 'iotop.*' /usr/man/man8/iotop.8.gz /usr/doc/iotop-0.6/iotop.SlackBuild root@Tower:~# Libffi.so seems to be .6 rather than .7 root@Tower:~# find / -name 'libffi.so.*' /usr/lib64/libffi.so.6 /usr/lib64/libffi.so.6.0.4 Any advice as to how to fix this? -- Tom

Among many great features: Responsiveness to problems, issues, questions, etc. is the best feature. For what I would like to see in 2020: easier to create & manage custom docker / docker compose templates. -- Tom

Thank you for the advice ! Spin down delay just set to 'Never' on the cache. -- Tom

Here is the status: I am currently unable to re-create the original issue. However have discovered a problem that perhaps may have triggered it previously. I can start/stop and edit Ubuntu 18.04 , 19.04 VMs with no issues. These were installed under 6.7.2, and kept after the Upgrade to 6.8 Under 6.8 I was successful in installing Ubuntu 19.10 VM, and it runs fine. However, I cannot edit that VM (the VM is stopped when editing). Trying to edit a property (memory, CPU cores) then clicking apply results in: 1. The GUI never returns - it just hangs with the buttons greyed-out. 2. Trying to then start 19.10 results in it being dead - it goes directly into grub2 screen with no valid image found and asking to do a new install from scratch. I repeated these steps several times. 6.7.2 was never successful in installing 19.10 (nor upgrading 19.04 to 19.10 which fails in the middle of the upgrade becoming unbootable the same way), so 6.8.0 is a wonderful improvement there. - Tom

@limetech Thanks for all your help looking into this ! I have re-loaded 6.8 and am trying to methodically go through steps to see if there is a specific trigger that leads to the behavior. Last time this all happened after about 24 hours (or perhaps 10 or so VM start/stops). Will report back in a few days. -- Tom

The error happens when clicking "VNC Remote" in the drop-down menu after having started the particular VM. (Happens for all VMs). It happens in Windows Edge and Linux Firefox browsers. Resolved when I reverted to 6.7.2 -- Tom

Libvirt log from the above problem: 2019-12-17 03:52:50.664+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=10 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 03:54:15.784+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 03:54:48.864+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=11 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 03:54:48.864+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=11 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 04:03:27.375+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:05:34.833+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=12 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 04:05:34.833+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=12 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 04:16:33.072+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:17:08.712+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=13 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 04:17:08.712+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=13 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 04:18:53.269+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:20:13.009+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=14 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 04:20:13.009+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=14 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 04:31:47.002+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:31:57.890+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=15 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 04:31:57.890+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=15 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 04:33:26.044+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:55:23.921+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=16 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 04:55:23.921+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=16 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 04:59:35.632+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 05:00:19.488+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=17 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 05:00:19.488+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=17 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 05:05:25.075+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:37:03.012+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=18 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 14:37:03.012+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=18 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 14:37:47.027+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=19 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 14:37:47.027+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=19 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 14:39:12.190+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=20 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 14:39:12.190+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=20 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 14:40:06.579+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:41:17.254+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:44:05.842+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=21 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 14:44:05.843+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=21 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 14:50:54.226+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:51:05.707+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=22 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 14:51:05.707+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=22 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 14:51:56.053+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:52:00.842+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=23 name='Ubuntu-18.04-Server' uuid=c4b2ea8f-a0f6-f617-ec72-90a13d5f2a75 is tainted: high-privileges 2019-12-17 14:52:00.842+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=23 name='Ubuntu-18.04-Server' uuid=c4b2ea8f-a0f6-f617-ec72-90a13d5f2a75 is tainted: host-cpu 2019-12-17 14:56:20.832+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor

Had the exact same problem. Removing Libvirt.img and recreating did not solve. Downgrading to 6.7.2 resolved. Reported separately:

I also had the issue that trying to change the VM settings of an established (stopped) VM would also cause the GUI to spin forever. About a day later noVNC would throw an exception each time trying to start any VM (reported separately). I had NO red elements on the VM Manager GUI. Deleting and recreating Libvirt manually did not solve the noVNC exception issue. Can't give a 6.8 screenshot because have since reverted to 6.7.2. Reverted to 6.7.2, deleted all VMs and files, deleted Libvirt, re-enabled VMs (thus creating new Libvirt), re-created VMs in 6.7.2 and everything VM wise is working fine in 6.7.2 (as it did previously). My impression is that Libvirt created in 6.8 made 6.7.2 unhappy (after reverting). Perhaps there is some kind of file difference between Libvirt in 6.7.2 and 6.8 ? -- Tom

Libvirt log from the above problem: 2019-12-17 03:52:50.664+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=10 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 03:54:15.784+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 03:54:48.864+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=11 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 03:54:48.864+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=11 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 04:03:27.375+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:05:34.833+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=12 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 04:05:34.833+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=12 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 04:16:33.072+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:17:08.712+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=13 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 04:17:08.712+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=13 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 04:18:53.269+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:20:13.009+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=14 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 04:20:13.009+0000: 7708: warning : qemuDomainObjTaint:9168 : Domain id=14 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 04:31:47.002+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:31:57.890+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=15 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 04:31:57.890+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=15 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 04:33:26.044+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 04:55:23.921+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=16 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 04:55:23.921+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=16 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 04:59:35.632+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 05:00:19.488+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=17 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: high-privileges 2019-12-17 05:00:19.488+0000: 7707: warning : qemuDomainObjTaint:9168 : Domain id=17 name='Ubuntu-19.10-Desktop' uuid=41b55cb8-a5ab-f49b-522a-99d458bdebba is tainted: host-cpu 2019-12-17 05:05:25.075+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:37:03.012+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=18 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 14:37:03.012+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=18 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 14:37:47.027+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=19 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 14:37:47.027+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=19 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 14:39:12.190+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=20 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 14:39:12.190+0000: 7709: warning : qemuDomainObjTaint:9168 : Domain id=20 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 14:40:06.579+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:41:17.254+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:44:05.842+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=21 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: high-privileges 2019-12-17 14:44:05.843+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=21 name='Ubuntu-19.04-Desktop' uuid=efd9acde-a6c4-9beb-e9ce-297e49a47639 is tainted: host-cpu 2019-12-17 14:50:54.226+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:51:05.707+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=22 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: high-privileges 2019-12-17 14:51:05.707+0000: 7710: warning : qemuDomainObjTaint:9168 : Domain id=22 name='Ubuntu-18.04-Desktop' uuid=3cb0729f-f5d3-5459-b3fb-711bccc930c8 is tainted: host-cpu 2019-12-17 14:51:56.053+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor 2019-12-17 14:52:00.842+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=23 name='Ubuntu-18.04-Server' uuid=c4b2ea8f-a0f6-f617-ec72-90a13d5f2a75 is tainted: high-privileges 2019-12-17 14:52:00.842+0000: 7711: warning : qemuDomainObjTaint:9168 : Domain id=23 name='Ubuntu-18.04-Server' uuid=c4b2ea8f-a0f6-f617-ec72-90a13d5f2a75 is tainted: host-cpu 2019-12-17 14:56:20.832+0000: 7706: error : qemuMonitorIO:619 : internal error: End of file from qemu monitor

After several days of finally figuring out how to install VMs in 6.8 last night (separate thread), all of the VM's which were running fine last night now throw the following error: noVNC encountered an error: SyntaxError: import not found: supportsImageMetadata http://192.168.0.250/plugins/dynamix.vm.manager/novnc/core/display.js:11:9 noVNC Diagnostics attached. tower-diagnostics-20191217-0643.zip

Solved. Finally got VMs (including 19.10) installed under UNRAID 6.8. My Solution: 1. Assign all 16 cores to the VM for initial install. 2. Assign 8G minimum RAM. 3. Keep the VNC display window very small during installation. It requires scrolling through all subsequent windows. 4. Very quickly attach VNC to the VM when first starting so that the short grub timeout does not try to do a 'Try Ubuntu'. There are only a few seconds to get to the grub menu and select Install Ubuntu using up and down arrow keys. 5. Very quickly navigate to the installation buttons after the graphics comes up and be quick to click the buttons. Waiting just 2-3 seconds causes the CPU to go to 100% and the display, mouse, and keyboard goes unresponsive for all time (well an hour at least). This is the select language 1st page. 6. Similarly, go through pages 2,3, and 4 fast. Don't read anything as any delay will cause the whole thing to go unresponsive and lock up. 7. Once at about the 5th page of the Ubuntu install menu it seems to be better behaved, and one can take enough time to enter a name, password for Ubuntu, etc. 8. Complete the install with very small VNC window size. Once through the power down and reboot cycle, then the VNC window can be enlarged. 9. After the VM normal shutdown 2nd time, the VM can be edited to select fewer cores, less memory, etc. and it seems to run OK tried with 1920x1080 Ubuntu display size. NOTE: I successfully edits 3 VMs, but the fourth won't let me edit the VM.. Clicking apply after changing the number of cores just causes the UNRAID GUI to spin for a long time. My server does not have a dedicated graphics card, just a VGA card enough to configure the BIOS. It runs headless. I don't know what is going on here, but the appearance is that during the VM startup/install phase that the graphics/mouse/keyboard is consuming huge amounts of server resources enough to cause it to lock up. -- Tom

Update - was able to install and run Ubuntu 18.04 Server VM with no issues both in 6.7.2 and 6.8. There is no gui, all command line and text menus based. -- Tom

I changed back to 6.8 and reproduced the problem. Created diagnostics and submitted a report. I have upgrade / downgraded multiple times in the process, and now it is not possible to install VMs of any vintage in either 6.7.2 or 6.8 . I setup in 6.7.2, disabled VMs, deleted libvirt (using the VM manger GUI). Then rebooted. Now in either OS version, when I start to install a VM I get the grub menu, select Install Ubuntu, Ubuntu starts up and goes to the first menu (Installation, Select Language) and the assigned CPU cores go to 100% and stay there. At this point the VM GUI is unresponsive. I left it for an hour with CPU cores pegged at 100% but it made no further progress. Perhaps the downgrade from 6.8 left some file changes unreverted? So the next question - how do I restore the flash from the backup created before starting this adventure? It is as easy as just copying the files from the ZIP over on top of the flash, or is something more needed? Diagnostics attached. -- Tom tower-diagnostics-20191216-2350.zip

One more piece to the puzzle. If I manually edit domain.cfg on the flash to enable VMs, then reboot, the VM's will come up showing enabled. However the GUI still will not change the VM enable state using the VM manager. -- Tom

Further to the repost. I downgraded to 6.7.2, stopped the VM Manager, used the delete Libvirt checkbox to delete libvirt.img Then re-updated to 6.8, now VM Manager reports that the VM is stopped, but am now unable to Enable VM via VM manager. -- Tom

Decided to revert Unraid to 6.7.2 and the VM problems seem to have cleared up. The VM Manger can now disable / enable VMs. The images shutdown fully and the VMs stop (as they used to). Not sure I'm brave enough to try installing 19.10 yet. Maybe later. -- Tom This is the last issue I had under Unraid 6.8, trying to start a previously working VM caused a noVNC exception: noVNC encountered an error: TypeError: ({_listeners:null, addEventListener:(function(type, callback) { if (!this._listeners) { this._listeners = new Map(); } if (!this._listeners.has(type)) { this._listeners.set(type, new Set()); } this._listeners.get(type).add(callback); }), removeEventListener:(function(type, callback) { if (!this._listeners || !this._listeners.has(type)) { return; } this._listeners.get(type).delete(callback); }), dispatchEvent:(function(event) { if (!this._listeners || !this._listeners.has(event.type)) { return true; } this._listeners.get(event.type).forEach(function (callback) { callback.call(this, event); }, this); return !event.defaultPrevented; })}) is not a constructor http://192.168.0.250/plugins/dynamix.vm.manager/novnc/core/rfb.js:36:16 @http://192.168.0.250/plugins/dynamix.vm.manager/novnc/core/rfb.js:36:16

Unraid 6.8. I have docker disabled. All VMs are stopped. When I select Settings -> VM Manager -> Enable VMs -> select No then click APPLY, nothing happens and the VMs remain enabled. I recall this used to work, but has been several versions ago that I last tried. -- Tom

Thanks, does not fix the issue. I have noticed however that the VM's created under 6.7 have listed on the Virtual Machines status page GRAPHICS: VNC:auto while the one created under 6.8 lists GRAPHICS: VNC:5900 That's the only difference I can see. The SHA256SUM of the 19.10 ISO on the Unraid disk is the same as the SHA256 downloaded from the Canonical download site. So I'm pretty confident that the ISO is good. -- Tom