Ok, my appdata, domains, and system shares are now only on the cache: 

 

New diagnostics file:

server1-diagnostics-20190328-2313.zip

OK that looks good. Go ahead and try your VM again. If you still have a problem we might have to get somebody else to take a look.

OK, I enabled the vm & tried to set up my Windows vm as usual. 

Now, there is no execution Error like before. But it won't start. It only shows me a terminal when I use vnc. 

 

Vm-Log: 

ErrorWarningSystemArrayLogin

qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
qxl_cursor: not implemented: type 1
2019-03-26T18:49:01.833348Z qemu-system-x86_64: terminating on signal 15 from pid 12580 (/usr/sbin/libvirtd)
2019-03-26 18:49:02.059+0000: shutting down, reason=shutdown
2019-03-27 20:01:04.999+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Server1
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-Windows 10/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/4f89194b-cfee-a0e1-c769-dd2db0317b61_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -uuid 4f89194b-cfee-a0e1-c769-dd2db0317b61 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=27,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbu0,id=serial0 -chardev socket,id=charchannel0,fd=31,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:1,websocket=5701 -k de -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
2019-03-27 20:01:04.999+0000: Domain id=2 is tainted: high-privileges
2019-03-27 20:01:04.999+0000: Domain id=2 is tainted: host-cpu
2019-03-27T20:01:05.043084Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/2 (label charserial0)
2019-03-27 20:01:14.203+0000: shutting down, reason=failed
2019-03-27 20:02:38.643+0000: shutting down, reason=failed
2019-03-27 20:03:48.392+0000: shutting down, reason=failed
2019-03-27 20:04:07.083+0000: shutting down, reason=failed
2019-03-27 20:05:44.669+0000: shutting down, reason=failed
2019-03-27 20:10:15.128+0000: shutting down, reason=failed
2019-03-27 20:10:17.735+0000: shutting down, reason=failed
2019-03-27 20:11:24.939+0000: shutting down, reason=failed
2019-03-29 07:16:15.710+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Server1
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 10/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/e5246ee0-d6b9-d344-1b89-953e4f233599_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 4608 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -uuid e5246ee0-d6b9-d344-1b89-953e4f233599 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=26,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbu0,id=serial0 -chardev socket,id=charchannel0,fd=30,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -k de -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
2019-03-29 07:16:15.710+0000: Domain id=1 is tainted: high-privileges
2019-03-29 07:16:15.710+0000: Domain id=1 is tainted: host-cpu
2019-03-29T07:16:15.754041Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
2019-03-29T07:24:06.973386Z qemu-system-x86_64: terminating on signal 15 from pid 487 (/usr/sbin/libvirtd)
2019-03-29 07:24:07.173+0000: shutting down, reason=destroyed
2019-03-29 07:26:07.985+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Server1
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-Windows 10/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/2c128405-9d4a-3e78-8c2a-fb11412148a7_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 5632 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 2c128405-9d4a-3e78-8c2a-fb11412148a7 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=26,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbul0,id=serial0 -chardev socket,id=charchannel0,fd=30,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
2019-03-29 07:26:07.985+0000: Domain id=2 is tainted: high-privileges
2019-03-29 07:26:07.985+0000: Domain id=2 is tainted: host-cpu
2019-03-29T07:26:08.028318Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)

 

And the diagnostics:

 

 

server1-diagnostics-20190329-0845.zip

Unfortunately I'm out of my depth here. Since dockers were introduced I haven't needed any VMs. Wait and see if anybody else replies.

4 hours ago, trurl said:

Unfortunately I'm out of my depth here. Since dockers were introduced I haven't needed any VMs. Wait and see if anybody else replies.

Ok, thanks anyways!

 

//do you think I can install my dockers now, or should I wait?

Edited March 29, 20197 yr by Einzigstes

I think your dockers should be OK.

 

It was libvirt.img that was corrupt. But I think if you recreate it from scratch you would have to setup your VMs again. I don't suppose you had a backup of it?

On 3/29/2019 at 7:40 PM, trurl said:

I think your dockers should be OK.

 

It was libvirt.img that was corrupt. But I think if you recreate it from scratch you would have to setup your VMs again. I don't suppose you had a backup of it?

No, never made any

How would I recreate it?

 

 

 

--UPDATE

Switched vm's off & on. Now, my windows vm appears to be running.

I hope that everything is ok now.

 

Thanks for your help! 

Edited March 30, 20197 yr by Einzigstes