Bug 1279320
Summary: | ibm s390x kvm VM gets stuck in a crash loop | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | kevinzs |
Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | berrange, crobinso, gscrivan, kevinzs, rbalakri |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-11 15:03:01 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
kevinzs
2015-11-09 07:42:39 UTC
My guess is that something is causing qemu to repeatedly reset. Can you provide /var/log/libvirt/qemu/$vmname.log from the libvirtd server? Hi Cole, Here is the log information : /var/log/libvirt/qemu/generic.log, and virt-manager shows that the generic has the states "crashed" 2015-11-11 02:37:08.963+0000: starting up libvirt version: 1.2.20, package: 1.el7_1.kvmibm1_1_1.2 (Koji, 2015-11-02-15:14:28, lnx2), qemu version: 2.4.0 LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -name generic -S -machine s390-ccw-kvmibm-1.1.1,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 47653a1e-6726-4ef7-83ab-28acd68800b4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-generic/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -boot strict=on -device virtio-scsi-ccw,id=scsi0,devno=fe.0.0002 -drive file=/var/lib/libvirt/images/generic.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-ccw,scsi=off,devno=fe.0.0000,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/var/lib/libvirt/images/RHEL-7.0-20140507.0-Server-s390x-dvd1.iso,if=none,id=drive-scsi0-0-0-0,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:71:77:4d,devno=fe.0.0001 -chardev pty,id=charconsole0 -device sclpconsole,chardev=charconsole0,id=console0 -device virtio-balloon-ccw,id=balloon0,devno=fe.0.0003 -msg timestamp=on char device redirected to /dev/pts/1 (label charconsole0) qemu: terminating on signal 15 from pid 1382 2015-11-11 02:37:09.399+0000: shutting down 2015-11-11 02:37:11.368+0000: starting up libvirt version: 1.2.20, package: 1.el7_1.kvmibm1_1_1.2 (Koji, 2015-11-02-15:14:28, lnx2), qemu version: 2.4.0 LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -name generic -S -machine s390-ccw-kvmibm-1.1.1,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 47653a1e-6726-4ef7-83ab-28acd68800b4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-generic/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device virtio-scsi-ccw,id=scsi0,devno=fe.0.0002 -drive file=/var/lib/libvirt/images/generic.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-ccw,scsi=off,devno=fe.0.0000,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-scsi0-0-0-0,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:71:77:4d,devno=fe.0.0001 -chardev pty,id=charconsole0 -device sclpconsole,chardev=charconsole0,id=console0 -device virtio-balloon-ccw,id=balloon0,devno=fe.0.0003 -msg timestamp=on char device redirected to /dev/pts/1 (label charconsole0) (In reply to Cole Robinson from comment #1) > My guess is that something is causing qemu to repeatedly reset. Can you > provide /var/log/libvirt/qemu/$vmname.log from the libvirtd server? Hi Cole, Thanks for your help~ Here is the log information : /var/log/libvirt/qemu/generic.log, and virt-manager shows that the generic has the states "crashed" 2015-11-11 02:37:08.963+0000: starting up libvirt version: 1.2.20, package: 1.el7_1.kvmibm1_1_1.2 (Koji, 2015-11-02-15:14:28, lnx2), qemu version: 2.4.0 LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -name generic -S -machine s390-ccw-kvmibm-1.1.1,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 47653a1e-6726-4ef7-83ab-28acd68800b4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-generic/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -boot strict=on -device virtio-scsi-ccw,id=scsi0,devno=fe.0.0002 -drive file=/var/lib/libvirt/images/generic.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-ccw,scsi=off,devno=fe.0.0000,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/var/lib/libvirt/images/RHEL-7.0-20140507.0-Server-s390x-dvd1.iso,if=none,id=drive-scsi0-0-0-0,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:71:77:4d,devno=fe.0.0001 -chardev pty,id=charconsole0 -device sclpconsole,chardev=charconsole0,id=console0 -device virtio-balloon-ccw,id=balloon0,devno=fe.0.0003 -msg timestamp=on char device redirected to /dev/pts/1 (label charconsole0) qemu: terminating on signal 15 from pid 1382 2015-11-11 02:37:09.399+0000: shutting down 2015-11-11 02:37:11.368+0000: starting up libvirt version: 1.2.20, package: 1.el7_1.kvmibm1_1_1.2 (Koji, 2015-11-02-15:14:28, lnx2), qemu version: 2.4.0 LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -name generic -S -machine s390-ccw-kvmibm-1.1.1,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 47653a1e-6726-4ef7-83ab-28acd68800b4 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-generic/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device virtio-scsi-ccw,id=scsi0,devno=fe.0.0002 -drive file=/var/lib/libvirt/images/generic.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-ccw,scsi=off,devno=fe.0.0000,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-scsi0-0-0-0,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:71:77:4d,devno=fe.0.0001 -chardev pty,id=charconsole0 -device sclpconsole,chardev=charconsole0,id=console0 -device virtio-balloon-ccw,id=balloon0,devno=fe.0.0003 -msg timestamp=on char device redirected to /dev/pts/1 (label charconsole0) If the VM is crashing then you need to dig a bit deeper to figure out why. Could be a bug there, or a virt-manager XML issue, or libvirt qemu command line issue, or user error I'd suggest asking the KVM IBM folks, or take that qemu command line and try to manually make it work by hand. Closing as DEFERRED for now but please reopen if you determine virt-manager needs changes (In reply to Cole Robinson from comment #4) > If the VM is crashing then you need to dig a bit deeper to figure out why. > Could be a bug there, or a virt-manager XML issue, or libvirt qemu command > line issue, or user error > > I'd suggest asking the KVM IBM folks, or take that qemu command line and try > to manually make it work by hand. Closing as DEFERRED for now but please > reopen if you determine virt-manager needs changes Hi Cole, Thanks for your advice. I find that , when I don't specify the kernel and initrd , installation process has been skipped , and be treated successful. Then according to the boot xml, virt-manager will try to restart it again and again. Do you think I can debug this by getting the debug information of libvirtd in the server? Also ,I don't know the domain lifecycle event means , is it a event that sent by libvirtd in the server? Sincerely Thanks~ (In reply to Cole Robinson from comment #4) > If the VM is crashing then you need to dig a bit deeper to figure out why. > Could be a bug there, or a virt-manager XML issue, or libvirt qemu command > line issue, or user error > > I'd suggest asking the KVM IBM folks, or take that qemu command line and try > to manually make it work by hand. Closing as DEFERRED for now but please > reopen if you determine virt-manager needs changes Hi Cole, Thanks for your advice. I find that , when I don't specify the kernel and initrd , installation process has been skipped , and be treated successful. Then according to the boot xml, virt-manager will try to restart it again and again. Do you think I can debug this by getting the debug information of libvirtd in the server? Also ,I don't know the domain lifecycle event means , is it a event that sent by libvirtd in the server? Sincerely Thanks~ |