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

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

All,

I uploaded testing releases for 1.8 under:  
ftp://ftp.devil-linux.org/pub/devel/testing
It seems already very stable, but need more help testing.

-- 

Regards
   Heiko Zuerker

On 08.11.2015 21:39, Heiko Zuerker wrote:
> All,
>
> I uploaded testing releases for 1.8 under:  
> ftp://ftp.devil-linux.org/pub/devel/testing
> It seems already very stable, but need more help testing.
>
>
Hi,
do some more tests...
devil-linux-1.8.0-2015-11-08-i686.tar.bz2 is "broken".

1.)
During tests on a proxmox-ve host, there was no network device (I tried e1000 + virtio).
lsmod shows only:
ata_piix
libata
loop

The same on devil-linux-1.8.0-2015-11-08-x86_64-server.tar.bz2 work. (lsmod shows also virtio_net/e1000).

2.)
lvm don't work on devil-linux-1.8.0-2015-11-08-i686.tar.bz2

# vgcreate -s4M devil-linux /dev/hda2
  Physical volume "/dev/hda2" successfully created
  Volume group "devil-linux" successfully created

#lvcreate -n data -L 512M devil-linux
  /dev/mapper/control: open failed: No such device
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper (unknown version) and kernel driver (unknown version).
  striped: Required device-mapper targest(s) not detected in your kernel.

this is not an real wonder, because dm_mod  is also not loaded...

Udo

Hi,
the default syslog-ng conf file has the wrong format:

/usr/sbin/syslog-ng
[2015-12-02T11:15:12.445990] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode
Please update it to use the syslog-ng 3.6 format at your time of convinience, compatibility mode can operate less
efficiently in some cases. To upgrade the configuration, please review the warnings about incompatible changes printed
by syslog-ng, and once completed change the @version header at the top of the configuration file.;
[2015-12-02T11:15:12.459165] WARNING: Starting with syslog-ng 3.6, the system() source performs JSON parsing of messages
starting with the '@cim:' prefix. No additional action is needed;
[2015-12-02T11:15:12.459249] WARNING: Your configuration uses a newly introduced reserved word as identifier, please use
a different name or enclose it in quotes before upgrading; keyword='channel', config-version='3.3', version='3.4',
filename='source confgen system', line='1:1'
Error parsing source, source plugin channel not found in source confgen system at line 1, column 1:
                                           included from /etc/syslog-ng/syslog-ng.conf line 11, column 9

channel
^^^^^^^

Udo

Udo,

Thanks for testing. I believe #1 & #2 are both related to the module  
bug I fixed end of last week.
Unfortunately something else broke now and the nightly build doesn't  
complete. I'll upload a new version once I get a chance to fix this.

Heiko

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

> On 08.11.2015 21:39, Heiko Zuerker wrote:
>> All,
>>
>> I uploaded testing releases for 1.8 under:
>> ftp://ftp.devil-linux.org/pub/devel/testing
>> It seems already very stable, but need more help testing.
>>
>>
> Hi,
> do some more tests...
> devil-linux-1.8.0-2015-11-08-i686.tar.bz2 is "broken".
>
> 1.)
> During tests on a proxmox-ve host, there was no network device (I  
> tried e1000 + virtio).
> lsmod shows only:
> ata_piix
> libata
> loop
>
> The same on devil-linux-1.8.0-2015-11-08-x86_64-server.tar.bz2 work.  
> (lsmod shows also virtio_net/e1000).
>
> 2.)
> lvm don't work on devil-linux-1.8.0-2015-11-08-i686.tar.bz2
>
> # vgcreate -s4M devil-linux /dev/hda2
>   Physical volume "/dev/hda2" successfully created
>   Volume group "devil-linux" successfully created
>
> #lvcreate -n data -L 512M devil-linux
>   /dev/mapper/control: open failed: No such device
>   Failure to communicate with kernel device-mapper driver.
>   Check that device-mapper is available in the kernel.
>   Incompatible libdevmapper (unknown version) and kernel driver  
> (unknown version).
>   striped: Required device-mapper targest(s) not detected in your kernel.
>
> this is not an real wonder, because dm_mod  is also not loaded...
>
>
> Udo
>
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

-- 

Regards
   Heiko Zuerker

All,

I'm currently uploading the latest test build.
It has most reported issues fixed (I believe), with the exception of  
the syslog-ng config and heartbeat (made progress on this, but need a  
bit more time).

As always, your help with testing is very much appreciated.

-- 

Regards
   Heiko Zuerker

Hi,
tested an openvpn gateway with the new devil-linux-1.8.0-2015-11-08-i686.

Work well for app. 10 hour, but then the VM wasn't accessbile and used
100% cpu. - during this 10 hour there wasn't much traffic on the
vpn-tunnel, but the iperf for testing runs without trouble in the beginning.
Switched back to 1.6.8.

Must do further test over weekend (and with the right syslog-ng.conf) so
perhaps I see something in the log?!

Udo

On 04.12.2015 17:59, Heiko Zuerker wrote:
> All,
>
> I'm currently uploading the latest test build.
> It has most reported issues fixed (I believe), with the exception of  
> the syslog-ng config and heartbeat (made progress on this, but need a  
> bit more time).
>
> As always, your help with testing is very much appreciated.
>
>

  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

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

> Hi,
> tested an openvpn gateway with the new devil-linux-1.8.0-2015-11-08-i686.
>
> Work well for app. 10 hour, but then the VM wasn't accessbile and used
> 100% cpu. - during this 10 hour there wasn't much traffic on the
> vpn-tunnel, but the iperf for testing runs without trouble in the
> beginning.
> Switched back to 1.6.8.
>
> Must do further test over weekend (and with the right syslog-ng.conf) so
> perhaps I see something in the log?!
>
> Udo
>
> On 04.12.2015 17:59, Heiko Zuerker wrote:
>> All,
>>
>> I'm currently uploading the latest test build.
>> It has most reported issues fixed (I believe), with the exception of
>> the syslog-ng config and heartbeat (made progress on this, but need a
>> bit more time).
>>
>> As always, your help with testing is very much appreciated.
>>  
>
>
------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple
> OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> Devil-linux-discuss mailing list
>
Dev...@li...://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
--

Regards
  Heiko Zuerker

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
>

  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

Hello Heiko,
Downloaded your latest build (1.8.0-2015-12-04-x86_64) and in process of testing on a lab system.  Here are results of my tests so far.

1) Unable to load nf_conntrack_amanda and nf_nat_amanda:
I don’t use all of the various modules for conntrack but found that nf_conntrack_amanda and nf_nat_amanda has following error when trying to insert those modules:

modprobe: ERROR: could not insert ‘nf_conntrack_amanda’: Unknown symbol in module, or unknown parameter (see dmesg)
modprobe: ERROR: could not insert ‘nf_nat_amanda’: Unknown symbol in module, or unknown parameter (see dmesg)

Unfortunately dmesg does not include any message related to nf_conntrack_amanda.

I don’t need the amanda modules (my firewall script currently loads all *nat* and *conntrack* modules).  If I omit amanda modules, the remaining conntrack and nat modules appear to load fine.

2) Modules iptable_filter and ip6table_filter are no longer loaded automatically.  These modules were loaded automatically in devil-linux 1.6.5 (guessing occurred when I loaded other modules).  In 1.8, the modules weren’t loaded so I modified my machine to load prior to applying netfilter rules.  Not entirely sure of what changed between 1.6.5 and 1.8 to no longer auto load these modules.   Likely just some education needed on my part, but thought I’d point out in case I missed something.

3) Shorewall6
Would it be possible to include shorewall6?  Been thinking of converting my firewall rule management to shorewall but need shorewal6 for IPv6.

Appreciate all your efforts in creating/managing devil-linux as I have found it to be a very convenient option for deploying my firewall.

 - Rick Frey

> On Dec 4, 2015, at 10:59 AM, Heiko Zuerker <he...@zu...> wrote:
> 
> All,
> 
> I'm currently uploading the latest test build.
> It has most reported issues fixed (I believe), with the exception of  
> the syslog-ng config and heartbeat (made progress on this, but need a  
> bit more time).
> 
> As always, your help with testing is very much appreciated.
> 
> 
> -- 
> 
> Regards
>   Heiko Zuerker

Rick,

Thanks again for testing. All the module loading issues have been  
fixed and should work in the next release.
I added shorewall6 to the todo list, but no idea when I'll get around  
to do it. As always, patches are welcome.

Heiko

Quoting Rick Frey <gr...@gm...>:

> Hello Heiko,
> Downloaded your latest build (1.8.0-2015-12-04-x86_64) and in  
> process of testing on a lab system.  Here are results of my tests so  
> far.
>
> 1) Unable to load nf_conntrack_amanda and nf_nat_amanda:
> I don’t use all of the various modules for conntrack but found that  
> nf_conntrack_amanda and nf_nat_amanda has following error when  
> trying to insert those modules:
>
> modprobe: ERROR: could not insert ‘nf_conntrack_amanda’: Unknown  
> symbol in module, or unknown parameter (see dmesg)
> modprobe: ERROR: could not insert ‘nf_nat_amanda’: Unknown symbol in  
> module, or unknown parameter (see dmesg)
>
> Unfortunately dmesg does not include any message related to  
> nf_conntrack_amanda.
>
> I don’t need the amanda modules (my firewall script currently loads  
> all *nat* and *conntrack* modules).  If I omit amanda modules, the  
> remaining conntrack and nat modules appear to load fine.
>
>
> 2) Modules iptable_filter and ip6table_filter are no longer loaded  
> automatically.  These modules were loaded automatically in  
> devil-linux 1.6.5 (guessing occurred when I loaded other modules).   
> In 1.8, the modules weren’t loaded so I modified my machine to load  
> prior to applying netfilter rules.  Not entirely sure of what  
> changed between 1.6.5 and 1.8 to no longer auto load these modules.   
>  Likely just some education needed on my part, but thought I’d point  
> out in case I missed something.
>
> 3) Shorewall6
> Would it be possible to include shorewall6?  Been thinking of  
> converting my firewall rule management to shorewall but need  
> shorewal6 for IPv6.
>
> Appreciate all your efforts in creating/managing devil-linux as I  
> have found it to be a very convenient option for deploying my  
> firewall.
>
>  - Rick Frey
>
>
>
>> On Dec 4, 2015, at 10:59 AM, Heiko Zuerker <he...@zu...> wrote:
>>
>> All,
>>
>> I'm currently uploading the latest test build.
>> It has most reported issues fixed (I believe), with the exception of
>> the syslog-ng config and heartbeat (made progress on this, but need a
>> bit more time).
>>
>> As always, your help with testing is very much appreciated.
>>
>>
>> --
>>
>> Regards
>>   Heiko Zuerker
>
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

-- 

Regards
   Heiko Zuerker

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...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

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
>

  Udo,

Thanks for testing. Let's just wait until I get the latest build uploaded,
which also includes the latest kernel.
I'm struggling with some dependencies I missed. Once it's all working
again, I'll upload a new version.

--

Regards
  Heiko Zuerker

Hi Heiko,
support for config virtio-device would be very nice for me. The most of my devil linux system are virtualisized.

Udo

On 20.12.2015 22:15, Heiko Zuerker wrote:
>
> Should we add support for vdX devices ?
>
> Heiko
>

  Udo,

I'm just working on the booting logic and it seems /dev/vd?? devices are
supported already.
What exactly doesn't work?

Heiko

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

> Hi Heiko,
> support for config virtio-device would be very nice for me. The most of
> my devil linux system are virtualisized.
>
> Udo
>
> On 20.12.2015 22:15, Heiko Zuerker wrote:
>
>> Should we add support for vdX devices ?
>>
>> Heiko
--

Regards
  Heiko Zuerker

Hi Heiko,
VG devil-linux on /dev/vdX works fine, but the config an a vda1
partition (ext2) are not reconised.
The config-partition must be on a ide-device (hdX).

Udo

On 26.12.2015 16:14, Heiko Zuerker wrote:
>
> Udo,
>
> I'm just working on the booting logic and it seems /dev/vd?? devices
> are supported already.
> What exactly doesn't work?
>
> Heiko
>

  Udo,

That's weird. The code to handle all /dev/vd* devices is there. It might
have something to do with the correct modules not being loaded.
Which modules are required for the partitions to show up?

Right now we have this code:

# virtio
if grep QEMU /proc/cpuinfo > /dev/null ; then
  modprobe virtio_pci
  modprobe virtio_blk
fi
  Heiko

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

> Hi Heiko,
> VG devil-linux on /dev/vdX works fine, but the config an a vda1
> partition (ext2) are not reconised.
> The config-partition must be on a ide-device (hdX).
>
> Udo
>
>   On 26.12.2015 16:14, Heiko Zuerker wrote:
>
>> Udo,
>>
>> I'm just working on the booting logic and it seems /dev/vd?? devices
>> are supported already.
>> What exactly doesn't work?
>>
>> Heiko
>>  
--

Regards
  Heiko Zuerker

Hi Heiko,
just testet devil-linux-1.8.0-2015-12-29-i686 with config on vda1 -
onscreen message:

Creating devices in /dev
Assembking Software RAID
mdadm: No arrays found in config file or automatically
Searching for configuration media
Search list:    /dev/hdc
Checking for "etc-mods.tar.bz2" on "/dev/hdc" ... file not found
Examination of /dev/hdc
Would you really like to load DL without Configuration Media?
 (y/n)

You see, the "Search list" contains the virtual cdrom only.

I connect two hdds to the DL-VM, one ide with the config and an virtio
one. Put in S01boot an "ls /dev" and "lsmod" and I see no vda-device,
wich don't suprise, because lsmod shows only:
ata_piix
libata
loop

Thats all! - so virtio_blk must be loaded after the config file is readed!

Udo

On 26.12.2015 16:14, Heiko Zuerker wrote:
>
> Udo,
>
> I'm just working on the booting logic and it seems /dev/vd?? devices
> are supported already.
> What exactly doesn't work?
>
> Heiko
>
> Quoting Udo Lembke <udo...@al...
> <mailto:udo...@al...>>:
>
>> Hi Heiko,
>> support for config virtio-device would be very nice for me. The most
>> of my devil linux system are virtualisized.
>>
>>
>> Udo
>>
>> On 20.12.2015 22:15, Heiko Zuerker wrote:
>>>
>>> Should we add support for vdX devices ?
>>>
>>> Heiko
>>>
>
>
>
> --
>
> Regards
>   Heiko Zuerker
>  
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

  Udo,

I just downloaded QEMU and tested this and I see a different behavior. But
I'm also new, so I'm not sure if I'm doing this right.
I don't see a vd0 device at all, the harddisk I configured showed up as
hda.
What's the command line you use to start it?

I also added a message now that tells if it detects QEMU and loads the
modules.
It correctly loaded them on during my test.

Which version of QEMU are you using? I downloaded 2.5.

Heiko

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

> Hi Heiko,
> just testet devil-linux-1.8.0-2015-12-29-i686 with config on vda1 -
> onscreen message:
>
> Creating devices in /dev
> Assembking Software RAID
> mdadm: No arrays found in config file or automatically
> Searching for configuration media
> Search list:    /dev/hdc
> Checking for "etc-mods.tar.bz2" on "/dev/hdc" ... file not found
> Examination of /dev/hdc
> Would you really like to load DL without Configuration Media?
>  (y/n)
>
> You see, the "Search list" contains the virtual cdrom only.
>
> I connect two hdds to the DL-VM, one ide with the config and an virtio
> one. Put in S01boot an "ls /dev" and "lsmod" and I see no vda-device,
> wich don't suprise, because lsmod shows only:
> ata_piix
> libata
> loop
>
> Thats all! - so virtio_blk must be loaded after the config file is
readed!
>
> Udo
>  
>
>   On 26.12.2015 16:14, Heiko Zuerker wrote:
>
>> Udo,
>>
>> I'm just working on the booting logic and it seems /dev/vd?? devices
>> are supported already.
>> What exactly doesn't work?
>>
>> Heiko
>>
>> Quoting Udo Lembke <udo...@al...>:
>>
>>> Hi Heiko,
>>> support for config virtio-device would be very nice for me. The most
>>> of my devil linux system are virtualisized.
>>>
>>> Udo
>>>
>>> On 20.12.2015 22:15, Heiko Zuerker wrote:
>>>
>>>> Should we add support for vdX devices ?
>>>>
>>>> Heiko
>>
>>
>> --
>>
>> Regards
>>   Heiko Zuerker
>>  
>>
>>
>>
------------------------------------------------------------------------------
>>
>> _______________________________________________ Devil-linux-discuss
>> mailing list
>>
Dev...@li...://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
--

Regards
  Heiko Zuerker

Hi Heiko,
I use proxmox-ve
(http://proxmox.com/en/downloads/category/iso-images-pve) for
virtualisation (easy solution if you have an free box for test).

It's not depend on the qemu-version - it's the same with 2.2 and 2.4.

The command-line for one VM with an ide (vm-106-disk-1.raw) and an
virtio-hdd (vm-106-disk-2.raw):
root      335033  3.8  0.3 1497000 212924 ?      Sl   Dec29  54:56
/usr/bin/kvm -id 106 -chardev
socket,id=qmp,path=/var/run/qemu-server/106.qmp,server,nowait -mon
chardev=qmp,mode=control -vnc
unix:/var/run/qemu-server/106.vnc,x509,password -pidfile
/var/run/qemu-server/106.pid -daemonize -smbios
type=1,uuid=a9e989b0-843d-4fec-a569-1cfda760978f -name test-dl -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 1024 -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:5197a2bd6852 -drive
file=/mnt/local_iso/template/iso/dl-1.8.0-2015-12-29-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=/mnt/local_pve/images/106/vm-106-disk-2.raw,if=none,id=drive-virtio0,format=raw,aio=native,cache=none,detect-zeroes=on
-device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa
-drive
file=/mnt/local_pve/images/106/vm-106-disk-1.raw,if=none,id=drive-ide0,format=raw,aio=native,cache=none,detect-zeroes=on
-device ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0 -netdev
type=tap,id=net0,ifname=tap106i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on
-device
virtio-net-pci,mac=7A:BC:80:D4:F2:55,netdev=net0,bus=pci.0,addr=0x12,id=net0

Udo

On 30.12.2015 21:57, Heiko Zuerker wrote:
>
> Udo,
>
> I just downloaded QEMU and tested this and I see a different behavior.
> But I'm also new, so I'm not sure if I'm doing this right.
> I don't see a vd0 device at all, the harddisk I configured showed up
> as hda.
> What's the command line you use to start it?
>
> I also added a message now that tells if it detects QEMU and loads the
> modules.
> It correctly loaded them on during my test.
>
> Which version of QEMU are you using? I downloaded 2.5.
>
> Heiko
>

usually qemu/kvm identify itself as:

> CPU: AMD QEMU Virtual CPU

and virtualization detection will definitely work. However, for "-cpu
host" option it uses real cpu information, so I'm afraid detections will
not work.

i.e

# qemu-system-x86_64 --version
QEMU emulator version 2.5.0, Copyright (c) 2003-2008 Fabrice Bellard

no "-cpu host":

> qemu-system-x86_64 -enable-kvm -kernel /tmp/vmlinuz -initrd
/tmp/initrd -append "console=ttyS0" -serial telnet::9001,server,nowait

# mount -t proc none /proc
# cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 6
model name      : QEMU Virtual CPU version 2.5+

with "-cpu host":

# qemu-system-x86_64 -enable-kvm  -cpu host -kernel  /tmp/vmlinuz
-initrd /tmp/initrd -append "console=ttyS0" -serial
telnet::9001,server,nowait

# mount -t proc none /proc
# cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 10
model name      : AMD Phenom(tm) II X6 1090T Processor

i'll try to find another identification sign - and let you know. My
assumption is - qemu uses a very specific seabios, so "dmidecode" or
something similar should identify a vm pretty good.

Serge

On 12/30/2015 12:57 PM, Heiko Zuerker wrote:
> Udo,
> 
> I just downloaded QEMU and tested this and I see a different behavior.
> But I'm also new, so I'm not sure if I'm doing this right.
> I don't see a vd0 device at all, the harddisk I configured showed up as hda.
> What's the command line you use to start it?
> 
> I also added a message now that tells if it detects QEMU and loads the
> modules.
> It correctly loaded them on during my test.
> 
> Which version of QEMU are you using? I downloaded 2.5.
> 
> Heiko
> 
> Quoting Udo Lembke <udo...@al...
> <mailto:udo...@al...>>:
> 
>> Hi Heiko,
>> just testet devil-linux-1.8.0-2015-12-29-i686 with config on vda1 -
>> onscreen message:
>>
>> Creating devices in /dev
>> Assembking Software RAID
>> mdadm: No arrays found in config file or automatically
>> Searching for configuration media
>> Search list:    /dev/hdc
>> Checking for "etc-mods.tar.bz2" on "/dev/hdc" ... file not found
>> Examination of /dev/hdc
>> Would you really like to load DL without Configuration Media?
>>  (y/n)
>>
>>
>> You see, the "Search list" contains the virtual cdrom only.
>>
>> I connect two hdds to the DL-VM, one ide with the config and an virtio
>> one. Put in S01boot an "ls /dev" and "lsmod" and I see no vda-device,
>> wich don't suprise, because lsmod shows only:
>> ata_piix
>> libata
>> loop
>>
>> Thats all! - so virtio_blk must be loaded after the config file is readed!
>>
>>
>> Udo
>>  
>>
>> On 26.12.2015 16:14, Heiko Zuerker wrote:
>>>
>>> Udo,
>>>
>>> I'm just working on the booting logic and it seems /dev/vd?? devices
>>> are supported already.
>>> What exactly doesn't work?
>>>
>>> Heiko
>>>
>>> Quoting Udo Lembke <udo...@al...
>>> <mailto:udo...@al...>>:
>>>
>>>> Hi Heiko,
>>>> support for config virtio-device would be very nice for me. The most
>>>> of my devil linux system are virtualisized.
>>>>
>>>>
>>>> Udo
>>>>
>>>> On 20.12.2015 22:15, Heiko Zuerker wrote:
>>>>>
>>>>> Should we add support for vdX devices ?
>>>>>
>>>>> Heiko
>>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Regards
>>>   Heiko Zuerker
>>>  
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>>
>>> _______________________________________________
>>> Devil-linux-discuss mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>>
> 
> 
> 
> --
> 
> Regards
>   Heiko Zuerker
>  
> 
> 
> ------------------------------------------------------------------------------
> 
> 
> 
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
> 

Hi Heiko, Udo,

could you please check if it's a good VM identification?

> dmesg | grep 'DMI:' | grep -i qemu > /dev/null

# dmesg | grep DMI
DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.2-0-g33fbe13
by qemu-project.org 04/01/2014

i didn't find anything useful yet in busybox' applets. dmidecode is not
very big (~100kb) but i'd rather use kernel buffer.

Serge

On 12/30/2015 07:57 PM, serge wrote:
> usually qemu/kvm identify itself as:
>
>> CPU: AMD QEMU Virtual CPU
> and virtualization detection will definitely work. However, for "-cpu
> host" option it uses real cpu information, so I'm afraid detections will
> not work.
>
> i.e
>
> # qemu-system-x86_64 --version
> QEMU emulator version 2.5.0, Copyright (c) 2003-2008 Fabrice Bellard
>
> no "-cpu host":
>
>> qemu-system-x86_64 -enable-kvm -kernel /tmp/vmlinuz -initrd
> /tmp/initrd -append "console=ttyS0" -serial telnet::9001,server,nowait
>
>
> # mount -t proc none /proc
> # cat /proc/cpuinfo
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 6
> model           : 6
> model name      : QEMU Virtual CPU version 2.5+
>
>
> with "-cpu host":
>
> # qemu-system-x86_64 -enable-kvm  -cpu host -kernel  /tmp/vmlinuz
> -initrd /tmp/initrd -append "console=ttyS0" -serial
> telnet::9001,server,nowait
>
> # mount -t proc none /proc
> # cat /proc/cpuinfo
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 16
> model           : 10
> model name      : AMD Phenom(tm) II X6 1090T Processor
>
> i'll try to find another identification sign - and let you know. My
> assumption is - qemu uses a very specific seabios, so "dmidecode" or
> something similar should identify a vm pretty good.
>
> Serge
>
>
> On 12/30/2015 12:57 PM, Heiko Zuerker wrote:
>> Udo,
>>
>> I just downloaded QEMU and tested this and I see a different behavior.
>> But I'm also new, so I'm not sure if I'm doing this right.
>> I don't see a vd0 device at all, the harddisk I configured showed up as hda.
>> What's the command line you use to start it?
>>
>> I also added a message now that tells if it detects QEMU and loads the
>> modules.
>> It correctly loaded them on during my test.
>>
>> Which version of QEMU are you using? I downloaded 2.5.
>>
>> Heiko
>>
>> Quoting Udo Lembke <udo...@al...
>> <mailto:udo...@al...>>:
>>
>>> Hi Heiko,
>>> just testet devil-linux-1.8.0-2015-12-29-i686 with config on vda1 -
>>> onscreen message:
>>>
>>> Creating devices in /dev
>>> Assembking Software RAID
>>> mdadm: No arrays found in config file or automatically
>>> Searching for configuration media
>>> Search list:    /dev/hdc
>>> Checking for "etc-mods.tar.bz2" on "/dev/hdc" ... file not found
>>> Examination of /dev/hdc
>>> Would you really like to load DL without Configuration Media?
>>>  (y/n)
>>>
>>>
>>> You see, the "Search list" contains the virtual cdrom only.
>>>
>>> I connect two hdds to the DL-VM, one ide with the config and an virtio
>>> one. Put in S01boot an "ls /dev" and "lsmod" and I see no vda-device,
>>> wich don't suprise, because lsmod shows only:
>>> ata_piix
>>> libata
>>> loop
>>>
>>> Thats all! - so virtio_blk must be loaded after the config file is readed!
>>>
>>>
>>> Udo
>>>  
>>>
>>> On 26.12.2015 16:14, Heiko Zuerker wrote:
>>>> Udo,
>>>>
>>>> I'm just working on the booting logic and it seems /dev/vd?? devices
>>>> are supported already.
>>>> What exactly doesn't work?
>>>>
>>>> Heiko
>>>>
>>>> Quoting Udo Lembke <udo...@al...
>>>> <mailto:udo...@al...>>:
>>>>
>>>>> Hi Heiko,
>>>>> support for config virtio-device would be very nice for me. The most
>>>>> of my devil linux system are virtualisized.
>>>>>
>>>>>
>>>>> Udo
>>>>>
>>>>> On 20.12.2015 22:15, Heiko Zuerker wrote:
>>>>>> Should we add support for vdX devices ?
>>>>>>
>>>>>> Heiko
>>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Regards
>>>>   Heiko Zuerker
>>>>  
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>>
>>>> _______________________________________________
>>>> Devil-linux-discuss mailing list
>>>> Dev...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>>>
>>
>>
>> --
>>
>> Regards
>>   Heiko Zuerker
>>  
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>>
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>

Hi Serge,
work with pve3.x (qemu 2.2) but not with pve4.x (qemu 2.4).

pve-3.x:
dmesg | grep DMI
DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org 04/01/2014

pve-4.x:
root@test-dl:~ # dmesg | grep DMI
root@test-dl:~ #

Perhaps better simply grep for qemu? qemu-cdrom must exist, because
there is the devil-linux on.

root@test-dl:~ # dmesg | grep -i qemu
[    0.986947] hda: QEMU HARDDISK, ATA DISK drive
[    2.326925] hdc: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive
[    3.454375] usb 1-1: Product: QEMU USB Tablet
[    3.454376] usb 1-1: Manufacturer: QEMU
[    3.464152] input: QEMU QEMU USB Tablet as
/devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input5
[    3.464179] hid-generic 0003:0627:0001.0001: input: USB HID v0.01
Pointer [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0

Or grep for kvm - I see in both version following:
root@test-dl:~ # dmesg | grep -i kvm
[    0.000000] Booting paravirtualized kernel on KVM

Udo

On 31.12.2015 05:29, serge wrote:
> Hi Heiko, Udo,
>
> could you please check if it's a good VM identification?
>
>> dmesg | grep 'DMI:' | grep -i qemu > /dev/null
> # dmesg | grep DMI
> DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.2-0-g33fbe13
> by qemu-project.org 04/01/2014
>
> i didn't find anything useful yet in busybox' applets. dmidecode is not
> very big (~100kb) but i'd rather use kernel buffer.
>
> Serge
>
> On 12/30/2015 07:57 PM, serge wrote:
>> usually qemu/kvm identify itself as:
>>
>>> CPU: AMD QEMU Virtual CPU
>> and virtualization detection will definitely work. However, for "-cpu
>> host" option it uses real cpu information, so I'm afraid detections will
>> not work.
>>
>> i.e
>>
>> # qemu-system-x86_64 --version
>> QEMU emulator version 2.5.0, Copyright (c) 2003-2008 Fabrice Bellard
>>
>> no "-cpu host":
>>
>>> qemu-system-x86_64 -enable-kvm -kernel /tmp/vmlinuz -initrd
>> /tmp/initrd -append "console=ttyS0" -serial telnet::9001,server,nowait
>>
>>
>> # mount -t proc none /proc
>> # cat /proc/cpuinfo
>> processor       : 0
>> vendor_id       : AuthenticAMD
>> cpu family      : 6
>> model           : 6
>> model name      : QEMU Virtual CPU version 2.5+
>>
>>
>> with "-cpu host":
>>
>> # qemu-system-x86_64 -enable-kvm  -cpu host -kernel  /tmp/vmlinuz
>> -initrd /tmp/initrd -append "console=ttyS0" -serial
>> telnet::9001,server,nowait
>>
>> # mount -t proc none /proc
>> # cat /proc/cpuinfo
>> processor       : 0
>> vendor_id       : AuthenticAMD
>> cpu family      : 16
>> model           : 10
>> model name      : AMD Phenom(tm) II X6 1090T Processor
>>
>> i'll try to find another identification sign - and let you know. My
>> assumption is - qemu uses a very specific seabios, so "dmidecode" or
>> something similar should identify a vm pretty good.
>>
>> Serge
>>
>>
>> On 12/30/2015 12:57 PM, Heiko Zuerker wrote:
>>> Udo,
>>>
>>> I just downloaded QEMU and tested this and I see a different behavior.
>>> But I'm also new, so I'm not sure if I'm doing this right.
>>> I don't see a vd0 device at all, the harddisk I configured showed up as hda.
>>> What's the command line you use to start it?
>>>
>>> I also added a message now that tells if it detects QEMU and loads the
>>> modules.
>>> It correctly loaded them on during my test.
>>>
>>> Which version of QEMU are you using? I downloaded 2.5.
>>>
>>> Heiko
>>>
>>> Quoting Udo Lembke <udo...@al...
>>> <mailto:udo...@al...>>:
>>>
>>>> Hi Heiko,
>>>> just testet devil-linux-1.8.0-2015-12-29-i686 with config on vda1 -
>>>> onscreen message:
>>>>
>>>> Creating devices in /dev
>>>> Assembking Software RAID
>>>> mdadm: No arrays found in config file or automatically
>>>> Searching for configuration media
>>>> Search list:    /dev/hdc
>>>> Checking for "etc-mods.tar.bz2" on "/dev/hdc" ... file not found
>>>> Examination of /dev/hdc
>>>> Would you really like to load DL without Configuration Media?
>>>>  (y/n)
>>>>
>>>>
>>>> You see, the "Search list" contains the virtual cdrom only.
>>>>
>>>> I connect two hdds to the DL-VM, one ide with the config and an virtio
>>>> one. Put in S01boot an "ls /dev" and "lsmod" and I see no vda-device,
>>>> wich don't suprise, because lsmod shows only:
>>>> ata_piix
>>>> libata
>>>> loop
>>>>
>>>> Thats all! - so virtio_blk must be loaded after the config file is readed!
>>>>
>>>>
>>>> Udo
>>>>  
>>>>
>>>> On 26.12.2015 16:14, Heiko Zuerker wrote:
>>>>> Udo,
>>>>>
>>>>> I'm just working on the booting logic and it seems /dev/vd?? devices
>>>>> are supported already.
>>>>> What exactly doesn't work?
>>>>>
>>>>> Heiko
>>>>>
>>>>> Quoting Udo Lembke <udo...@al...
>>>>> <mailto:udo...@al...>>:
>>>>>
>>>>>> Hi Heiko,
>>>>>> support for config virtio-device would be very nice for me. The most
>>>>>> of my devil linux system are virtualisized.
>>>>>>
>>>>>>
>>>>>> Udo
>>>>>>
>>>>>> On 20.12.2015 22:15, Heiko Zuerker wrote:
>>>>>>> Should we add support for vdX devices ?
>>>>>>>
>>>>>>> Heiko
>>>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Regards
>>>>>   Heiko Zuerker
>>>>>  
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Devil-linux-discuss mailing list
>>>>> Dev...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>>>>
>>>
>>> --
>>>
>>> Regards
>>>   Heiko Zuerker
>>>  
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>>
>>>
>>> _______________________________________________
>>> Devil-linux-discuss mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

  Udo,

I'll change the code to do the "dmesg | grep -i qemu". This way we have at
least something that works, until Serge finds a nicer solution.

Heiko

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

> Hi Serge,
> work with pve3.x (qemu 2.2) but not with pve4.x (qemu 2.4).
>
> pve-3.x:
> dmesg | grep DMI
> DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> rel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org 04/01/2014
>
> pve-4.x:
> root@test-dl:~ # dmesg | grep DMI
> root@test-dl:~ #
>
> Perhaps better simply grep for qemu? qemu-cdrom must exist, because
> there is the devil-linux on.
>
> root@test-dl:~ # dmesg | grep -i qemu
> [    0.986947] hda: QEMU HARDDISK, ATA DISK drive
> [    2.326925] hdc: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive
> [    3.454375] usb 1-1: Product: QEMU USB Tablet
> [    3.454376] usb 1-1: Manufacturer: QEMU
> [    3.464152] input: QEMU QEMU USB Tablet as
>
/devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input5
> [    3.464179] hid-generic 0003:0627:0001.0001: input: USB HID v0.01
> Pointer [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
>
> Or grep for kvm - I see in both version following:
> root@test-dl:~ # dmesg | grep -i kvm
> [    0.000000] Booting paravirtualized kernel on KVM
>
> Udo
>
> On 31.12.2015 05:29, serge wrote:
>> Hi Heiko, Udo,
>>
>> could you please check if it's a good VM identification?
>>
>>> dmesg | grep 'DMI:' | grep -i qemu > /dev/null
>>
>> # dmesg | grep DMI
>> DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.2-0-g33fbe13
>> by qemu-project.org 04/01/2014
>>
>> i didn't find anything useful yet in busybox' applets. dmidecode is not
>> very big (~100kb) but i'd rather use kernel buffer.
>>
>> Serge
>>
>> On 12/30/2015 07:57 PM, serge wrote:
>>> usually qemu/kvm identify itself as:
>>>
>>>> CPU: AMD QEMU Virtual CPU
>>>
>>> and virtualization detection will definitely work. However, for "-cpu
>>> host" option it uses real cpu information, so I'm afraid detections
will
>>> not work.
>>>
>>> i.e
>>>
>>> # qemu-system-x86_64 --version
>>> QEMU emulator version 2.5.0, Copyright (c) 2003-2008 Fabrice Bellard
>>>
>>> no "-cpu host":
>>>
>>>> qemu-system-x86_64 -enable-kvm -kernel /tmp/vmlinuz -initrd
>>>
>>> /tmp/initrd -append "console=ttyS0" -serial telnet::9001,server,nowait
>>>
>>> # mount -t proc none /proc
>>> # cat /proc/cpuinfo
>>> processor       : 0
>>> vendor_id       : AuthenticAMD
>>> cpu family      : 6
>>> model           : 6
>>> model name      : QEMU Virtual CPU version 2.5+
>>>
>>> with "-cpu host":
>>>
>>> # qemu-system-x86_64 -enable-kvm  -cpu host -kernel  /tmp/vmlinuz
>>> -initrd /tmp/initrd -append "console=ttyS0" -serial
>>> telnet::9001,server,nowait
>>>
>>> # mount -t proc none /proc
>>> # cat /proc/cpuinfo
>>> processor       : 0
>>> vendor_id       : AuthenticAMD
>>> cpu family      : 16
>>> model           : 10
>>> model name      : AMD Phenom(tm) II X6 1090T Processor
>>>
>>> i'll try to find another identification sign - and let you know. My
>>> assumption is - qemu uses a very specific seabios, so "dmidecode" or
>>> something similar should identify a vm pretty good.
>>>
>>> Serge
>>>
>>> On 12/30/2015 12:57 PM, Heiko Zuerker wrote:
>>>> Udo,
>>>>
>>>> I just downloaded QEMU and tested this and I see a different behavior.
>>>> But I'm also new, so I'm not sure if I'm doing this right.
>>>> I don't see a vd0 device at all, the harddisk I configured showed up
>>>> as hda.
>>>> What's the command line you use to start it?
>>>>
>>>> I also added a message now that tells if it detects QEMU and loads the
>>>> modules.
>>>> It correctly loaded them on during my test.
>>>>
>>>> Which version of QEMU are you using? I downloaded 2.5.
>>>>
>>>> Heiko
>>>>
>>>> Quoting Udo Lembke <udo...@al...
>>>> <mailto:udo...@al...>>:
>>>>
>>>>> Hi Heiko,
>>>>> just testet devil-linux-1.8.0-2015-12-29-i686 with config on vda1 -
>>>>> onscreen message:
>>>>>
>>>>> Creating devices in /dev
>>>>> Assembking Software RAID
>>>>> mdadm: No arrays found in config file or automatically
>>>>> Searching for configuration media
>>>>> Search list:    /dev/hdc
>>>>> Checking for "etc-mods.tar.bz2" on "/dev/hdc" ... file not found
>>>>> Examination of /dev/hdc
>>>>> Would you really like to load DL without Configuration Media?
>>>>> (y/n)
>>>>>
>>>>> You see, the "Search list" contains the virtual cdrom only.
>>>>>
>>>>> I connect two hdds to the DL-VM, one ide with the config and an
virtio
>>>>> one. Put in S01boot an "ls /dev" and "lsmod" and I see no vda-device,
>>>>> wich don't suprise, because lsmod shows only:
>>>>> ata_piix
>>>>> libata
>>>>> loop
>>>>>
>>>>> Thats all! - so virtio_blk must be loaded after the config file is
>>>>> readed!
>>>>>
>>>>> Udo
>>>>>
>>>>> On 26.12.2015 16:14, Heiko Zuerker wrote:
>>>>>> Udo,
>>>>>>
>>>>>> I'm just working on the booting logic and it seems /dev/vd?? devices
>>>>>> are supported already.
>>>>>> What exactly doesn't work?
>>>>>>
>>>>>> Heiko
>>>>>>
>>>>>> Quoting Udo Lembke <udo...@al...
>>>>>> <mailto:udo...@al...>>:
>>>>>>
>>>>>>> Hi Heiko,
>>>>>>> support for config virtio-device would be very nice for me. The
most
>>>>>>> of my devil linux system are virtualisized.
>>>>>>>
>>>>>>> Udo
>>>>>>>
>>>>>>> On 20.12.2015 22:15, Heiko Zuerker wrote:
>>>>>>>> Should we add support for vdX devices ?
>>>>>>>>
>>>>>>>> Heiko
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Regards
>>>>>>   Heiko Zuerker
>>>>>>
>>>>>>
------------------------------------------------------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> Devil-linux-discuss mailing list
>>>>>> Dev...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>>>
>>>> --
>>>>
>>>> Regards
>>>>   Heiko Zuerker
>>>>
>>>>
------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Devil-linux-discuss mailing list
>>>> Dev...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
>>
------------------------------------------------------------------------------
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>
------------------------------------------------------------------------------
> _______________________________________________
> Devil-linux-discuss mailing list
>
Dev...@li...://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
--

Regards
  Heiko Zuerker