mikedpitt420

I installed a windows 10 VM using all the default settings and it has given me nothing but weird issues. Using the default graphics driver, the mouse periodically just stops working. I tried multiple fixes for this based on forum posts, and after reinstalling the virtio drivers the mouse worked again. For exactly one day. I have tried multiple mice, and nothing works. I managed to install teamviewer on the VM and remoted into the machine, and the mouse worked fine. I really don't want to have to remote desktop into my VM every time I need to administer it so I started trying other fixes. I have now got mouse control using the cirrus graphics drivers, but now I am limited to 800x600 resolution. I see many posts about this same issue. Is there really no way to run a windows 10 VM in unraid without it breaking like this? I am fine running the cirrus drivers, but I can't squint at the computer at 800x600. So my questions are: 1. Is there a way to run a windows 10 VM with QEMU drivers and have a working mouse? 2. Is there a way to increase the resolution with the cirrus drivers above 800x600? This is quite frustrating. I have been an unraid user for years and have nothing but loved it. That is, until I started trying to do VMs that are non linux. There has to be a solution for this and I am willing to try anything to get it to work so I don't have to build a whole different computer to run my smart home/camera software. Any help is GREATLY appreciated. I have been at this with help from some friends for days, and the best we have gotten to actually control the mouse is using the cirrus drivers and I am getting too old to see 800x600 not to mention I can't even click where I need to on that small a screen. I can post diagnostics if that would help solve these issues.

I am trying to follow Spaceinvaderone's windows 10VM installation. I have downloaded brand new ISO's from Microsoft, and VirtIO drivers. The VM boots to the "press any key to continue" which I do, and it just goes back to the Tiano screen and stays there. I have tried several different fixes I have found on the forums here, and none of them seem to work. I have tried using only one thread. I have tried using SeaBIOS. Any help is greatly appreciated.

I have tried stopping the array, unassigned cache drives, starting the array again, and I can still not see my old cache drive other than to format it.

I removed a cache drive from my system and installed a new one. I am trying to use UD to access the data on this drive. It is formatted BTRFS. UD sees the drive, but my only option is to format it. Is there another way to get at this data?

I have tried recreating this VM with the old vdisk1.img and it either will not start at all, or it does with oddly missing data. Is there a setting in the creation that I am missing? tower-diagnostics-20211008-0036.zip

This was not entirely accurate. Let me try to start again. I think I started my VM service again, thus creating a new libvrt file. I have backups of my vdisk1.img file. When I try to create a new VM with my vdisk1.img file, it does load, but seems to be missing a bunch of data. Is this expected behavior?

Changed cache drive, and no VMs exist any longer. All my ISOs and vdisk.img are located on the array. My libvrt ISO and windows installation ISO are located at /mnt/user/isos. My vdisk is located at /mnt/user/domains/Windows 7/vdisk1.img. I have tried to change these settings in the VM manager and the VM service will not start. Any help is appreciated. tower-diagnostics-20211007-2306.zip

I replaced my cache drive, and forgot about a VM that was on there. I can still mount it and access the disk image, but where do I find the XML? Or what is the best way to restore the VM ? I still have the same flash drive, and access to anything that was stored on the cache drive including the disk image.

Yup. Only choice I have at this point. Thanks

I was hoping that wouldn't be the case. I'll have no idea if the solder was bad or if it was the parity drive

So I lost 8 drives due to a completely moronic move and I have been repairing them one by one. I do not know which drives were which. I have been de soldering the BIOS chips of my old drives onto new PCBs and so far so good. I have managed to resurrect 3 of 8 dead drives so far. What I am curious about is this: when I finally get to my old parity drive and I plug it in and mount it, what will I see? I just was hoping to have some idea so when I do get to that one I know to just skip it.

@trurl I don't believe I have any saved but if there are some that still exist on the forum here they're the same disks so should still apply. Wow that's an impressive find man thanks!

I will do what squid said and just try to mount them as I can and the one I can't must be parity. Is just a shame I will probably have to burn a PCB on a drive without knowing before hand

Yes, all I have is a backup of my config folder and it was previous to this file apparently. Is there a way to get this info from the super.dat file? I mean it's not the end of the world if I order another PCB I can't use but it'd be great if I could skip it obviously

I don't seem to have this file in my config folder.