• 6.6.2 - virsh "believes" VM's are down when they are up


    cybrnook
    • Solved Urgent

    In WebUI, I selected my VM and "Restart". VM restarted no issues, however, WebUI and virsh believes they are both "shutdown". This is an issue as if I was to shutdown now, there would be no graceful shutdown of my VM's.

     

    image.thumb.png.79805a7973cc5ff3b06febbebf80a050.png




    User Feedback

    Recommended Comments

    Manually shutting down my seaBIOS based Ubuntu 16.04.5 VM with: "sudo shutdown -h now" does shutdown the VM, and I can then restart the VM and it registers.

     

    It's when you "Restart" from WebUI it get's lost.

    Edited by cybrnook
    Link to comment

    Same issue for me. Upgrade from 6.6.1 went fine except that a VM that autostart with Unraid first shows as started and as soon as i restart the VM no matter if inside the VM or within UnRaid it shows as "not started". 

     

    1362006142_virsherror.JPG.d993b860bd301eb88932a66a719f8d09.JPG

    Link to comment

    Looks to just be isolated to Linux VMs.  All of my Windows VMs work as expected when doing a "Restart" from the web UI context menu.  Still looking in to why this is happening...

    • Like 1
    Link to comment
    16 minutes ago, eschultz said:

    Looks to just be isolated to Linux VMs.  All of my Windows VMs work as expected when doing a "Restart" from the web UI context menu.  Still looking in to why this is happening...

    It's not just the webui, os level gets confused as well. Check out the screenshots we gave above.

     

    It does actually restart the VM, and they come back up. It just never registers it did and you get stuck.

    Link to comment

    I downgraded libvirt from 4.8.0 to 4.7.0 and I'm not seeing this issue anymore.  Unraid 6.6.1 was using libvirt 4.6.0 but there was a rare bug that affected json parsing that was fixed in 4.7.0.

     

    So libvirt 4.7.0 it is.  At some point i'll bisect the changes between 4.7.0 and 4.8.0 to see which commit is the culprit.

    • Like 1
    Link to comment
    4 hours ago, eschultz said:

    Looks to just be isolated to Linux VMs.

    It's also happens when restarting a Windows 7 VM from the webui for me. 

    Link to comment
    9 hours ago, eschultz said:

    I downgraded libvirt from 4.8.0 to 4.7.0 and I'm not seeing this issue anymore.  Unraid 6.6.1 was using libvirt 4.6.0 but there was a rare bug that affected json parsing that was fixed in 4.7.0.

     

    So libvirt 4.7.0 it is.  At some point i'll bisect the changes between 4.7.0 and 4.8.0 to see which commit is the culprit.

    Thanks for staying with this, and not dismissing it. Very much looking forward to getting back on the latest release of unraid.

    Link to comment
    On 10/17/2018 at 12:51 AM, eschultz said:

    I downgraded libvirt from 4.8.0 to 4.7.0 and I'm not seeing this issue anymore.  Unraid 6.6.1 was using libvirt 4.6.0 but there was a rare bug that affected json parsing that was fixed in 4.7.0.

     

    So libvirt 4.7.0 it is.  At some point i'll bisect the changes between 4.7.0 and 4.8.0 to see which commit is the culprit.

    Will this come in 6.6.3? Or perhaps a upcoming beta?

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.