@edisoninfo Great! This warning is a life saver and did perfectly its job, allowing you to discover a hidden issue Glad you found the root cause!

Hmm could the module causing the crash if the device isn't accessible? @TeddyAstie any opinion?

@Cygace Someone from the community may jump in and help troubleshoot this. The best approach would be to not modify the Dom0 installation by installing Zabbix via a community post, as you're customizing the installation. The vates team and XCP-ng specifically need to include these packages to ensure you're able to get support. Best of luck

That's because you are using DMC (dynamic memory control). Try on a VM with static == dynamic.

You are welcome Enjoy XCP-ng/XO!

Great! Thanks for the feedback

That's weird, but OK. Maybe it's because even when you update, the old/existing RRDs data won't be "replaced".

Yes, even if there no code, there's a lot of pushing on our end to make it happen on their side

@Andrew said in XOA suddenly "empty" during rolling update: @halvor Yes, kind of... The pool master must be updated and rebooted first. If you move the master to a different host then you are no longer rebooting the pool master first. XOA is just a very smart client and needs the pool master to provide all of the pool information. Secondary machines will just redirect to the master, so if you try to connect XOA to one as a backup it won't work. You just need to wait for the master to reboot and return to a functioning state and wait for XOA to automatically reconnect. The everything will start happening again. If your master host is destroyed (ie. software corruption, hardware failure) then an existing host can be forced to take over the pool as master, but this is not a good thing to do unless the actual pool master is unrecoverable. Ok, great, thank you for clearing this up!

Hello, thank you for your reply @bogikornel @TrapoSAMA . Here are my processor specifications: Intel Xeon E5-1620 v2 (8) @ 3.691GHz. Unfortunately @Andrew , I have to use RHEL 10 on my server ^^ but thank you for providing the link. I will change my processor/server.

@bryonadams said in Trouble Creating VM via API: Is there a place I can submit a feature request to allow setting a description and other settings from the UI to get feature parity when creating a VM? Otherwise, there's not much point since I have to go in and touch the new VM anyway. Unless I'm going about this wrong to begin with? You can create a feature request on Xen Orchestra github repository (https://github.com/vatesfr/xen-orchestra/issues), and if you have subscribed to support via XOA you can send a request through Zammad.

@Forza said in MegaCLI and StorCLI lastest version for 8.3 LTS: @jangar don't they have a statically linked version of storcli that can be downloaded? latest version is for min RHEL 8x i have older version https://docs.broadcom.com/docs-and-downloads/raid-controllers/raid-controllers-common-files/8-07-14_MegaCLI.zip and https://docs.broadcom.com/docs-and-downloads/007.2705.0000.0000_storcli_rel.zip i've installed them and seem work, but i'm not sure other command thank check raid status work tomorrow. wget https://docs.broadcom.com/docs-and-downloads/raid-controllers/raid-controllers-common-files/8-07-14_MegaCLI.zip unzip 8-07-14_MegaCLI.zip rpm -ivh Linux/MegaCli-8.07.14-1.noarch.rpm alternatives --install '/usr/bin/MegaCli64' 'MegaCli64' '/opt/MegaRAID/MegaCli/MegaCli64' 1 alternatives --install '/usr/bin/MegaCli' 'MegaCli' '/opt/MegaRAID/MegaCli/MegaCli64' 1 alternatives --install '/usr/bin/megacli' 'megacli' '/opt/MegaRAID/MegaCli/MegaCli64' 1 wget https://docs.broadcom.com/docs-and-downloads/007.2705.0000.0000_storcli_rel.zip unzip 007.2705.0000.0000_storcli_rel.zip cd storcli_rel unzip Unified_storcli_all_os.zip rpm -ivh Unified_storcli_all_os/Linux/storcli-007.2705.0000.0000-1.noarch.rpm alternatives --install '/usr/bin/StorCli64' 'StorCli64' '/opt/MegaRAID/storcli/storcli64' 1 alternatives --install '/usr/bin/StorCli' 'StorCli' '/opt/MegaRAID/storcli/storcli64' 1 alternatives --install '/usr/bin/storcli' 'storcli' '/opt/MegaRAID/storcli/storcli64' 1

I have no idea what this flag is doing, so my gut feeling is: no, it's not on XO side but a "problem "on the reverse proxy itself.

@Berrick Ah cool, I was anticipating that doing it live would've caused boot issues but I think I've just got a bug in my head about how it actually works, I'm conflating two separate things based on an incorrect interpretation of a previous experience I had once with XCP. Thanks!

What about the browser console?

Yes! That's a good guide for what you want to achieve

Hmmm that's a possibility. An interesting lead to explore. Ie trying to do it yourself to see if the result if the same?

Yes, the old method should work

@CodeMercenary hello and thanks for this idea! We will discuss about it with @clemencebx and see what we can propose on new XO-6 design and workflow.

@planedrop While you are connected to the XOA VM, be sure to verify that the required changes have been performed on /etc/systemd/system/xo-server.service when the VM memory was increased. Details can be found in this troubleshooting KB article -- https://help.vates.tech/kb/en-us/31/48