Mattaton Posted November 29, 2021 Share Posted November 29, 2021 I'm still very new to VMs (and unRAID too, for that matter). I have an existing VM that has run for 6 months or more. No issues. I moved everything to a new server build and got the existing VM running again. That took some doing as it appeared my libvirt file was corrupted and the VM didn't appear in the VMs list. I configured a new VM and pointed it to the old vm img and it worked fine. So, the next step was to pass through an add-on PCI USB controller. I did as Spaceinvader One did in this video (although the VFIO plugin is built-in). I have the controller showing in the VM config and added it, but now the VM won't start. If I remove the controller, then it boots fine. Any help is appreciated! Thanks! ap-archives-diagnostics-20211129-0818.zip Quote Link to comment
Mattaton Posted November 29, 2021 Author Share Posted November 29, 2021 Further testing... I tried creating a new Windows 10 VM with the same settings and passing through the controller and it also won't boot. So, it's not the VM img. Not sure if that's good or bad. 😕 Quote Link to comment
Mattaton Posted November 29, 2021 Author Share Posted November 29, 2021 I think there's are larger problem with the VM management on the server. libvirt and qemu logs have lots of errors. See newest diag file attached. ap-archives-diagnostics-20211129-1253.zip Quote Link to comment
Mattaton Posted November 30, 2021 Author Share Posted November 30, 2021 So, am I just screwed? Quote Link to comment
Recommended Posts
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.