same here with 2 win10 VM´s, since rc15 both are stable the intel gpu and nvidia one.

 

Before i had lots of Intel GPU VM lockups ... 

19 minutes ago, alturismo said:

same here with 2 win10 VM´s, since rc15 both are stable the intel gpu and nvidia one.

 

Before i had lots of Intel GPU VM lockups ... 

 

Not a typo above?  with -rc15 things are stable?

 

Some people are reporting VM issues starting with -rc15 (when we moved to 4.14 linux kernel).  FWIW, all our VM's are completely stable, no crashes, no unknown error messages (except @bonienl has a strange vmwrite error logged for some reason), that is to say: completely working.

I experience the same as sarf reports here. VM's run fine, but libvirt hangs during shutdown of a VM. My system is an Asus Prime Pro x370 with Ryzen 1600x. Only seen after upgrade to kernel 4.14.

well, i have then to join @bonienl here.

 

starting up my windows 10 VM (with passthrough'ed NVIDIA GPU) also logged these vmwrite errors (Call Trace) three times in a row – but: the VM started without any visible or experienced error so far. it seems to be stable. hadn't got these errors before (so that's a RC15e thingie).

 

though, i haven't since then rebooted nor did i shut it down, so can't report if i would see these hangs then, which some experience.

Edited December 11, 20178 yr by s.Oliver

Adding my diagnostics to see if it helps with the VM issues.  I'm trying to stop/force stop 'Buzz' a W10 VM that I've shut down, but unRAID shows it as still running.  When I try to stop/force stop it throws up the error message:

 

Quote

Execution error: Failed to terminate process 15774 with SIGKILL: Device or resource busy

Opening the VM tab is also very unresponsive and slow to load.

 

highlander-diagnostics-20171212-1117.zip

2 minutes ago, DZMM said:

Opening the VM tab is also very unresponsive and slow to load.

 

can't say that, all unRAID UI is lightning fast here.

Can someone tell me how to rollback to RC14. This freezing and locking of VMs when shutting them down is making it u usable.

Regards

9 minutes ago, naturalblue said:

Can someone tell me how to rollback to RC14. This freezing and locking of VMs when shutting them down is making it u usable.

Regards

Copy the files in the previous folder on the flash drive back to the root and reboot

3 hours ago, s.Oliver said:

 

can't say that, all unRAID UI is lightning fast here.

Just the VM tab - think it's related to the problems that are being listed

1 hour ago, naturalblue said:

Can someone tell me how to rollback to RC14. This freezing and locking of VMs when shutting them down is making it u usable.

Regards

I've had to give up and rollback as well.   I bookmark this site as it has all the old versions in one place - if you click on each release the stock version is also there

 

https://mirror.linuxserver.io/

Edited December 12, 20178 yr by DZMM

3 minutes ago, DZMM said:

I've had to give up and rollback as well.   I bookmark this site as it has all the old versions in one place

 

https://mirror.linuxserver.io/

If you're going to do that, just install the unRaid DVB plugin.  You can bounce around via its GUI

34 minutes ago, Squid said:

If you're going to do that, just install the unRaid DVB plugin.  You can bounce around via its GUI

True.  I have problems with that page loading sometimes e.g. it wouldn't load for me today

4 hours ago, DZMM said:

Adding my diagnostics to see if it helps with the VM issues.  I'm trying to stop/force stop 'Buzz' a W10 VM that I've shut down, but unRAID shows it as still running.  When I try to stop/force stop it throws up the error message:

 

Opening the VM tab is also very unresponsive and slow to load.

 

highlander-diagnostics-20171212-1117.zip

 

Any custom changes to your XML file?

1 hour ago, DZMM said:

I've had to give up and rollback as well.   I bookmark this site as it has all the old versions in one place - if you click on each release the stock version is also there

 

https://mirror.linuxserver.io/

Any custom changes to your XML file?

26 minutes ago, DZMM said:

True.  I have problems with that page loading sometimes e.g. it wouldn't load for me today

 

Does no good to post "won't work" without diags or anything for us to go on.

Is this just a issue with windows wms? I have no problem with my mac vm starting and stopping. BTW i use Q35-2.9 Q35-2.10 with all my vms to compare.

Edited December 12, 20178 yr by david279

8 minutes ago, limetech said:

Any custom changes to your XML file?

yes - I've got 3 W10 VMs with the same changes as this one, except for the GPU rom

 

<domain type='kvm' id='2'>
  <name>LEGO</name>
  <uuid>28bef482-fcbb-e5a2-f332-bc0fcbb1d293</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'>6</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='3'/>
    <vcpupin vcpu='2' cpuset='4'/>
    <vcpupin vcpu='3' cpuset='16'/>
    <vcpupin vcpu='4' cpuset='17'/>
    <vcpupin vcpu='5' cpuset='18'/>
    <emulatorpin cpuset='0,14'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.9'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/28bef482-fcbb-e5a2-f332-bc0fcbb1d293_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='3' threads='2'/>
  </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' discard='unmap'/>
      <source file='/mnt/disks/sm961/domains/LEGO/vdisk1.img'/>
      <backingStore/>
      <target dev='hdc' bus='scsi'/>
      <boot order='1'/>
      <alias name='scsi0-0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='nec-xhci'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='ide' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </controller>
    <controller type='scsi' index='0' model='virtio-scsi'>
      <alias name='scsi0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:33:4d:ed'/>
      <source bridge='br0.50'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target port='0'/>
      <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-2-LEGO/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='0x01' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <rom file='/mnt/disks/sm961/system/gt710.dump'/>
      <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='0x01' slot='0x00' function='0x1'/>
      </source>
      <alias name='hostdev1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc534'/>
        <address bus='3' device='10'/>
      </source>
      <alias name='hostdev2'/>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

 

7 minutes ago, david279 said:

Is this just a issue with windows wms?

Not all windows VMs, I have no problem with mine, and I run 3 (Win8.1, Win10 and Win Server 2012R2)

I'm seeing high emulator pin usage in an osx vm (90-100%). Have not tried others to confirm if it is an os dependent issue. Also, I did not run vm's on previous RC before this one so no comparison is available.(I changed pins and this seems to have put usage back in the 4-10% range) OSX vm appears fairly stable except when using device passthrough, it pegs all assigned cores to 100% at startup and holds there for a bit before showing the bios screen, then returns to normal.

 

I know osx isn't fully supported, but just sharing my findings.

Edited December 12, 20178 yr by 1812

1 hour ago, johnnie.black said:

Not all windows VMs, I have no problem with mine, and I run 3 (Win8.1, Win10 and Win Server 2012R2)

Might be worth posting your diags Johnny? If your windows VM's shutdown without issue, it may give the good people at unraid some comparisons to work with? it could be a motherboard type or manufacturer issue with the new kernel etc...  My windows VMs simply wont shutdown and lock up the server as per my post on page one...

My Windows Server 2016 VM seems to be working fine on rc15 however as stated above I get call traces (one per assigned tread) when the vm starts. No custom XML file. To get a clean log I rebooted the system, and then started and stopped the vm. Attached are my diagnostics.

servernas-diagnostics-20171212-1227.zip

3 minutes ago, sarf said:

My windows VMs simply wont shutdown and lock up the server as per my post on page one...

 

Any custom changes to your XML file?

13 minutes ago, sarf said:

Might be worth posting your diags Johnny? If your windows VM's shutdown without issue, it may give the good people at unraid some comparisons to work with? it could be a motherboard type or manufacturer issue with the new kernel etc...  My windows VMs simply wont shutdown and lock up the server as per my post on page one...

I can post the complete diags later if needed since all disks are spun down and I don't want to wake them, but this is the relevant syslog when I shutdown and restarted the win8 Win10 VM:

 

Dec 12 12:25:23 Tower1 kernel: mdcmd (97): spindown 4
Dec 12 16:14:16 Tower1 avahi-daemon[5409]: Interface vnet2.IPv6 no longer relevant for mDNS.
Dec 12 16:14:16 Tower1 avahi-daemon[5409]: Leaving mDNS multicast group on interface vnet2.IPv6 with address fe80::fc54:ff:febb:5aaf.
Dec 12 16:14:16 Tower1 kernel: br0: port 3(vnet2) entered disabled state
Dec 12 16:14:16 Tower1 kernel: device vnet2 left promiscuous mode
Dec 12 16:14:16 Tower1 kernel: br0: port 3(vnet2) entered disabled state
Dec 12 16:14:16 Tower1 avahi-daemon[5409]: Withdrawing address record for fe80::fc54:ff:febb:5aaf on vnet2.
Dec 12 16:14:18 Tower1 nginx: 2017/12/12 16:14:18 [error] 5460#5460: *1968278 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.9, server: , request: "GET /wsproxy/5702/ HTTP/1.1", upstream: "http://127.0.0.1:5702/", host: "tower1"
Dec 12 16:47:34 Tower1 kernel: br0: port 3(vnet2) entered blocking state
Dec 12 16:47:34 Tower1 kernel: br0: port 3(vnet2) entered disabled state
Dec 12 16:47:34 Tower1 kernel: device vnet2 entered promiscuous mode
Dec 12 16:47:34 Tower1 kernel: br0: port 3(vnet2) entered blocking state
Dec 12 16:47:34 Tower1 kernel: br0: port 3(vnet2) entered forwarding state
Dec 12 16:47:35 Tower1 avahi-daemon[5409]: Joining mDNS multicast group on interface vnet2.IPv6 with address fe80::fc54:ff:febb:5aaf.
Dec 12 16:47:35 Tower1 avahi-daemon[5409]: New relevant interface vnet2.IPv6 for mDNS.
Dec 12 16:47:35 Tower1 avahi-daemon[5409]: Registering new address record for fe80::fc54:ff:febb:5aaf on vnet2.*.

 

Edited December 12, 20178 yr by johnnie.black

2 hours ago, limetech said:

 

Does no good to post "won't work" without diags or anything for us to go on.

I did

7 hours ago, DZMM said:

Adding my diagnostics to see if it helps with the VM issues.  I'm trying to stop/force stop 'Buzz' a W10 VM that I've shut down, but unRAID shows it as still running.  When I try to stop/force stop it throws up the error message:

 

Opening the VM tab is also very unresponsive and slow to load.

 

highlander-diagnostics-20171212-1117.zip

 

Updated this morning - no issues that I can tell yet!