[community] on restart, 2 process are handling the same VM

[nicolasb827-1]

Hello,

(first, environment)

Hardware : 2x Xeon(R) CPU E5-2667 0 @ 2.90GHz (24 Cores), 128GB RAM, 500G HDD, 4 network interfaces
EVE-NG Running on - Bare Metal Linux (Ubuntu 20.04.6 LTS), community edition 5.0.1-24
VT-X - Enabled

I have created an Almalinux 9 image as documented. It starts perfectly in VNC. Network is good too.

1. check the path of the image ( for windows win-XXXX)
/opt/unetlab/addons/qemu/linux-almalinux-9

2. have you fixed permission(/opt/unetlab/wrappers/unl_wrapper -a fixpermissions)
yes

3. file name format matches against EVE-NG requirement mentioned in the site.

/opt/unetlab/addons/qemu/linux-almalinux-9/virtioa.qcow2

4. Check the logs /opt/unetlab/data/Logs/

I do not know what to search for

- my problem(s):

I created 2 admin accounts, sharing the same lab. When I start a VM, other admin sees the VM stopped (even with refresh) but he can connect to VNC console.
When he tries to start a VM, it is launched (green message) but stay poweroff (black square) on GUI. But, using ps on server, we can see 2 VMs :

Code: Select all

root@eve-ng:~# ps ax  | grep qemu-system-x86_64| grep IPA-213
  50538 ?        Sl    12:56 /opt/qemu-2.12.0/bin/qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=00:50:01:00:0a:00 -netdev tap,id=net0,ifname=vunl1_10_0,script=no -smp 2 -m 4096 -name IPA-213 -uuid cb682809-ac72-4a7b-ba15-0fb565b76e02 -vnc :27006 -drive file=virtioa.qcow2,if=virtio,bus=0,unit=0,cache=none -machine type=pc,accel=kvm -vga std -usbdevice tablet -boot order=cd -cpu host
 115326 ?        Sl     1:55 /opt/qemu-2.12.0/bin/qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=00:50:01:00:0a:00 -netdev tap,id=net0,ifname=vunl0_10_0,script=no -smp 2 -m 4096 -name IPA-213 -uuid cb682809-ac72-4a7b-ba15-0fb565b76e02 -vnc :26878 -drive file=virtioa.qcow2,if=virtio,bus=0,unit=0,cache=none -machine type=pc,accel=kvm -vga std -usbdevice tablet -boot order=cd -cpu host
 

same UUID, different VNC port.
So, strange behavior appears (I guess the hdd is shared between vms).

Is it a known problem related to community version ?
How can I dig deeper to find the problem ?
I tried to check using virsh, but eve is not using libvirtd i guess.
Thank you for your help
Nicolas.

[jameslu]

Hello,
I think you should check for shared resources. Verify if the VMs are using the same disk image (virtioa.qcow2) for storage. If both VMs are using the same image, it can lead to conflicts and unexpected behavior. Make sure that each VM has its own separate disk image.