6.8.2 Win10 VM shows started but is not. *SOLVED*

[xlucero1]

I haven't upgraded to 6.9 and 6.10 yet because I use the VM for work & worry about nextcloud data, passwords & losing photos. I can, and plan to upgrade soon, especially if this is the easiest solution. 
- My server was maxed out on storage last night; so I was using the VM to clean the server/media/array (working fine).

- I cleared the Recycle Bin plugin which had over 100GB of data. (maybe I deleted something in here, yet was working fine before)

- *The vdisk1.img I noticed is using used 75gb, even though I only allocated 70gb to it originally. (suspect. I turned off VM around 1230ish).

- I am noticing my "isos" and "vdisk" shares are set "yes" to use cache, but they seem to be in the array (disk 1).

- My cache pool is a little more fuller than usual as well. (invoking mover did nothing, before and after long shutdown and reset).

- Lastly, I get no errors when I start the VM, here is the VM log from when I click start, no force close. The keyboard is not even allowing me to turn on LED on it, although the keyboard works in the GUI. The Unraid login script goes away on the display when I start VM, but no sign of VM life whatsoever on display. 

 

Thank you all who help build an amazing community!

 

ps note: my diagnostics posted were pulled after several resets. Unfortunately I have a bad habit of restarting before pulling them. I have pasted a copy of the working XML into the advanced settings; also turning off and on VM manager, and nothing. 

tower-diagnostics-20220711-1408 copy.zip

Edited July 29, 2022 by xlucero1
SOLVED

[itimpi]

8 hours ago, xlucero1 said:

- I am noticing my "isos" and "vdisk" shares are set "yes" to use cache, but they seem to be in the array (disk 1)

That is where they are MEANT to end up with the Yes setting.    You might want to read the help built into the GUI about how this setting works and the action (if any) that mover subsequently takes.

[xlucero1]

8 hours ago, itimpi said:

That is where they are MEANT to end up with the Yes setting.    You might want to read the help built into the GUI about how this setting works and the action (if any) that mover subsequently takes.

Thank you for reminding me about that feature. Should the vdisk location be set to use cache "only"? Also I set the VM to be 70G, now it seems to have exceeded 70G now it is 75Gb... Do you think this is why it's not booting; if so, how can I fix/resolve this to get back into my VM? or what stands out to you that might be the issue? Thank you again

[JorgeB]

5 minutes ago, xlucero1 said:

Also I set the VM to be 70G, now it seems to have exceeded 70G now it is 75Gb...

VM section uses binary units, so 70G is 70GiB, and that's 75.16GB.

[xlucero1]

I made a new Win10 VM reusing all the old info and files (same machine, ISO, virtio, manually chose old vdisk, and same network Mac), and it booted up!! I didn't even have to modify the XML file and paste old info in, it just created it and booted. Now the truth is if it will keep working going forward after shutdown. 
Any input or ideas?

Thank you for responses

Edited July 12, 2022 by xlucero1