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

[Heiko Z. <he...@zu...>]

  Should we add support for vdX devices ?

Heiko

Quoting Udo Lembke <udo...@al...>:

> 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
>
>   On 19.12.2015 22:35, Udo Lembke wrote:
>
>> Hi Heiko,
>> just start another test (with Devil-Linux 1.8.0-2015-12-13-i686 and
>> openvpn 2.3.8) and with enabled syslog-ng.
>>
>> Will see what happens.
>>
>> Udo
>>
>>    On 19.12.2015 15:59, Heiko Zuerker wrote:
>>
>>> Udo,
>>>
>>> The next version will have the latest openvpn 2.3.9 and also the
>>> latest kernel.
>>> Hopefully that will help with the issue your experienced.
>>>
>>> Heiko
>>>  
>>
>>
>>
------------------------------------------------------------------------------
>>
>> _______________________________________________ Devil-linux-discuss
>> mailing list
>>
Dev...@li...://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
--

Regards
  Heiko Zuerker