[elbe-users] 'initvm create' fails on Debian stretch with elbe >= 12.5

[Hentschel Martin]

Hi everyone,

We are using elbe on Debian Stretch (9.12) inside a VMWare VM.
With elbe 12.4+deb9+build84 just calling command ‘elbe initvm create’ created a working initvm.
With elbe 12.5 and elbe 13 calling ‘elbe initvm create’ results in the following error during initvm creation.

…
cd .elbe-in/initrd-tree && find . | cpio -H newc -o --append -F ../../.elbe-gen/initrd-preseeded
48662 blocks
gzip -9f .elbe-gen/initrd-preseeded
qemu-img create -f qcow2 initvm-base.img 80G
Formatting 'initvm-base.img', fmt=qcow2 size=85899345920 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
/usr/bin/kvm
qemu-system-x86_64: /build/qemu-NMEKjq/qemu-2.8+dfsg/target-i386/kvm.c:1822: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
Aborted

------------------------------------------------------------------
kvm failed to start
This is most likely the case, because /dev/kvm is not available.
To use KVM inside a VMWARE or other VM instance,
nested KVM needs to be supported
------------------------------------------------------------------

Makefile:45: recipe for target 'initvm-base.img' failed
make: *** [initvm-base.img] Error 1
Building the initvm Failed
Giving up


Installed qemu packages are the following:
ii  ipxe-qemu                             1.0.0+git-20161027.b991c67-1      all          PXE boot firmware - ROM images for qemu
ii  qemu-kvm                              1:2.8+dfsg-6+deb9u11              amd64        QEMU Full virtualization on x86 hardware
ii  qemu-system-common                    1:2.8+dfsg-6+deb9u11              amd64        QEMU full system emulation binaries (common files)
ii  qemu-system-x86                       1:2.8+dfsg-6+deb9u11              amd64        QEMU full system emulation binaries (x86)
ii  qemu-utils                            1:2.8+dfsg-6+deb9u11              amd64        QEMU utilities


Anyone an idea about the cause of this error.
Google has a lot of hits according to the message. Since elbe v12.4 works properly, I guess a change in v12.5 causes the error.

Best regards

Martin Hentschel
Development Engineer
Process Automation - Fieldbus Technology

Pepperl+Fuchs SE
Lilienthalstrasse 200
68307 Mannheim
Germany


[e-news abonnieren]<http://www.pepperl-fuchs.de/e-news> [YouTube: Pepperl+Fuchs auf YouTube] <https://www.youtube.com/c/pepperl-fuchs>  [@PepperlFuchsDE folgen] <https://twitter.com/PepperlFuchsDE>   [Pepperl+Fuchs auf XING] <https://www.xing.com/companies/pepperl%252bfuchsgmbh>         [Pepperl+Fuchs auf LinkedIn] <https://www.linkedin.com/company/pepperl-fuchs-group/>

________________________________
[Pepperl+Fuchs GmbH]<http://www.pepperl-fuchs.com>

Denken Sie bitte an die Umwelt und prüfen Sie, ob diese E-Mail wirklich ausgedruckt werden muss.

SocialMedia2014



Pepperl+Fuchs SE, Mannheim
Vorstände/Board members: Dr.-Ing. Gunther Kegel (Vors.), Werner Guthier (stellv. Vors.), Mehmet Hatiboglu
Vorsitzender des Aufsichtsrats/Chairman of the supervisory board: Michael Fuchs sen.
Registergericht/Register Court: AG Mannheim HRB 737016 ∙ UST-ID Nr. DE 143877372

Wichtiger Hinweis:
Diese E-Mail einschliesslich ihrer Anhaenge enthaelt vertrauliche und rechtlich geschuetzte Informationen, die nur fuer den Adressaten bestimmt sind. Sollten Sie nicht der bezeichnete Adressat sein, so teilen Sie dies bitte dem Absender umgehend mit und loeschen Sie diese Nachricht und ihre Anhaenge. Die unbefugte Weitergabe, das Anfertigen von Kopien und jede Veraenderung der E-Mail ist untersagt. Der Absender haftet nicht fuer die Inhalte von veraenderten E-Mails.
Important Information:
This e-mail message including its attachments contains confidential and legally protected information solely intended for the addressee. If you are not the intended addressee of this message, please contact the addresser immediately and delete this message including its attachments. The unauthorized dissemination, copying and change of this e-mail are strictly forbidden. The addresser shall not be liable for the content of such changed e-mails.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linutronix.de/pipermail/elbe-users/attachments/20201014/3c64d481/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image20ffd2.BMP
Type: image/bmp
Size: 1782 bytes
Desc: image20ffd2.BMP
URL: <http://lists.linutronix.de/pipermail/elbe-users/attachments/20201014/3c64d481/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image1ef5a8.BMP
Type: image/bmp
Size: 1782 bytes
Desc: image1ef5a8.BMP
URL: <http://lists.linutronix.de/pipermail/elbe-users/attachments/20201014/3c64d481/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagec7c86a.BMP
Type: image/bmp
Size: 1782 bytes
Desc: imagec7c86a.BMP
URL: <http://lists.linutronix.de/pipermail/elbe-users/attachments/20201014/3c64d481/attachment-0007.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image8787e0.BMP
Type: image/bmp
Size: 1782 bytes
Desc: image8787e0.BMP
URL: <http://lists.linutronix.de/pipermail/elbe-users/attachments/20201014/3c64d481/attachment-0008.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image59f839.PNG
Type: image/png
Size: 431 bytes
Desc: image59f839.PNG
URL: <http://lists.linutronix.de/pipermail/elbe-users/attachments/20201014/3c64d481/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image5fbf62.BMP
Type: image/bmp
Size: 55350 bytes
Desc: image5fbf62.BMP
URL: <http://lists.linutronix.de/pipermail/elbe-users/attachments/20201014/3c64d481/attachment-0009.bin>