search for: qemumonitorio

Hi, I am trying to get some VMs running under qemu-kvm. At some point the VM starts, but then they shutdown by themselves and I see those messages in the log: 2013-10-11 18:28:57.165+0000: 4148: error : qemuMonitorIO:615 : internal error: End of file from monitor 2013-10-11 18:28:57.165+0000: 4148: debug : qemuMonitorIO:648 : Error on monitor internal error: End of file from monitor Any ideas what could cause this behavior? I am running Ubuntu 13.10 x86_64 with libvirt 1.1.1 and qemu-kvm 1.5.0. -- Francoi...

On 11.10.2013 20:37, Francois Gaudreault wrote: > Hi, > > I am trying to get some VMs running under qemu-kvm. At some point the > VM starts, but then they shutdown by themselves and I see those messages > in the log: > > 2013-10-11 18:28:57.165+0000: 4148: error : qemuMonitorIO:615 : internal > error: End of file from monitor > 2013-10-11 18:28:57.165+0000: 4148: debug : qemuMonitorIO:648 : Error on > monitor internal error: End of file from monitor > > Any ideas what could cause this behavior? > > I am running Ubuntu 13.10 x86_64 with libvirt 1.1.1...

...0:37, Francois Gaudreault wrote: >> Hi, >> >> I am trying to get some VMs running under qemu-kvm. At some point the >> VM starts, but then they shutdown by themselves and I see those messages >> in the log: >> >> 2013-10-11 18:28:57.165+0000: 4148: error : qemuMonitorIO:615 : internal >> error: End of file from monitor >> 2013-10-11 18:28:57.165+0000: 4148: debug : qemuMonitorIO:648 : Error on >> monitor internal error: End of file from monitor >> >> Any ideas what could cause this behavior? >> >> I am running Ubuntu 13.10...

On 14.10.2013 17:38, Francois Gaudreault wrote: > Hi Michal, > > Looking in the logs, it looks like the libvirt process sent a sigkill to > the qemu process: > 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerAcquire:358 : > lock=0x7f6bc80de170 state='(null)' flags=3 action=0 fd=0x7f6bdf3bf074 > 2013-10-11 19:59:22.132+0000: 10212: debug :

...gather anything interresting. Hi, it happened again. Following the log of my script it started on 8th of june at 5:59:09 (UTC+2) to blockcommit the domain. These are the related lines in libvirtd.log: =================================================== 2019-06-07 20:30:57.170+0000: 30299: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor 2019-06-08 03:59:17.690+0000: 30299: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor 2019-06-08 03:59:26.145+0000: 30300: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-08 03:59:26.191+0000:...

...: 1355: error : virSysinfoRead:465 : internal error Failed to find path for dmidecode binary 2011-09-21 15:05:43.873: 1349: warning : qemuDomainObjTaint:1128 : Domain id=1 name='IIS' uuid=a02e41a9-9f4d-d94f-43a6-995b1ca6d37d is tainted: high-privileges 2011-09-21 16:07:10.593: 1344: error : qemuMonitorIO:541 : internal error End of file from monitor Any help would be much appreciated. -- Sincerely, falazemi

...-------------------------------------------- vdb /mnt/snap/severin.sn ... ============================================================== The libvirtd-log says (it's UTC IIRC): ============================================================= ... 2019-05-31 20:31:34.481+0000: 4170: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor 2019-06-01 01:05:32.233+0000: 4170: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor 2019-06-01 01:05:43.804+0000: 22605: warning : qemuGetProcessInfo:1461 : cannot parse process status data 2019-06-01 01:05:43.848+0000: 2...

...ne with Openstack. We are using in libvirtd.conf log_level=1 and log_outputs="1:file:/var/log/libvirt/libvirtd.log" we can see that in /var/log/libvirt/libvirtd.log appear the following error message and the VM is finally shutdown : 2014-06-11 14:47:26.166+0000: 12971: error : qemuMonitorIO:614 : internal error End of file from monitor ( file attached below) ( VM shutdown seen here) The host has enough resources( we see no complains) and the XML of the VM is : The libvirt version is: 0.10.2 The qemu-kvm version: 0.12.1.2 >From the internet we could not figure ou...

Hi Martin Here is some more info in the libvirt/qemu/instance...log file . Does it help in resolving the issue of : error : qemuMonitorIO:614 : internal>error End of file from monitor In the libvirtd.log file I sent you could see clearly that the debug option is active and this is the most detailed info available (or some better option than log_leve=1 exists ?) Thx Zvi Dubitzky Email:dubi@il.ibm.com From: Marti...

I am unable to mount a vdi image with virt-df. I get this error in the libvirt log. 2012-06-24 02:37:22.484+0000: 2364: error : qemuMonitorIO:583 : internal error End of file from monitor I don't really know from this output what the problem is and some assistance would be appreciated. I'm attaching the output of the libguest test program. Brian ____________________________________________________________ GET FREE SMILEYS FOR...

Hi Peter, thanks for your help. ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: >> ============================================================= >> ... >> 2019-05-31 20:31:34.481+0000: 4170: error : qemuMonitorIO:719 : internal error: >> End of file from qemu monitor >> 2019-06-01 01:05:32.233+0000: 4170: error : qemuMonitorIO:719 : internal error: >> End of file from qemu monitor > > This message is printed if qemu crashes for some reason and then closes > the monitor socket une...

.... > These are the related lines in libvirtd.log: > =================================================== Thanks for comming back to me with the information. Unfortunately this is not a full debug log but I can try to tell you what I see here: > 2019-06-07 20:30:57.170+0000: 30299: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor > 2019-06-08 03:59:17.690+0000: 30299: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor So this looks like qemu crashed. Or at least it's the usual symptom we get. Is there anything in /var/log/libvirt/qemu/$VMNAME...

...---- > vdb /mnt/snap/severin.sn > ... > ============================================================== > > The libvirtd-log says (it's UTC IIRC): > ============================================================= > ... > 2019-05-31 20:31:34.481+0000: 4170: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor > 2019-06-01 01:05:32.233+0000: 4170: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor This message is printed if qemu crashes for some reason and then closes the monitor socket unexpectedly. > 2019-06-01 01:05:43....

...tering monitor without asking for a nested job is dangerous 2018-05-22 11:45:39.091+0000: 32314: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous 2018-05-22 11:45:41.841+0000: 32310: error : qemuMonitorIO:615 : internal error End of file from monitor the qmeu-kvminstance-00001959.log: 2018-05-22 11:45:38.603+0000: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/home/ning.zhao USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name instance-00001959 -S -M rhel6.6.0 -...

...y a probably rather unusual device), the VM dies with the following error in the libvirtd.log: 2012-07-20 21:04:19.591+0000: 1282: error : virConnectNumOfInterfaces:9803 : this function is not supported by the connection driver: virConnectNumOfInterfaces 2012-07-20 21:05:05.762+0000: 1276: error : qemuMonitorIO:603 : internal error End of file from monitor This happens no matter if is it the only configured USB device or if there is another USB device present in the config or not. I configured it doing the following steps: - I looked up the vendor / product ID using lsub Bus 001 Device 003: ID 180f:...

...on https://wiki.libvirt.org/page/DebugLogs . Isn't that correct ? That should create informative logfiles. The other host has excat the same configuration but produce much bigger logfiles !?! I have libvirt-daemon-4.0.0-8.12.1.x86_64. > >> 2019-06-07 20:30:57.170+0000: 30299: error : qemuMonitorIO:719 : internal error: >> End of file from qemu monitor >> 2019-06-08 03:59:17.690+0000: 30299: error : qemuMonitorIO:719 : internal error: >> End of file from qemu monitor > > So this looks like qemu crashed. Or at least it's the usual symptom we > get. Is there anyt...

...qemuMonitorJSONIOProcessEvent:235 : type: STOP, vm: d470c3b284425b9bacb34d3b5f3845fe, cost 1.203 secs 2019-07-25 14:23:59.601+0000: 15818: warning : qemuMonitorJSONIOProcessEvent:235 : type: SHUTDOWN, vm: d470c3b284425b9bacb34d3b5f3845fe, cost 1.203 secs 2019-07-25 14:23:59.629+0000: 15818: error : qemuMonitorIORead:597 : Unable to read from monitor: Connection reset by peer 2019-07-25 14:23:59.629+0000: 121081: warning : qemuProcessEventHandler:4840 : vm: d470c3b284425b9bacb34d3b5f3845fe, event: 6 locked 2019-07-25 14:23:59.629+0000: 15822: error : qemuMonitorJSONCommandWithFd:364 : internal error: Missin...

...ut asking for a nested job is dangerous > 2018-05-22 11:45:39.091+0000: 32314: warning : > qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async > job owner; entering monitor without asking for a nested job is dangerous > 2018-05-22 11:45:41.841+0000: 32310: error : qemuMonitorIO:615 : internal > error End of file from monitor > This says that qemu died. You can try to look into domain log to see why. Michal

...not exist 18:27:31.022: 3046: error : virNetworkObjIsDuplicate:1742 : operation failed: network 'bobnet' already exists with uuid 85e167f9-4670-4f7c-68c7-caf2daeecc93 18:31:57.184: 3048: error : ifaceGetIndex:334 : internal error interface vnet0 does not exist 19:15:24.599: 3043: error : qemuMonitorIO:583 : internal error End of file from monitor 00:54:12.418: 7632: warning : qemuDomainObjStart:4649 : Ignoring incomplete managed state /var/lib/libvirt/qemu/save/mywebsite.save 11:51:27.639: 2157: error : qemuDomainSaveImageOpen:3914 : operation failed: failed to read qemu header 2014-03-24 19:...

...log/libvirt/libvirtd.log appear the following >error message and the VM is finally shutdown : > Do you have some filters applied? If not, the file should have more messages. Actually, it should get so big it is unsuitable for the list :) >2014-06-11 14:47:26.166+0000: 12971: error : qemuMonitorIO:614 : internal >error End of file from monitor This means qemu died before we even connected to the monitor socket. And as can be seen from the instance log there is no output from qemu as to why it died. If you properly turn on debug logs (and restart libvirtd) you should be able to see at le...