Ubuntu / Lubuntu 22.04.1 broken in Community 5.0.1-13

[mlacomb]

All:

Been fighting an issue since trying to bring up a new instance of eve-ng at home. The issue occurs in the Community edition 5.0.1-13 in the following installations:

Code: Select all

1.  Dell R620 server, E5-2660 8core 256GB ram 2x300gb SAS raid0
     a.  Bare metal install
     b.  ESXI 8 free edition licensed Install 
          1.  given 8 cores and 128GB
     c.  Proxmox 7.2 (latest? as of 2 weeks ago)
          1.  given 12 cores and 128GB
2.  SuperMicro 1u server SYS5018D-FN8T Xeon-D 1518, 32GB ram 4x300GB SATA/NVME
    a.  ESXI 7.03 free edition licensed install
         1.  given 4 cores and 16GB ram

What occurs - I import a new iso of Linux (either ubuntu or Lubuntu, 22.04.1) to the proper /opt/uunet/addons/qemu subdirectory set, renaming to cdrom.iso and creating a 30GB HDD as described in the official eve Linux image documentation. I then run the fixpermissions command. Next, I create a blank lab with the new linux instance in it and a mgmt net connection to the outside world. I then launch the VM connected to the Management Net to get updates. Launching the VM works properly, and I can VNC to it or SSH to it as usual.
SSH stays connected throughout the issues, and I see panics in the syslog - however the system stays active. On the remote VNC side though, the video crashes - and sometimes, the subsystem restarts and prompts me with a login screen (put in password). I can do so, but on other crashes, the display subsystem just goes "gray" in VNC and doesn't respond.
I've also seen graphical glitches as I move the mouse around (almost seeming like the video memory is getting corrupted somehow?)

What works correctly: if I use either a bare metal Eve-NG pro (5.0.1-20) or I use my older setup - vmware workstation player 17 free on an AMD system (community edition 2.0.3-112 with an older 4.20.17 linux kernel). I do the exact same process as above and do NOT experience the crashes with the exact same ISO files (md5 verified etc.)

It appears that there are fixes (?) to QEMU in 5.0.1-20 that need brought forward to the community version. Does anyone have any thoughts on this - and potentially how I can patch this issue so I can move forward on my home lab environment without this issue?

[Uldis (UD)]

Ubuntu 22.04 is not supported
use Ubuntu 20.04

[mlacomb]

Understood. I've not followed the community release schedule, however when is the next release due?

[mlacomb]

Just installed 20.04.5 desktop on baremetal r620 (specs in first post) - same issues are occurring. Video corruption, blanking and reset of gnome user session - as well as kernel segfaults in syslog.

[Uldis (UD)]

Excuseme, but please read our cookbook mate
you again doing what is not told
EVE OS is Ubuntu 20.04 Server !!!
https://www.eve-ng.net/index.php/docume ... -cookbook/

[mlacomb]

Apologies, and thank you for the clarification. To be clear, I'm using the eve-ng installation media (.iso) to install eve-ng in every scenario in my primary post, and the issue occurs when running the ubuntu VM within eve-ng, just in case we're on the wrong page.

There are only 3 places that reference 20.04 in the cookbook, and all 3 references are for installing eve-ng itself, but not references to actual LAB VMs:

1: Operation System: Ubuntu Server 20.04.4 LTS x64 (under 2.1.4 Dedicated Server (bare) system requirements)
2: Ubuntu Server 20.04 LTS as platform for bare metal (under 2.2 Supported virtualization platforms and software)
3: Step 2: create a nested Ubuntu 20.04 image model. (under 3.4 Google Cloud Platform)

The requirements in the 3 statements above are definitely satisfied if I install using the official eve-ng iso - since 20.04 server is the official release installed each time.

My only ask at this point is when will enhancements in 5.1.20 (pro) trickle down to community? At this point I can run 22.04.1 via separate virtual machines and patch it into my labs as needed via other nets. Thanks!