• 6.12.0-RC1 VMs do not display


    ross232
    • Solved Minor

    After upgrading to 6.12.0-RC1 Virtual Machines are not displaying. In the dashboard these are visible.

    If a VM was set to autostart it is actually running.

     

    Virtual Machines are correctly shown using virsh list-all:

     

    root@Tower:~# virsh list --all
     Id   Name                State
    ------------------------------------
     1    Fedora Silverblue   running
     -    Fedora SB           shut off
     -    Windows 11          shut off

    Screenshot_20230316_164336.png

    Screenshot_20230316_163727.png

    tower-diagnostics-20230317-0554.zip




    User Feedback

    Recommended Comments



    sure, there you go:

     

    cat /sys/devices/system/cpu/*/topology/thread_siblings_list|sort -nu
    0,4
    1,5
    2,6
    3,7

     

     

    Edit: Inspired by your question I just checked if I could edit the vms and interestingly enough edit is only possible for No 2 "WinServ" (although it takes a "longer" minute to load) for "DebServ" the edit screen won't load at all

    Edited by paddesb
    Link to comment
    1 hour ago, paddesb said:

    sure, there you go:

     

    cat /sys/devices/system/cpu/*/topology/thread_siblings_list|sort -nu
    0,4
    1,5
    2,6
    3,7

     

     

    Edit: Inspired by your question I just checked if I could edit the vms and interestingly enough edit is only possible for No 2 "WinServ" (although it takes a "longer" minute to load) for "DebServ" the edit screen won't load at all

    Have you removed vcpupinning from XML? Issue I am seeing the issue is due to no cpus pinned.

     

    Each VM should have a CPU. I can put a fix to stop the error stopping edit and vmmachines list from working.

     

    But can you also confirm if you goto setting cpupinning

     

    it has errors also. adding  via edit and change to XML should allow it to load correctly.

     after

    <vcpu placement='static'>1</vcpu>

     

    This
      <cputune>
        <vcpupin vcpu='0' cpuset='0'/>
      </cputune>

     

     

    image.png

     

    image.png

    • Thanks 1
    Link to comment
    1 hour ago, SimonF said:

    and @ThrashMan Can you provide the out of cat /sys/devices/system/cpu/*/topology/thread_siblings_list|sort -nu for me please.

     

    Hi Simon, interesting spot. Neither Pop-OS nor pfSense settings will open in 6.12 RC6. (see attached)
    pfSense:  starts ok.  All is virtual.

    Pop-OS:    starts ok.  All is virtual.

    Output:
    root@Tower:~# cat /sys/devices/system/cpu/*/topology/thread_siblings_list|sort -nu
    0,8
    1,9
    2,10
    3,11
    4,12
    5,13
    6,14
    7,15

     

    I'm happy to delete both VMs to see if that "fixes" the issue but I assume it would be more useful to get to the bottom of it as 6.11 has no issues with any of my VMs?

     

    Regards,

    Andy.
     

    image.png.987552b63e5b0edc5b27848cc908efd6.png

    Edited by ThrashMan
    Link to comment
    39 minutes ago, SimonF said:

    Have you removed vcpupinning from XML? Issue I am seeing the issue is due to no cpus pinned.

     

    yes, i had removed the vcpu-pinning.

    By adding one via console and rebooting the server, all is fine and well again 🙂

     

    in case someone else needs to know how:

       nano /etc/libvirt/qemu/<yourvmname>.xml

       and add/change the settings SimonF mentioned above)

     

    Thanks @SimonF!

     

    Have to ask though, why did removing the pinning "suddenly" cause the system to not display the settings? it was working perfectly without pinning all these years... 🤔

    Edited by paddesb
    Link to comment
    8 minutes ago, paddesb said:

     

    yes, i had removed the vcpu-pinning.

    By adding one via console (in case someone else needs to know how: nano /etc/libvirt/qemu/<yourvmname>.xml and add/change the settings SimonF mentioned above) and rebooting the server all is fine and well again 🙂

     

    Have to ask though, why did removing the pinning "suddenly" cause the system to not display the settings? it was working perfectly without pinning all these years... 🤔

     

     

    As part of the 6.12 PHP was upgraded to version 8+ this is more strict on some things. The in_array function now fails which is causing the issue as Unraid expects a pinned cpu, function just didn't fail previously. 

     

    You can fix but adding the following to your VMs, edit the VM and switch to XML. The template method is also broken with no vcpu pinning.

     

    after <vcpu placement='static'>1</vcpu>

     

    This
      <cputune>
        <vcpupin vcpu='0' cpuset='0'/>
      </cputune>

     

    I have created a PR that should cater for missing vcpu and allow the pages to work.

    Link to comment
    22 minutes ago, SimonF said:

     

     

    As part of the 6.12 PHP was upgraded to version 8+ this is more strict on some things. The in_array function now fails which is causing the issue as Unraid expects a pinned cpu, function just didn't fail previously. 

     

    You can fix but adding the following to your VMs, edit the VM and switch to XML. The template method is also broken with no vcpu pinning.

     

    after <vcpu placement='static'>1</vcpu>

     

    This
      <cputune>
        <vcpupin vcpu='0' cpuset='0'/>
      </cputune>

     

    I have created a PR that should cater for missing vcpu and allow the pages to work.

     

    Hi Simon,

    adding that to both XML resolved the "VMS" tab....all display correctly now.
    I had to reboot as LibVirt service failed to restart.

    • Like 1
    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.