2:37 a.m.
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.
--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudreault(a)cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC H3J 1S6
www.cloudops.com
@CloudOps_
1:40 p.m.
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 and qemu-kvm 1.5.0.
See /var/log/libvirt/qemu/$dom.log. There should be an error message
reported by qemu what went wrong.
Michal
11:38 p.m.
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 : virLockManagerFree:395 :
lock=0x7f6bc80de170
2013-10-11 19:59:22.132+0000: 10212: debug : virObjectUnref:256 :
OBJECT_UNREF: obj=0x7f6bd000f890
2013-10-11 19:59:22.132+0000: 10212: debug : qemuProcessHook:2573 : Hook
complete ret=0
2013-10-11 19:59:22.132+0000: 10212: debug : virExec:632 : Done hook 0
2013-10-11 19:59:22.132+0000: 10212: debug : virExec:669 : Setting child
uid:gid to 108:115 with caps 0
2013-10-11 19:59:22.132+0000: 10212: debug :
virCommandHandshakeChild:360 : Notifying parent for handshake start on 37
2013-10-11 19:59:22.132+0000: 10212: debug :
virCommandHandshakeChild:368 : Waiting on parent for handshake complete
on 38
2013-10-11 19:59:22.137+0000: 10212: debug : virFileClose:90 : Closed fd 37
2013-10-11 19:59:22.137+0000: 10212: debug : virFileClose:90 : Closed fd 38
2013-10-11 19:59:22.137+0000: 10212: debug :
virCommandHandshakeChild:388 : Handshake with parent is done
W: kvm binary is deprecated, please use qemu-system-x86_64 instead
char device redirected to /dev/pts/3 (label charserial0)
qemu: terminating on signal 15 from pid 1437
2013-10-11 20:00:26.427+0000: shutting down
ps output:
1437 ? Sl 0:15 /usr/sbin/libvirtd -d -l
Any way to troubleshoot deeper?
Thanks!
Francois
On 10/14/2013, 1:40 AM, Michal Privoznik wrote:
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 and qemu-kvm 1.5.0.
>
See /var/log/libvirt/qemu/$dom.log. There should be an error message
reported by qemu what went wrong.
Michal
--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudreault(a)cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC H3J 1S6
www.cloudops.com
@CloudOps_
3:19 p.m.
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 : virLockManagerFree:395 :
lock=0x7f6bc80de170
2013-10-11 19:59:22.132+0000: 10212: debug : virObjectUnref:256 :
OBJECT_UNREF: obj=0x7f6bd000f890
2013-10-11 19:59:22.132+0000: 10212: debug : qemuProcessHook:2573 : Hook
complete ret=0
2013-10-11 19:59:22.132+0000: 10212: debug : virExec:632 : Done hook 0
2013-10-11 19:59:22.132+0000: 10212: debug : virExec:669 : Setting child
uid:gid to 108:115 with caps 0
2013-10-11 19:59:22.132+0000: 10212: debug :
virCommandHandshakeChild:360 : Notifying parent for handshake start on 37
2013-10-11 19:59:22.132+0000: 10212: debug :
virCommandHandshakeChild:368 : Waiting on parent for handshake complete
on 38
2013-10-11 19:59:22.137+0000: 10212: debug : virFileClose:90 : Closed fd 37
2013-10-11 19:59:22.137+0000: 10212: debug : virFileClose:90 : Closed fd 38
2013-10-11 19:59:22.137+0000: 10212: debug :
virCommandHandshakeChild:388 : Handshake with parent is done
W: kvm binary is deprecated, please use qemu-system-x86_64 instead
char device redirected to /dev/pts/3 (label charserial0)
qemu: terminating on signal 15 from pid 1437
2013-10-11 20:00:26.427+0000: shutting down
ps output:
1437 ? Sl 0:15 /usr/sbin/libvirtd -d -l
Any way to troubleshoot deeper?
Well, what says the libvirtd.log then?
http://wiki.libvirt.org/page/DebugLogs
Michal
10:39 p.m.
Michal,
I do see a SHUTDOWN event in the log, but it's not clear from where that
comes from. If you issue a reboot command on a VM would it show like a
SHUTDOWN event in the logs? Anyway, I pasted the log here for review:
http://pastebin.com/raw.php?i=Xf2GHvN3
The shudown appears at 20:00:26.
Many thanks!
Francois
On 10/15/2013, 3:19 AM, Michal Privoznik wrote:
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 : virLockManagerFree:395 :
> lock=0x7f6bc80de170
> 2013-10-11 19:59:22.132+0000: 10212: debug : virObjectUnref:256 :
> OBJECT_UNREF: obj=0x7f6bd000f890
> 2013-10-11 19:59:22.132+0000: 10212: debug : qemuProcessHook:2573 : Hook
> complete ret=0
> 2013-10-11 19:59:22.132+0000: 10212: debug : virExec:632 : Done hook 0
> 2013-10-11 19:59:22.132+0000: 10212: debug : virExec:669 : Setting child
> uid:gid to 108:115 with caps 0
> 2013-10-11 19:59:22.132+0000: 10212: debug :
> virCommandHandshakeChild:360 : Notifying parent for handshake start on 37
> 2013-10-11 19:59:22.132+0000: 10212: debug :
> virCommandHandshakeChild:368 : Waiting on parent for handshake complete
> on 38
> 2013-10-11 19:59:22.137+0000: 10212: debug : virFileClose:90 : Closed fd 37
> 2013-10-11 19:59:22.137+0000: 10212: debug : virFileClose:90 : Closed fd 38
> 2013-10-11 19:59:22.137+0000: 10212: debug :
> virCommandHandshakeChild:388 : Handshake with parent is done
> W: kvm binary is deprecated, please use qemu-system-x86_64 instead
> char device redirected to /dev/pts/3 (label charserial0)
> qemu: terminating on signal 15 from pid 1437
> 2013-10-11 20:00:26.427+0000: shutting down
>
> ps output:
> 1437 ? Sl 0:15 /usr/sbin/libvirtd -d -l
>
> Any way to troubleshoot deeper?
>
Well, what says the libvirtd.log then?
http://wiki.libvirt.org/page/DebugLogs
Michal
--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudreault(a)cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC H3J 1S6
www.cloudops.com
@CloudOps_
3980
days inactive
3984
days old
4 comments
2 participants
participants (2)
-
Francois Gaudreault -
Michal Privoznik