@gduperrey

Thank you for the reply. The use case is to centralize all of our reporting and monitoring for all of our devices. We have a number of XCP host, various servers, etc, that we are responsible for, and all of them besides our XCP nodes are being monitored for real-time analytics by Netdata. We are also using Zabbix for trending and long term usage but would like to be able to move the XCP nodes into our Netdata cloud versus being just on XOA/XCP.

I also understand this would be overidden by updates and that you guys cant support it. I mainly wanted to see if it would "break" anything you already have in place. As a feature request, maybe have a way that you can report to a Netdata cloud instance. That would be nice.

Hello,

I know you have the Netdata binaries on XOA/XCP with the advanced analytics, but do you guys "support", and I use support as in not Vates supporting me on its use, but if I installed this, would this cause an issue with your implementation of Netdata? Also, would this need to be reinstalled after every update of XCP-NG.

Thank you for the help.

And if I am not mistaken, this setting in Proxmox has nothing to do with RDP connections, this would only apply to the "console" correct?

He is also comparing this to Proxmox which can be set to 256M for example.

My user is wanting a "buttery smooth" video. Honestly, he has some somewhat high expectations of what he is trying to do. This is an RDS server running session based connections.

He needs to use GPU passthrough, but until then, I need to see what I can do to move this to something higher than 16MB if I can.

Thank you for the help.

I see that in XOA and XCP-Centre, you can only set the video ram to 16MB. I looked for a CLI command to set it higher in the CLI reference location but did not see anything that specifically said video ram, only "memory settings".

Is it not possible to set the emulated video RAM above 16MB?

Thank you for the help.

Hello Vates Team,

What is the current support status of XOSTOR on 8.2 or 8.3? If I am needing an XCP-NG cluster using XOSTOR, is it support now or still not considered production ready?

Thank you as always. Keep up the good work, your guys are great.

This just started on my XOA server yesterday. I am getting over 1000 of these tasks in my running tasks list.

It does not seem to be affecting the operation of XOA but this seems odd.

Any guidance would be helpful. Thank you.

@Andrew, Thank you for the reply.

Hello.

I set up a new backup on my XOA, and according to the documentation, it is recommended to use NBD. The connection I am using says, "No NDB connection." Before I change this, I want to ensure that when I enable this, it does not cause any issues with anything else or cause a blimp in traffic.

Thank you all for the help.

@olivierlambert thank you. I am on the official channels since I pay for premium. I will wait to see the fix this week.

@olivierlambert this is my first time using a proxy that is not over a VPN link. I have another that works fine, but there is a VPN link between the server and the proxy.

Also, same behavior as mine. I can see stats as well. I will report this on the Github site.

@olivierlambert thats what I thought. I have another proxy in a another server and it works.

Everything looks correct,I can see the host, and every detail about the VMs, I can create VMs, etc, but I can not view the console. The proxy shows as green and happy and in the servers tab the proxy URL is in place. There is not a VPN between these sites so if that was not in place, it would not connect.

What can I check?

Hello,

Should I be able to see the console of VMs on an XCP-NG install that is accessed via the proxy?

@olivierlambert You know what, I have never clicked on that little guy...

See. I knew I was missing something.. Thank you @olivierlambert

I feel like this should be easy and I may be missing it, but where do I delete a filter?

@gskger There is not a Netdata plugin in my plugins directory.

It shows as running on two of the three hosts. Once does even have it installed.

So I think I figured out my issue. The VMs I was importing were reading off the local storage of the ESX server which is a single SSD. Once I started one that was reading off the the storage device, it went much, much faster.

I still have an issue with something else on imports, but I will open a ticket since I have support. Thank you for the help.

@aurora-chase The XOA has two NICs. One is on a subnet for general access. That interface has a gateway.

The second NIC is on a non-routable subnet, so there is no gateway on the NIC.

When I access the ESX server, I access this server by going to an IP on this secondary NIC. The ESX server also has an IP on this subnet.

You can see a spike in network activity when I first start the migration, but once it starts the task to import into the VDI, it slows to a crawl. Screenshot below.