Hypervisor status still error..

[dndud2532]

Hello, I downloaded IsardVDI open source and implemented it by following the guide of Quick Start and Installation, but the status of the hypervisor is continuously showing as an error, so I ask for a guide on how to solve it. Is there anything else I need to do to enable the hypervisor? Also, it seems that the error persists because the hypervisor connection is not working for templates and ISO downloads through download other than user creation. Is this correct? Please give me a solution.

my configuration environment

• VMware ESXi CentOS7 VM
• Hardware nested virtualization enabled
• selinux disabled

What I tried to solve the above problem and what I referenced are as follows.

• Fix docker networking in isardvdi.cfg (See Trouble connecting hypervisor #404, #408)

Thank you.

[jvinolas]

Please first check the faq about possible error on virtualization: https://isard.gitlab.io/isardvdi-docs/admin/faq/#after-finishing-install-the-default-isard-hypervisor-is-disabled-or-shows-error

It everything looks good then bring the compose down, remove /opt/isard-local and /opt/isard folders and bring compose up again (it will start clean).

If the hypervisor doesn't register then try setting LOG_LEVEL=DEBUG at isardvdi.cfg, build again the compose and bring it up and provide us the docker logs isard-api and docker logs isard-engine to analyze what could be happening in your system.

[dndud2532]

Thanks for your help.

I checked the methods you gave me first, but the symptoms are the same.

1 Check the FAQ guide

2 Delete /opt/isard-local, /opt/isard folder and docker-compose up

I am checking additional isard-api and isard-engine logs, and if there is a guide for actions related to those logs, please.

thank you

2022년 8월 1일 (월) 오전 4:57, Josep Maria Viñolas Auquer < @.***>님이 작성:

Please first check the faq about possible error on virtualization: https://isard.gitlab.io/isardvdi-docs/admin/faq/#after-finishing-install-the-default-isard-hypervisor-is-disabled-or-shows-error

It everything looks good then bring the compose down, remove /opt/isard-local and /opt/isard folders and bring compose up again (it will start clean).

If the hypervisor doesn't register then try setting LOG_LEVEL=DEBUG at isardvdi.cfg, build again the compose and bring it up and provide us the docker logs isard-api and docker logs isard-engine to analyze what could be happening in your system.

— Reply to this email directly, view it on GitHub https://github.com/isard-vdi/isard/issues/425#issuecomment-1200489377, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6RXL6U7D7GFPJ2T7W3C73VW3LEFANCNFSM55FHZTAQ . You are receiving this because you authored the thread.Message ID: @.***>

[jvinolas]

Wait, maybe you are using the prebuilt docker-compose.yml that you could download (it is deprecated).

Please use new install method:

 git clone https://gitlab.com/isard/isardvdi
cd isardvdi
cp isardvdi.cfg.example isardvdi.cfg
./build.sh
docker-compose pull
docker-compose up -d

[dndud2532]

I created a clean image VM and tried it with the guide you gave me, but the symptoms are the same.. Is there anything I need to do before GIT Clone?

Thanks for your help.

2022년 8월 1일 (월) 오후 3:15, Josep Maria Viñolas Auquer < @.***>님이 작성:

Wait, maybe you are using the prebuilt docker-compose.yml that you could download (it is deprecated).

Please use new install method:

git clone https://gitlab.com/isard/isardvdi cd isardvdi cp isardvdi.cfg.example isardvdi.cfg ./build.sh docker-compose pull docker-compose up -d

— Reply to this email directly, view it on GitHub https://github.com/isard-vdi/isard/issues/425#issuecomment-1200758002, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6RXL3ICFGYJRXXQYQQJALVW5TP3ANCNFSM55FHZTAQ . You are receiving this because you authored the thread.Message ID: @.***>

[jvinolas]

Without the isard-api and isard-engine logs it is almost impossible to evaluate what is happening in your system.

The hypervisor should have nested virtualization activated and I'm pretty sure it could be that. In a running system it should show the virtualization at hyper column like this:

Also note that maybe there is the latest error messate in Status detailed info.

If you could provide the logs then we could analyze what it is happening.

[dndud2532]

I attached the log file as an attachment to the G-mail reply in the last reply, but it doesn't seem to be visible, so I will share it again as a Github captured image.

Can this log be analyzed?

P.S : I tried restarting and reinstalling the libvirtd service to fix the libvirtd virtqemud-socket error that was already checked in the isard-engins error.

Thank you

-isard-api log

-isard-engine log <1>

-isard-engine log <2>

[jvinolas]

It seems a docker network problem. Are you able to ping isard-api from isard-hypervisor?

# docker exec -ti isard-hypervisor ping isard-api
PING isard-api (172.31.255.10): 56 data bytes
64 bytes from 172.31.255.10: seq=0 ttl=64 time=0.083 ms
64 bytes from 172.31.255.10: seq=1 ttl=64 time=0.073 ms

[dndud2532]

There is no problem with that communication. Are there more things to check?

Thank you.

[dndud2532]

Do you have a recommended OS version?

2022년 8월 2일 (화) 오후 4:21, Josep Maria Viñolas Auquer < @.***>님이 작성:

It seems a docker network problem. Are you able to ping isard-api from isard-hypervisor?

docker exec -ti isard-hypervisor ping isard-api

PING isard-api (172.31.255.10): 56 data bytes 64 bytes from 172.31.255.10: seq=0 ttl=64 time=0.083 ms 64 bytes from 172.31.255.10: seq=1 ttl=64 time=0.073 ms

— Reply to this email directly, view it on GitHub https://github.com/isard-vdi/isard/issues/425#issuecomment-1202113714, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6RXL7HU3BK4DJF5L7JNRLVXDD7XANCNFSM55FHZTAQ . You are receiving this because you authored the thread.Message ID: @.***>

[dndud2532]

Hello, I'm still configuring to complete the setup, but the above problem doesn't seem to be resolved, so I'm asking again.

First of all, if you use git-clone to download the isardvdi.cfg file and complete compose as instructed, all containers will be running.

However, the hypervisor connection does not continue after that, but I have a few questions.

1 If I build compose without changing isard-cfg and other files in an environment where nested virtualization is running, does the hypervisor come out normally?

2 It doesn't work even if I refer to the hypervisor configuration guide on the web page, can you provide detailed steps?

(/reset-hyper.sh file does not exist, etc.)

3 Logs of isard-hypervisor, isard-engine, etc. have been uploaded below.

1. isard-hypervisor

2. isard-engine

libvirtd service : libvirt service is running but crashes again on isard-hypervisor startup

There is a virtqemud-sock socket file, but it does not run.

3. in isard-hypervisor

[jvinolas]

Do you have a recommended OS version? 2022년 8월 2일 (화) 오후 4:21, Josep Maria Viñolas Auquer < @.>님이 작성: … It seems a docker network problem. Are you able to ping isard-api from isard-hypervisor? # docker exec -ti isard-hypervisor ping isard-api PING isard-api (172.31.255.10): 56 data bytes 64 bytes from 172.31.255.10: seq=0 ttl=64 time=0.083 ms 64 bytes from 172.31.255.10: seq=1 ttl=64 time=0.073 ms — Reply to this email directly, view it on GitHub <#425 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6RXL7HU3BK4DJF5L7JNRLVXDD7XANCNFSM55FHZTAQ . You are receiving this because you authored the thread.Message ID: @.>

What OS are you using? We deploy it either with Debian or Ubuntu.

You should take care of apparmor on those distros and selinux in Fedora/CentOS

[jvinolas]

Do you have KVM installed on host system? You should remove it, it could conflict with the privileged isard-hypervisor container where KVM will be started.

[dndud2532]

Hello, thank you for your support. I saw in the documentation that wireguard needs to be additionally installed, and after I installed it, I saw the hypervisor go online

408

After the hypervisor is online, I'm running tests to run the VM, and I've run into some issues. This section will be rewritten as an additional issue.

[jvinolas]

Nice to see it is working. I suspect that the problem was actually with the kernel, that maybe was upgraded during the wireguard install.