• Can't Update VMs


    BrianIsSecond
    • Minor

    Version: 6.6.6

    Problem: Unable to update a VM. After clicking "update," the button simply changes to "updating..." and never finishes.

     

    Replication Steps:

    1. Select VM and click "Edit"

    257824781_ScreenShot2018-12-31at7_00_46PM.png.92c99e426e0d9b5e229388895223bb36.png

     

    2. Change Name (or toggle "autostart"... just to test some kind of change😞

    2063111898_ScreenShot2018-12-31at7_16_38PM.thumb.png.8d5538cc9eca97c13b503c5e7cf93f42.png

     

    3. Click "Update".

    527490496_ScreenShot2018-12-31at7_01_09PM.png.e90e03cfc808e5a70b334a8120b483c8.png

     

    Other Notes: 

    If it helps to diagnose the problem, toggling "auto start" from the "Virtual Machines" main menu works perfectly (see image below). However, clicking into a specific VM via "edit", and then choosing "update", as mentioned above, does not.

     

    1219078241_ScreenShot2018-12-31at7_22_20PM.thumb.png.90c042b19d34a6d27cfbdeeca8b9437d.png

     

     

    • Upvote 1



    User Feedback

    Recommended Comments

    Updating VMs works perfectly alright.

    We need more information about your specific setup to understand your problem.

     

    1. Post a screenshot of your VM settings

    2. Post your XML file

    3. Post diagnostics

     

    Link to comment

    Another user stuck at updating

     

    I've also started experiencing this issue. Tried to change the available cores on a Windows VM and it hangs on updating. Replicated across a variety of browsers. Doesn't affect the other VMs. Can use Settings>CPU Pinning to still change cores through GUI. Editing XML manually will also update correctly.

     

    However, clicking update in Form View in that specific Windows VM will hang, no matter if a change is made or not.

     

     

    Link to comment

    I also encountered this issue. But only after the VM was renamed previosly.

     

    Here are my exact steps to reproduce this issue:

     

    Preparation:

    1. Create a new VM (settings doesn't matter), name it e.g. "VM-01"

    2. Click on "CREATE" -> The VM was created successfully

    3. Click on the VM, click "Edit"

    4. Change the name of the VM from "VM-01" to e.g. "VM-01 - renamed", click on "UPDATE"

    5. The name of the VM got updated successfully, but now the VM is in a broken state.

        This means you couldn't edit it again.

    Here starts the problem:

    7. Click on the VM again, than click "Edit"

    8. Now we can change anything, e.g. we add another core to the VM.

    9. If we now click on "UPDATE" -> the button simply changes to "updating..." and never finishes.

    10. We have to reload the Web-UI, and the changes havn't been applied

    Link to comment

    Same happened to me right now on 6.7.0 RC3.

     

    1: Created a new Win10 VM succesful

    2: Edit that VM and add a USB Device for example or a GPU or change the name, doesn't matter

    3: hit the Update button and it will never finish updating

     

    Picture below shows the current settings. 2 USB devices i had to add manualy cause the initial config couldn't been changed. Nothing else has been placed or changed in the xml after the first creation. 

     

    VM_update.thumb.png.e4ee832b61dee48196dc52d2b0a305b2.png

     

    <?xml version='1.0' encoding='UTF-8'?>
    <domain type='kvm' id='38'>
      <name>W10_4</name>
      <uuid>b7b73747-6358-d959-c4e5-563197f607e9</uuid>
      <metadata>
        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
      </metadata>
      <memory unit='KiB'>8388608</memory>
      <currentMemory unit='KiB'>8388608</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>8</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='4'/>
        <vcpupin vcpu='1' cpuset='20'/>
        <vcpupin vcpu='2' cpuset='5'/>
        <vcpupin vcpu='3' cpuset='21'/>
        <vcpupin vcpu='4' cpuset='6'/>
        <vcpupin vcpu='5' cpuset='22'/>
        <vcpupin vcpu='6' cpuset='7'/>
        <vcpupin vcpu='7' cpuset='23'/>
      </cputune>
      <resource>
        <partition>/machine</partition>
      </resource>
      <os>
        <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/b7b73747-6358-d959-c4e5-563197f607e9_VARS-pure-efi.fd</nvram>
      </os>
      <features>
        <acpi/>
        <apic/>
        <hyperv>
          <relaxed state='on'/>
          <vapic state='on'/>
          <spinlocks state='on' retries='8191'/>
          <vendor_id state='on' value='none'/>
        </hyperv>
      </features>
      <cpu mode='host-passthrough' check='none'>
        <topology sockets='1' cores='8' threads='1'/>
      </cpu>
      <clock offset='localtime'>
        <timer name='hypervclock' present='yes'/>
        <timer name='hpet' present='no'/>
      </clock>
      <on_poweroff>destroy</on_poweroff>
      <on_reboot>restart</on_reboot>
      <on_crash>restart</on_crash>
      <devices>
        <emulator>/usr/local/sbin/qemu</emulator>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/VMs/W10_test/vdisk1.img'/>
          <backingStore/>
          <target dev='hdc' bus='scsi'/>
          <boot order='1'/>
          <alias name='scsi0-0-0-2'/>
          <address type='drive' controller='0' bus='0' target='0' unit='2'/>
        </disk>
        <controller type='usb' index='0' model='nec-xhci' ports='15'>
          <alias name='usb'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
        </controller>
        <controller type='scsi' index='0' model='virtio-scsi'>
          <alias name='scsi0'/>
          <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
        </controller>
        <controller type='sata' index='0'>
          <alias name='ide'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
        </controller>
        <controller type='pci' index='0' model='pcie-root'>
          <alias name='pcie.0'/>
        </controller>
        <controller type='pci' index='1' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='1' port='0x8'/>
          <alias name='pci.1'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
        </controller>
        <controller type='pci' index='2' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='2' port='0x9'/>
          <alias name='pci.2'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
        </controller>
        <controller type='pci' index='3' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='3' port='0xa'/>
          <alias name='pci.3'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
        </controller>
        <controller type='pci' index='4' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='4' port='0xb'/>
          <alias name='pci.4'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
        </controller>
        <controller type='pci' index='5' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='5' port='0xc'/>
          <alias name='pci.5'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
        </controller>
        <controller type='pci' index='6' model='pcie-root-port'>
          <model name='pcie-root-port'/>
          <target chassis='6' port='0xd'/>
          <alias name='pci.6'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
        </controller>
        <controller type='virtio-serial' index='0'>
          <alias name='virtio-serial0'/>
          <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
        </controller>
        <interface type='bridge'>
          <mac address='52:54:00:c5:e3:5e'/>
          <source bridge='br0'/>
          <target dev='vnet0'/>
          <model type='virtio'/>
          <alias name='net0'/>
          <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
        </interface>
        <serial type='pty'>
          <source path='/dev/pts/0'/>
          <target type='isa-serial' port='0'>
            <model name='isa-serial'/>
          </target>
          <alias name='serial0'/>
        </serial>
        <console type='pty' tty='/dev/pts/0'>
          <source path='/dev/pts/0'/>
          <target type='serial' port='0'/>
          <alias name='serial0'/>
        </console>
        <channel type='unix'>
          <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-38-W10_4/org.qemu.guest_agent.0'/>
          <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
          <alias name='channel0'/>
          <address type='virtio-serial' controller='0' bus='0' port='1'/>
        </channel>
        <input type='mouse' bus='ps2'>
          <alias name='input0'/>
        </input>
        <input type='keyboard' bus='ps2'>
          <alias name='input1'/>
        </input>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
          </source>
          <alias name='hostdev0'/>
          <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/>
          </source>
          <alias name='hostdev1'/>
          <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x046d'/>
            <product id='0xc517'/>
            <address bus='1' device='4'/>
          </source>
          <alias name='hostdev2'/>
          <address type='usb' bus='0' port='1'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x8087'/>
            <product id='0x0aa7'/>
            <address bus='1' device='3'/>
          </source>
          <alias name='hostdev3'/>
          <address type='usb' bus='0' port='2'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x04fc'/>
            <product id='0x0003'/>
            <address bus='3' device='4'/>
          </source>
          <alias name='hostdev4'/>
          <address type='usb' bus='0' port='3'/>
        </hostdev>
        <memballoon model='none'/>
      </devices>
      <seclabel type='dynamic' model='dac' relabel='yes'>
        <label>+0:+100</label>
        <imagelabel>+0:+100</imagelabel>
      </seclabel>
    </domain>

     

    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.