Hi unraiders,

Happy Birthday everyone, I brought along something very special for you all! I held off for over 6 months raising this issue here in the hope that something might change or that a solution from the Reddit community would bear fruit. The last time I was able to and tried to was prior to v7, and it hasn't worked on 7.1, 7.1.2, or 7.1.4.

The Reddit community hasn't provided much in terms of what I had hoped for and explicitly asked for. In the end, the realization came that I needed the kind of person Reddit wasn't going to give me. The general rhetoric became that "this noob doesn't have a clue." But I've been with unRAID for 15 years, and I'm not afraid to get my hands dirty.

The biggest issue for me, and for initially seeking community support, is that there is no error message. Simply, when I attempt to create a VM with any combination of settings and then click "Create," nothing happens.

I've ruled out it being a client-side issue by trying three different browsers across three different platforms. I'm at a brick wall and over 6 months behind on needing to spin up a VM (now with a waiting list).

So, in desperation, short of logging a ticket and hoping for help, I poked around enough to generate errors

I configured a VM, switched to XML mode, copied the contents, and then created a custom VM with the text I just copied. The "Create" button worked here and threw an error, "domain type not specified," or something similar.

Sure enough, <domain TYPE=""> was in the XML, so I entered qemu thinking my problems were over and tried again.

The error message this time is "No PCI busses available." Now I at least have something I can bring forth, but it feels like there might be a deeper issue here because the default interface should be throwing an error. If it did, my project wouldn't have been stagnant for so long.

So what is this error message actually telling me, and what do I need to do to resolve it? Or do we need to back up and understand why the domain TYPE was never defined and/or get word to the company devs that there might be a bug in the interface?

Or D: None of the above, but please, can anybody give me tasks to get this issue resolved?

I'm attaching the diagnostics and default VM XML just to cover all the bases.

Thank you so much to anyone who comes to my aid

yoda-diagnostics-20250803-1416.zip defaultVM.xml

55 minutes ago, Nasha said:

Thank you so much to anyone who comes to my aid

not really clear, this also happens when you as sample try to create a VM via Form ? not only when you try to just copy / paste some xml code ?

one thing i would consider, your target Share Name ... "VM's" ... special character like this ... not really a good choice, may try renaming or test with standard "domains".

from your logs there is nothing to see for me besides thousands of lines from docker/s restarting ... may also take a look there which docker is constantly restarting, makes no real fun looking through your logs like this ... ;)

37 minutes ago, alturismo said:

not really clear, this also happens when you as sample try to create a VM via Form ? not only when you try to just copy / paste some xml code ?

one thing i would consider, your target Share Name ... "VM's" ... special character like this ... not really a good choice, may try renaming or test with standard "domains".

from your logs there is nothing to see for me besides thousands of lines from docker/s restarting ... may also take a look there which docker is constantly restarting, makes no real fun looking through your logs like this ... ;)

Docker - I was unaware, where'd you see the flooding (log?) - makes sense why it took unusually lint to generate the logs

My target name hasn't changed, but I know the manager was overhauled so I will try this. Not a good choice, or not entirely confirming to Linux generally accepted foldername schema? If I look back 20yrs ago I would expect problems, just like editing scripts in notepad was a no-no. I'll remove the punctuation and we'll see .

Via.form NOTHING happens as in click create and nothing happens.

Everything you've said tells me that limetexh have a bug and if foldermames isnt the issue then there's nothing else wrong wo back to where I started :(

Edited August 3, 2025Aug 3 by Nasha

Resolved - removed the libvert image now all is well.

When I stopped and started VM it logged a strange error that it was already running

15 minutes ago, Nasha said:

Everything you've said tells me that limetexh have a bug and if foldermames isnt the issue then there's nothing else wrong wo back to where I started :(

actually im running many VM's on different systems without any issues ...

standard, gvt-g, sr-iov and vfio passthrough ... so no, i wouldnt say there is a bug as then this forum would be flooded ...

may also try to wipe the libvirt image and redo that one (vm service stop / delete / vm service start), may that helps too ...

1 minute ago, Nasha said:

Resolved - removed the libvert image now all is well.

perfect, enjoy now ;)