If you create every vmx-vcp on your own, this problem doesn't exists, so I think there is a mistake in the base-mac creation. Would be cool if this can be fixed. I'm not aware if other image have this problem as well.

2. If you use the HTML Wireshark, only packets till 1518 will be seen, higher packet length will not be seen, reason is because the docker eth has an mtu of 1500.

To be honest I've no idea what it does and why it's not default, but at least for me it saved a huge amount of cpu cycles and I didn't noticed any problems at all.

4. I tried to create another linux vm with libvirt. As long as no eve-ng image is running the libvirt vm is stable, but as soon I start one machine, the machine will be exited with code 15 and one restart it will fail after 10 seconds. Unfortunately I don't know how to troubleshoot this. If I start the machine by hand with qemu it works fine.

5. At least for my installation about 3 weeks ago, the qemu-3.1 is missing, there is non under /opt

Lastly a some nice to have things as feature request:
a. store a default config in template folder which can be attached directly to the vm. really cool would be with some variables like ip addresses.

b. define a standard cloud for the management interface in a template. I usally connect the fxp to cloud0 for oob access. It would be nice if this could be default.

c. please add https to the forum

I think thats all from now on. Looking forward to hearing from you and thanks in advance
Viets

1. I will review the code to fix this.
2. Indeed, you are right , but to not force everybody to rebuild the docker, I will add this setting in the creation of the container on the fly as well.
3. Very nice catch. we will test impact on other nodes as well.
4. Libvirt is not supported and not advised. EVE API handle kvm nodes itself
5. qemu 3.1 require some api modification due to arguments depreciation so it is still in progress
6. https is already active fort both www.eve-ng.net and sub-site ( forum )

For me it looks like one of these processes is killing my qemu. Is this expected as some kind of job running to prevent running other vms? Is this a bug, or simply not supported?

It would be very nice to have a possibility to run one vm at startup. I'ld like to do some disk passthrough and I wasn't able to do this in eve directly. Just to make sure I'm now testing with a standard ubuntu image, no passthrough involved, so it's not the trigger.

Furthermore I know that this is even more unsupported, but I tried to run virtualbox or vmware workstation on this box, but It failed always with:

make[2]: *** [/tmp/modconfig-hJQay6/vmnet-only/vnetUserListener.o] Error 1
In file included from ./include/linux/compat.h:16:0,
from ./include/linux/ethtool.h:17,
from ./include/linux/netdevice.h:41,
from /tmp/modconfig-hJQay6/vmnet-only/userif.c:29:
./include/linux/if.h:28:54: fatal error: sys/socket.h: No such file or directory

Even though I've installed kernel headers, I wasn't able to find root cause yet, do you have an idea? Is there something missing in the kernel-headers? Ubuntu kernels work fine.

Is there a reason why it's prohibited? I'ld understand that if you like to protect your license for example. But I have a valid license and it is checked regulary. So I don't understand why it should not be allowed. Even more this should also prevent this howto (didn't tested yet):

Because we see eve-ng pro as an appliance.
We give support and it will be a nightmare to manage customization.

Our vision is like CUCM CallManager: It is a Redhat system but only Cisco stuff and needed daemons , tools runs on it.

Linux OS does not mean we support to use it as any linux distribution.
Pro will get more and more features like ram/cpu/disk usage limit per user. The be able to offer such, EVE APi will control all the qemu processes to brings the best performance for EVE services only.

The goal is to brings a well managed solution.

Use a seperate server to runs other services than those offered by EVE.
If some features are needed, as you saw previously, we are open to discussion and to include new stuff if we thing that it is a benefit for majority of users....

None of the services janus , cpulimit or tomcat is involved in this limitation/control.

node's qemu options permit to add fancy stuff..... starting a VM at boot time could be achieved using API calls from a script..... ( login, the start a node from a lab..... )

Care should be taken when setting the halt_poll_ns module parameter as a
large value has the potential to drive the cpu usage to 100% on a machine which
would be almost entirely idle otherwise. This is because even if a guest has
wakeups during which very little work is done and which are quite far apart, if
the period is shorter than the global max polling interval (halt_poll_ns) then
the host will always poll for the entire block time and thus cpu utilisation
will go to 100%.