Re: [libvirt-users] terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)

2017-10-20 14:59 GMT+03:00 Martin Kletzander <mkletzan(a)redhat.com&gt;: > On Thu, Oct 19, 2017 at 09:11:00PM +0300, Matwey V. Kornilov wrote: >> >> Hello, >> >> I use libvirt 3.3.0 and qemu 2.9.0 >> >> My domain XML spec is the following: >> >> <domain type='qemu'> >> <name>s390_generic</name> >> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> >> <memory unit='KiB'>1048576</memory> >> <currentMemory unit='KiB'>1048576</currentMemory> >> <vcpu placement='static'>1</vcpu> >> <os> >> <type arch='s390x' machine='s390-ccw-virtio-2.9'>hvm</type> >> <boot dev='hd'/> >> </os> >> <clock offset='utc'/> >> <on_poweroff>destroy</on_poweroff> >> <on_reboot>restart</on_reboot> >> <on_crash>destroy</on_crash> >> <devices> >> <emulator>/usr/bin/qemu-system-s390x</emulator> >> <disk type='block' device='disk'> >> <driver name='qemu' type='raw' cache='none' io='native'/> >> <source dev='/dev/lvm_pda/libvirt_s390'/> >> <target dev='vda' bus='virtio'/> >> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/> >> </disk> >> <disk type='file' device='cdrom'> >> <driver name='qemu' type='raw'/> >> <target dev='sda' bus='scsi'/> >> <readonly/> >> <address type='drive' controller='0' bus='0' target='0' unit='0'/> >> </disk> >> <controller type='scsi' index='0' model='virtio-scsi'> >> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/> >> </controller> >> <interface type='bridge'> >> <mac address='52:54:00:e8:61:7e'/> >> <source bridge='br0'/> >> <model type='virtio'/> >> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0001'/> >> </interface> >> <console type='pty'> >> <target type='sclp' port='0'/> >> </console> >> <memballoon model='virtio'> >> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0003'/> >> </memballoon> >> <panic model='s390'/> >> </devices> >> </domain> >> >> The issue is that when I try to start it, it starts and shutdowns >> immediately: >> >> virsh # start s390_generic >> Domain s390_generic started >> >> virsh # >> >> In the domain log file I see the following: >> >> 2017-10-19 18:10:21.633+0000: starting up libvirt version: 3.3.0, qemu >> version: 2.9.0(openSUSE Leap 42.3), hostname: oak.local >> LC_ALL=C >> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin >> QEMU_AUDIO_DRV=none /usr/bin/qemu-system-s390x -name >> guest=s390_generic,debug-threads=on -S -object >> >> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-7-s390_generic/master-key.aes >> -machine s390-ccw-virtio-2.9,accel=tcg,usb=off,dump-guest-core=off -m >> 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid >> 82b4d16e-b636-447e-9fda-41d44616bce8 -display none -no-user-config >> -nodefaults -chardev >> >> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-s390_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=/dev/lvm_pda/libvirt_s390,format=raw,if=none,id=drive-virtio-disk0,cache=none,aio=native >> -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 -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=26,id=hostnet0 -device >> >> virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:e8:61:7e,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 >> 2017-10-19T18:10:21.701184Z qemu-system-s390x: -chardev >> pty,id=charconsole0: char device redirected to /dev/pts/5 (label >> charconsole0) >> 2017-10-19T18:10:21.721299Z qemu-system-s390x: terminating on signal 15 >> from pid 2146 (/usr/sbin/libvirtd) >> 2017-10-19 18:10:21.985+0000: shutting down, reason=shutdown >> > > You don't have much logging enabled, so there's not that much info. What's > in > the libvirtd.log? what is the status reason for the domain? I.e. output of > `virsh domstate --reason` ? How could I increase log level? There is nothing in libvirtd.log.