July 23, 20241 yr I stopped the Array, while being in the VM, which isn't the problem. The problem is that I changed the names of all the shares that I had made back in April 2023, from a blend of capital and small letters to all small letters, totally forgetting about Linux having problems with such things. haha After I stopped the Array, I couldn't get my main VM going or any of them for that matter. I could get the Ubuntu one starting quite easily, but the rest was basically dead in the water, so I deleted all of them and in order to get in here, I created the Fedora one that I'm on now. I usually set the source pathway to the VMs share, but what I noticed with the other one's before deleting them was that they were in the domains path, don't know why it was like that. Windows 10: I can probably get Win10 working without a problem since I could throw it a bone to where the vdisk image was, but Windows 11 on the other hand doesn't have a vdisk, it's installed on a m.2 NVMe disk that is passed through directly to the VM. So I can't find any vdisk info and thus not getting it to start at all. Windows 11:
July 23, 20241 yr Author I have yet to test if I can get it working, but I'm on the Win 11 install now. I had problems even starting it from the m.2, went into the bios and set the integrated graphics to auto instead of forced, because when I had it on forced, it would give me some glitchy graphical errors starting Win11. Now I'm going to restart into unRAID and test if Win11 will start again.
July 23, 20241 yr Author 34 minutes ago, Querzion said: I have yet to test if I can get it working, but I'm on the Win 11 install now. I had problems even starting it from the m.2, went into the bios and set the integrated graphics to auto instead of forced, because when I had it on forced, it would give me some glitchy graphical errors starting Win11. Now I'm going to restart into unRAID and test if Win11 will start again. I get a bluescreen as soon as it starts. I have no Idea why that is. Maybe I should create a new VM, and use the harddrive again. Here is the xml file : https://pastebin.com/aFYHS59H Edited July 23, 20241 yr by Querzion Added a pastebin link and picture.
July 23, 20241 yr Since this all started after renaming shares, I think you should be able to verify all your paths in VMs to correct. Changing from upper case to lower case letters would be the same as moving your data to a different location so your vms just got lost.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.