In trying to get pfsense setup on my server, I set the VM to autostart, but since then, I'm unable to get sustained access to unRAID.  it will connect, let me see user shares, connect via putty and see the GUI, but not for more than about a minute.  After about a minute, I loose all connectivity.  I've tried to start in safe mode, to try unassigning one of my NIC's to not be available to unRAID, tried to quickly get to the VM tab and uncheck autorun, but after about an hour of mucking about, I'm no closer to having a usable server.

 

I'm out of ideas, short of killing the whole thing and starting from scratch with a new install; which I'd prefer to avoid if possible, as there are many dockers and VM's I don't want to have to re-create.

 

PLEASE help 

Been a while since I have used a VM on unRAID since I have dockers for everything I want to do.

 

My experience in general though is that anything that can be set in the webUI is stored somewhere on the flash and can be manually edited in a pinch.  So you may be able to turn off that VM autostart that way. Try looking in config/plugins/dynamix.kvm.manager for example.

Thanks for the guidance.  The location I needed was actually /ect/libvirt/qemu/autostart

 

I then deleted the .xml of the VM that was causing the problems, then rebooted, and was finally able to use the GUI.  I then tried starting it manually to see if I could make any progress, and killed the server again, but at least it's not autostarting and killing it before I can use it now.

 

Now I just need to figure out what's wrong with the VM and maybe I can take another step forward.

 

thanks again for the help

Thanks for the guidance.  The location I needed was actually /ect/libvirt/qemu/autostart

 

I then deleted the .xml of the VM that was causing the problems, then rebooted, and was finally able to use the GUI.  I then tried starting it manually to see if I could make any progress, and killed the server again, but at least it's not autostarting and killing it before I can use it now.

 

Now I just need to figure out what's wrong with the VM and maybe I can take another step forward.

 

thanks again for the help

/etc is one of the many places that is actually in RAM, only /boot and /mnt are not. Everything else gets unpacked fresh from bzimage,bzroot just exactly as it was when you got this version of unRAID. That is why I am pretty sure there is some place on flash where this is stored. I don't know why editing something in /etc would have survived a reboot. Possibly it was written to flash also by something when you made that change.

 

And I just looked into the bzroot archive. That autostart folder doesn't exist until something creates it during bootup.

Boot it into safemode, then it won't run any plugins, etc. When I am playing with a new VM I don't have it auto start until it works correctly.

Boot it into safemode, then it won't run any plugins, etc. When I am playing with a new VM I don't have it auto start until it works correctly.

I don't think VMs are considered plugins. At least when I tried safe mode that didn't help. I had to stop the VM autoloading before I could use the server again.

 

Unfortunately, at some point I have to hope the VM will work without testing it, because I'll need to assign both cards to it, and once I do, I can't get to unRAID to start it manually. Sort of a catch 22

/etc is one of the many places that is actually in RAM, only /boot and /mnt are not. Everything else gets unpacked fresh from bzimage,bzroot just exactly as it was when you got this version of unRAID. That is why I am pretty sure there is some place on flash where this is stored. I don't know why editing something in /etc would have survived a reboot. Possibly it was written to flash also by something when you made that change.

 

And I just looked into the bzroot archive. That autostart folder doesn't exist until something creates it during bootup.

Yeah, I don't know why it worked, but I had to do this a second time and it worked again.