• VM management is not consistent

    ks2016

    By ks2016

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

     

     

     

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    itimpi

    I believe this is probably an instance of a long standing issue where once you have made any edits in XML mode then you can no longer edit that VM in form mode without potentially losing the edits made in XML mode.   I have wondered why a pop-up warning to this effect is not displayed when you try to switch back to form mode from xml mode.

     

    This is slightly aggravated by the fact that the toggle for xml mode is a global one and not specific to a VM.   If the underlying problem cannot be easily fixed then it would be useful if the system remembered the last edit mode used for a specific VM so that at least if you go into Edit mode then if you used XML mode you are taken straight there.

    Edited by itimpi
    Link to comment
    ks2016

    On top of that, once you add password. You need to repetitively add the passwd='whatever' on every single edit to the XML because it gets removed. ARGH !!!

    At the moment neither form or xml view are fully usable.

    They should decide which view holds the truth.

    Since xml is feature complete, it would be good to have xml as source of truth.

     

    Next, if you edit the config in form view, they should start with the xml contents .... decide what they can handle and show it on screen. When clicking save, change ONLY the section of the xml that the user touched (instead of overwriting it). Finally, do something to have the passwd in the xml. It is VERY annoying and security risk to have to add it on every edit. 

     

    Also, creating a new VM in XML view is completely useless as the initial xml is empty.

    Edited by ks2016
    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.