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

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

  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