After the recreation of the VM all seams to be ok for a while. But today, again, the VM is working properly, but I cannot manage it from the web GUI.

From myunraid.net I can see my vm

 

but from  the vms page I don't

Do they show on dashboard?

Hi SimonF, no, they don't

46 minutes ago, terafil said:

Hi SimonF, no, they don't

Can you post diagnostics. 

Yes, sure

microserver-diagnostics-20240126-1841.zip

Thank you

34 minutes ago, terafil said:

Yes, sure

microserver-diagnostics-20240126-1841.zip 119.34 kB · 0 downloads

The XML shows ok on my test systems. Disk has a strange path but should be ok.

Can you goto tools->php settings and if available does the view log have any errors you can send?

 

I'm having the same issue currently. Diagnostics are posted below. I've tried all the previous fixes.

lovenest-diagnostics-20240616-2045.zip

14 hours ago, kal-el681 said:

I'm having the same issue currently

A reboot should resolve it, if it doesn't post new diags.

I've rebooted multiple times. The VMs will start and then two of them will pause. These diags posted are after a restart. If I disable VMs they won't re-enable unless I reboot and again some of them will pause and not start properly.  

30 minutes ago, kal-el681 said:

These diags posted are after a restart

The service initially started, but then it was stopped.

I've restarted and taken two additional diagnostics. First from right after restart, second from restart + ~ 2mins when some of the VMs pause themselves. I can do additional diags after stopping and restarting VM service if needed. 

after-restart-lovenest-diagnostics-20240617-1251.zip after-vms-load-and-pause-lovenest-diagnostics-20240617-1253.zip

1 hour ago, kal-el681 said:

some of the VMs pause themselves.

If the VMs are pausing you need to fix this first, after that you won't need to restart the libvirt service

 

AFAIK there are only two reasons for VMs pausing, sleep is enabled in the VM, or they are running out of space, assuming it's not the former, where are the vdisks for the affected VMs being stored?

Here's a couple screenshots that should show what you need:

14 hours ago, kal-el681 said:

Here's a couple screenshots that should show what you need:

 

According to the diags, domains share exists on disks 1, 2 and 3, and disk1 is completely full:
 

Filesystem      Size  Used Avail Use% Mounted on
/dev/md1p1      5.5T  5.5T   16K 100% /mnt/disk1

 

So any vdisks stored there will have issues.

I've figured it out. It seems that my vdisk1.img files were corrupt. I rebuilt the VM and it worked without issue. I did also notice through all of this that I had to manually assign the port for VNC on them to avoid them all trying to use the same one and crashing. 

Hello, I'm getting the same "Libvirt Service failed to start." message. This seemed as good as place as any to post this. If I'm wrong, please correct me. I deleted the libvert.img file, rebooted the server and I get this message. I rebooted because VMs were not working and I disabled/enabled the service but that did nothing. LIbvert storage location points to the .img file and the VM and ISO paths are legitimate. So I'm not sure what I'm missing. I've attached the diagnostics -- thank you for your help.

tower-diagnostics-20241230-2017.zip

Did you delete it by checking this checkbox "Delete Image File" and hitting done? Because that is how I do it. On next disable/enable VM, file gets recreated again.

 

By the way, I am still getting that. I run multiple unraid servers, and I am getting that on more of them. Basically when I disable VM service because I need to change something in settings, or when I reboot server for whatever reason, there is 50/50 chance that VMs won't work. Not sure what it really is related to, when I check libvirt logs, there are messages related to USB devices, how they could not be attached or something. But since I wasn't able to figure it out, I stopped bothering much. I just back up VM XML, and on next libvirt file creation, I just recreate VMs.

Yes that is how I delete the file. I did that, disabled/enabled VM, and that's when I get this error. I also have lots of issues getting USB devices to work with the one W10 VM I have but I can't get the VM to start at the moment.

1 hour ago, gnickdog said:

Yes that is how I delete the file. I did that, disabled/enabled VM, and that's when I get this error. I also have lots of issues getting USB devices to work with the one W10 VM I have but I can't get the VM to start at the moment.

Image is in-use, reboot Unraid and post new diags if it still doesn't start.

Hi all - I havent rebooted my server in many months (~7-8 months uptime) and have been using my Windows 11 VM like normal since then. I think I ran a quick update on Windows 11 last night to whatever the latest update was (i remember it being called something along the lines of 24H2 or so), and then my VM started getting a bit wonky, crashing and requiring me to force stop the VM and restart. I thought it may originally be because of this certain action i was trying to do (recover an old chrome session with ~800 open tabs), but my VM just crashed again with not much going on (just excel, ~30 or so tabs, itunes running).

 

the VM instability has caused the webUI to be unstable, i.e. it would take 30-60 seconds just for the dashboard to show my VM section and container section. Eventually it got so unstable that unraid was not even loading any containers or VM on dashboard (though containers were still working), so i proceeded to restart Unraid via webUI which caused entire system to hang (i.e. Plex was working but every container / accessing remotely via wireguard stopped working) requiring a friend to go over to my server sitting in another state to manually turn server off and on again.

 

I just recently went to settings -> VM Manager to turn off the VM and then turn it back on and now my VM tab in unraid says "Libvirt Service failed to start." When i click libvirt log, it looks like below:

 

 

What do i need to do to fix my VM instability issue? Should i proceed with upgrading to 7.0.0 to fix this, or do i need to rebuild my libvirt.img file? If so, does anyone have a precise step by step so i don't destroy anything more by clicking delete image file and doing irreparable harm to my poor VMs (i'm bit of a noob so handholding is advised, last time i clicked around i accidentally applied docker safe new perms to my appdata folder and screwed up almost all my containers...).

Edited January 24, 20251 yr by Linguafoeda

Try rebooting, post new diags if it still doesn't start. 

10 hours ago, JorgeB said:

Try rebooting, post new diags if it still doesn't start. 

 

I tried to restart and the server hung. i had to manually turn off and on again. that doesn't seem like a good sign that it happened twice in a row.

 

My VM is back to working (like when i restarted 2 days ago), but i guess i will monitor it. Is there a way for me to generate logs to maybe troubleshoot this instability happening?

 

Edit: i just tried to start a VM and it's not loading with the right click VM Console (VNC) or try to connect via RDP.

Edited January 24, 20251 yr by Linguafoeda

I just went into settings, stopped VM then tried to turn it on again and now am back to square 1 of the error message "Libvirt Service failed to start."

 

 

this person above is also seemingly having same issue and claiming he has to do a fresh install of unraid to fix it (has tried to recreate his libvirt image 3 times and failed). I'd really like to avoid a fresh unraid install if possible. I haven't done anything to touch my libvirt file - i'm assuming that will be the next step? and figure out why my server is not properly restarting requiring a physical power off and power on for me to restart the server.

When I faced libvirt issues, I could not start VM services at all. For me, it worked by deleting the libvirt.img (on settings - VM tab, once you stop VM service, there should be button to delete libvirt). It will be recreated upon VM service start.

You can backup VM XML, since after libvirt deletition, VMs will be gone. But this is just VM definition, virtual disks are still there, you just need to create VM again, assign old disk, RAM, etc.