Internal Error: QEMU unexpectedly closed monitor.

[androo303]

Trying to reboot my VM and I continually get this error.

 

 

I've pasted the log file for it on PasteBin https://pastebin.com/xiRfvNP2 . I've also included the libvert log output as well just below (didn't go to PasteBin since it is smaller in size).

 

2023-05-20 17:57:28.744+0000: 19056: info : libvirt version: 8.7.0
2023-05-20 17:57:28.744+0000: 19056: info : hostname: Tower
2023-05-20 17:57:28.744+0000: 19056: error : qemuMonitorIORead:423 : Unable to read from monitor: Connection reset by peer
2023-05-20 17:57:28.744+0000: 19056: error : qemuProcessReportLogError:1963 : internal error: qemu unexpectedly closed the monitor

 

I attempted to up my ram to 30G but I think this is what started breaking it. I cannot remember what I had it set to prior to these crashes.

 

Are there any other logs that I can share to help troubleshoot? 

Edited May 20, 2023 by androo303

[Squid]

1 hour ago, androo303 said:

I attempted to up my ram to 30G but I think this is what started breaking it. I cannot remember what I had it set to prior to these crashes.

 

Do you remember doing any manual XML edits when you set up the VM in the first place?  Changing the memory via the template would have resulted in the manual edits being lost.

[androo303]

I didn't manually touch the XML, but I did edit the MAX RAM by adding an extra 2G. I was able to find out what I had it at before, so its now stable again.

 

Any tips on how to virtually "add" more ram to my VM?

[SimonF]

7 hours ago, androo303 said:

I didn't manually touch the XML, but I did edit the MAX RAM by adding an extra 2G. I was able to find out what I had it at before, so its now stable again.

 

Any tips on how to virtually "add" more ram to my VM?

What is the total system memory and current utilisation, i.e. do you have extra capacity? Any error messages in the syslog at the time you started the VM with increased memory.