Tom3

Members
 View Profile  See their activity

  • Posts

    104

  • Joined

  • Last visited

 Content Type 

Report Comments posted by Tom3

    noVNC errors

    in Stable Releases

    Posted

    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

     

    noVNC errors

    in Stable Releases

    Posted

    @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

     

     

    noVNC errors

    in Stable Releases

    Posted · Edited by Tom3
    add revert note

    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

     

     

    noVNC errors

    in Stable Releases

    Posted

    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

    Cannot disable VM

    in Stable Releases

    Posted

    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

     

     

     

     

    Cannot disable VM

    in Stable Releases

    Posted · Edited by Tom3
    fix typo

    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

     

    Cannot disable VM

    in Stable Releases

    Posted

    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