Win10 VM has been up and running for a while now without issue. Some things that rely on it were misbehaving so I rebooted it (VM not UNraid).  I usually use Chrome Remote desktop to access it, but that wouldn't come up like it normally does, so I stopped it and rebooted again.  It now doesn't come up at all and I cannot get into it with noVNC either as it will not accept the password.  I am suspecting that it was in the middle of doing to the Creators Update (maybe even on the screen where it tells you not to shut off the PC) when I killed it, so I'm guessing the image is corrupted and I have to start over.  Not the end of the world, but I thought I would throw it out here and see if anyone has any ideas.

 

I thought that CA backup was covering the VMs too, but apparently not the case. There is only one file on the whole image that would be very nice to have back. Is there a way I can mount the disk image to try and get ahold of it?

 

Here's the VM log, diag also attached:

 

2017-11-08 12:55:55.179+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.1, hostname: UNRAID
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10-Sage Drivers,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 10-Sage Driv/master-key.aes' -machine pc-i440fx-2.7,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -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/95548dcb-3a02-5498-1305-e592fc25308d_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid 95548dcb-3a02-5498-1305-e592fc25308d -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Windows 10-Sage Driv/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -devchardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev 'socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10-Sage Driv/org.qemu.guest_agent.0,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,password -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 vfio-pci,host=82:00.0,id=hostdev0,bus=pci.0,addr=0x6 -device vfio-pci,host=81:00.0,id=hostdev1,bus=pci.0,addr=0x8 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on
Domain id=1 is tainted: high-privileges
Domain id=1 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)

unraid-diagnostics-20171108-0851.zip

Disregard the part about recovering the one file, I was able to get into the .img file with 7zip.  Would still like to know if there is anything to learn from the logs.