SHarmon5

Members
  • Posts

    1
  • Joined

  • Last visited

SHarmon5's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Greetings SpaceInvaderOne, First, really big fan, thank you for your contributions in the community. I've been working on creating your dual boot scenario for a week... honestly everyday for hours and hours but the windows vm never actually starts. When I start the VM(After creating the VM and then transplanting the UUID as instructed) I only see an image of the docker "thinking" with the circular arrows and the word "stopped" next to it, under the docker symbol. I've never actually seen it start up. What I'm working with: my windows copy is not activated because I copied it from a 2TB HDD to a NVME SSD and so now my UUID is 00000000-0000-0000-0000-"then a configuration of numbers and letters". So obviously I lost my activation in the transfer. So I've been using that unactivated UUID in my VM. My bios say that the NVME is in a LEGACY+UEFI boot so I don't know if that counts as UEFI or not. Because I'm trying to boot from the NVME SSD I attempted to passthrough my controller by putting "vfio-pci.ids=..........." in the syslinux configuration and after rebooting it get the error (in Fix Common Problems) the "vfio-pci.ids=.........." is not compatible with 6.9.2. I figured that was probably because the give you the option to bind it in system devices. My. controller is individual in the list so I don't need to separate it from a group. So I took it out and used that feature of the new UNRAID and it still did the exact same thing. I'm pretty new as you can probably tell but eager to learn. Thank you in advance for any help you can give.