Hi @Sugarat. thanks for the report.
Can you try this branch: fix-handle-inavlid-vm-creation?
This should fix the issue

@rs Yes, this is normal. I am still working on making the installation possible via XO.

Hi @RS.
I just wanted to know if you can test this branch: fix-xs-8-patches.
It should fix the list of missing patches (not the RPU or other update function from XO)

Well, the problem is here then.
The XAPI reports NULL (NULL) so XO can't compare your bios version and display if it is up to date or not.

@olivierlambert Do you know why there is no value here?

Good catch for the extra underscore, it will be fixed, BTW xo-cli should not return true. In your host's Advanced tab, what is shown in Manufacturer Information and BIOS Information?

Hi.
The IPMI plugin is only used to display hardware information if you are using mona_1.44gg.

To display if a BIOS update is available, we mainly fetch this endpoint: https://pictures.2cr.si/Images_site_web_Odoo/Pages_produit/VATES-BIOS_BMC_last-version.json

Does your host have access to this endpoint?
What is the ouput of xo-cli host.getBiosInfo id=<host-id>

Hi
Indeed. We will see how we can fix this bug.
Thanks

@JamfoFL As the bug appears to be non-trivial, I’ll create the issue on our end, and then we’ll see with the team to schedule this task. We’ll keep you updated here.

Hi. I am finally able to reproduce the end of alert issue.
However, I was only able to reproduce if I used the "ALL *" options and not by manually selecting the objects to monitor. Can you confirm that you are using All running VMs/Hosts/SRs?

I see that the bug is actually already fixed on the latest version (5.98.1).

Hi @TwoPlus1, thanks for the report. I can reproduce the bug. We will fix this for the next release (5.99)`

Hi @rtjdamen

In the VM's advanced tab, in the Misc section, you should see Resource set with a selector.

Hi

Fix available on the master branch.
Commit: b539b

Hi @abudef
A fix is available on the branch fix-attach-pci

Hi @abudef thanks for the report. I spotted where the bug came from and I will fix it soon.

@abudef As workaround, you can run an XO locally, shutdown all your VMs from your host and toggle your PCI from your local XO.
Otherwise it's also possible doing it with command line.

In the modal, if we simply change the buttons like this: [Reboot, Force Reboot, Cancel], instead of [Ok, Cancel] would that be sufficient?

So the error is "normal".
XOA tries to evacuate your host before restarting it, but your host's VMs have "nowhere to go" since you don't have another host.
Are you using XO from sources?

Hi @abudef

how many host do you have in your pool?

Ho, i see the it was already planned to be in the pool dashboard for XO6.
Not yet designed BTW.

Ok, we take the request into account, and we transmit the information to our XO6 designer! Thanks