Re: [Devil-Linux-discuss] 1.8 testing release uploaded

[Udo L. <udo...@al...>]

Hi,
a short update.

With virtio as storage it's still running (5 hours.)

One Error mesage appear:
Dec 20 14:13:59 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 14:19:50 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 14:25:42 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 14:31:33 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 14:37:24 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 14:43:15 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 14:49:06 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 14:54:57 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:00:48 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:06:39 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:12:30 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:18:21 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:24:12 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:30:03 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:35:54 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:41:45 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:47:36 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:53:27 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 15:59:19 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 16:05:10 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 16:11:01 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 16:16:52 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 16:22:43 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 16:28:34 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 16:34:25 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 16:40:16 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 16:46:07 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes
Dec 20 16:51:58 vpnxxx init[1]: Id "8" respawning too fast: disabled for
5 minutes


8:2345:respawn:env - TERM=linux /bin/procinfo -f -F /dev/tty8

On Term 8 I see an floating point exception and "gcc can't parse" - see
screenshot.


Udo

On 20.12.2015 11:19, Udo Lembke wrote:
> Hi,
> the VM stoped working after a short time (100% cpu usage). I restart
> the VM to see if anything in the logs.
>
> Looks that the issue has nothing to do with openvpn!
> After a very short time an kernel panic occur - unfortunality I'm not
> fast enough to do an screenshot of the first output - only the
> repeated error messages on the console (see attachment).
>
> The VM run on QEMU version 2.2.1 - on a Proxmox VE 3.4 system.
> VM-config:
> cat /etc/pve/qemu-server/518.conf
> boot: d
> cores: 1
> ide0: e_sas_r1:vm-518-disk-1,cache=writethrough,size=6G
> ide2: local_iso:iso/dl-1.8.0-2015-12-13-i686.iso,media=cdrom,size=599554K
> localtime: 1
> memory: 768
> name: vpnxxx
> net0: virtio=B6:C2:F4:C7:3D:31,bridge=vmbr1,tag=99
> numa: 1
> ostype: l26
> sockets: 1
>
> resulting Command:
> root     30264  6.4  0.1 1231544 155692 ?      Sl   10:45   0:36
> /usr/bin/kvm -id 518 -chardev
> socket,id=qmp,path=/var/run/qemu-server/518.qmp,server,nowait -mon
> chardev=qmp,mode=control -vnc
> unix:/var/run/qemu-server/518.vnc,x509,password -pidfile
> /var/run/qemu-server/518.pid -daemonize -name vpnxxx -smp
> 1,sockets=1,cores=1,maxcpus=1 -nodefaults -boot
> menu=on,strict=on,reboot-timeout=1000 -vga cirrus -cpu
> kvm64,+lahf_lm,+x2apic,+sep -m 768 -object
> memory-backend-ram,size=768M,id=ram-node0 -numa
> node,nodeid=0,cpus=0,memdev=ram-node0 -k de -device
> piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device
> usb-tablet,id=tablet,bus=uhci.0,port=1 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi
> initiator-name=iqn.1993-08.org.debian:01:df4992719fb2 -drive
> file=/mnt/local_iso/template/iso/dl-1.8.0-2015-12-13-i686.iso,if=none,id=drive-ide2,media=cdrom,aio=native
> -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=100
> -drive
> file=/dev/e_sas_r1/vm-518-disk-1,if=none,id=drive-ide0,cache=writethrough,aio=threads,detect-zeroes=on
> -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0 -netdev
> type=tap,id=net0,ifname=tap518i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on
> -device
> virtio-net-pci,mac=B6:C2:F4:C7:3D:31,netdev=net0,bus=pci.0,addr=0x12,id=net0
> -rtc base=localtime
>
> The blk_end_bidi_request in the trace could be from the ide-IO driver.
> I can try to use virtio instead, but unfortunality devil linux don't
> find the config on a virtio-drive (vdX). So I need to split the drives
> in an ide for config and one virtio for dev devil-linunx VG.
>
>
> Udo
>