VM Oddities 6.6RC1

To investigate this better, the complete XML file is required. This is not included in the diagnostics, but requires manual upload.

Perhaps you can highlight which part in the XML file you change that causes the issue.

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Gaming-VM</name>
  <uuid>76af2bd6-4e74-336b-3f6c-65c01e933f66</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>33554432</memory>
  <currentMemory unit='KiB'>33554432</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>16</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='32'/>
    <vcpupin vcpu='2' cpuset='1'/>
    <vcpupin vcpu='3' cpuset='33'/>
    <vcpupin vcpu='4' cpuset='2'/>
    <vcpupin vcpu='5' cpuset='34'/>
    <vcpupin vcpu='6' cpuset='3'/>
    <vcpupin vcpu='7' cpuset='35'/>
    <vcpupin vcpu='8' cpuset='4'/>
    <vcpupin vcpu='9' cpuset='36'/>
    <vcpupin vcpu='10' cpuset='5'/>
    <vcpupin vcpu='11' cpuset='37'/>
    <vcpupin vcpu='12' cpuset='6'/>
    <vcpupin vcpu='13' cpuset='38'/>
    <vcpupin vcpu='14' cpuset='7'/>
    <vcpupin vcpu='15' cpuset='39'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/76af2bd6-4e74-336b-3f6c-65c01e933f66_VARS-pure-efi.fd</nvram>
    <boot dev='hd'/>
  </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='16' 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>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='3a:cb:76:d8:4e:71'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x42' slot='0x00' function='0x0'/>
      </source>
      <rom file='/mnt/user/domains/Asus.GT1070edited.rom'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0b' slot='0x00' function='0x3'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0a' slot='0x00' function='0x3'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x41' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x43' slot='0x00' function='0x3'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

 

Below is what I added and its from the guide below.

<hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x41' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </hostdev>

Edited September 2, 2018 by Jerky_san

Step 1: I created a new VM using your XML file (excluding the part which you added later)

Step 2: I added the hostdev part

Step 3: switched to Form view and changed cpu pinning assignment. This works

Step 4: changed memory from 32G to 16G. This works

 

I don't start the VM upon creation because I don't have a NMVE device, but all appears to work when the VM is never started. Can you do a similar test?

40 minutes ago, bonienl said:

Step 1: I created a new VM using your XML file (excluding the part which you added later)

Step 2: I added the hostdev part

Step 3: switched to Form view and changed cpu pinning assignment. This works

Step 4: changed memory from 32G to 16G. This works

 

I don't start the VM upon creation because I don't have a NMVE device, but all appears to work when the VM is never started. Can you do a similar test?

So I can't replicate completely as it automatically populates my NVME into every windows 10 machine now for some reason. Don't know why exactly. But I created a Test machine, opened XML, added a single return, saved, then tried to add a processor and it fails.

Below is a video I recorded of it. Sorry if I am wonky with the mouse didn't get much sleep last night. ;-; kids bringing things home from to make you sick sucks..

https://drive.google.com/open?id=1ShZvbaFHSyd9aO5FbxXd2qLrd_uq5_T1

 

Should also mention the space is gone and it didn't even save it but appears to gimp me afterwords.

Edited September 2, 2018 by Jerky_san

You get the same creation error which was reported by other people as well.

This is under investigation.

 

(thanks for the video, it made the issue clearer to understand)

One thing I noticed. Some options are missing in the creation of the vdisk. A completely new VM has these:

Perhaps the image is already existing in your case?

1 hour ago, bonienl said:

One thing I noticed. Some options are missing in the creation of the vdisk. A completely new VM has these:

Perhaps the image is already existing in your case?

You are correct on that. I had set the test up as test2 but guess I forgot to put the 2 in the video. Without the .img file being present during creation it will still get the error as shown in the video.

Changed Status to Retest

Was fixed by RC2

Changed Status to Solved