@lsouai-vates Great! Thanks for addressing this

@Greg_E Ah, ok..yeah...guess I did Yep, agree. Really needs more functions...like networking (and elsewhere) ha

I have not had time to work on this, and my lab changed significantly, had to spend a bunch of money to move it to a new rack and that rack has been disconnected for months so no real work in XCP or vSphere and learning to migrate VMs from vSphere to XCP which was one of my big intentions. But a recent post confirms that this "oddity" of trying to create a UEFI VM from XO-lite is still present. I'd bet money that this gets fixed before or when the full release is provided. https://xcp-ng.org/forum/topic/11227/boot-new-vm-to-iso-in-xo-lite Workaround is to either click the button provided to download XOA, or install Linux and XO from sources in BIOS mode. Then you have the full XO to work with to bring everything else up the way you want it. I see it as a minor annoyance right now, not really a bug or problem.

Thanks for engaging! In this thread I would say: Storage I need it to get ISO files uploaded without going native (CLI). Or in other words, the basic stuff you would expect of a web-interface to be able to launch working VM's.

@olivierlambert said in Limiting access to xo-lite to a specific IP address or ssubnet: About iptables, there's /etc/sysconfig/iptables but I'm not sure it's the right place to put manual modification, that's why I pinged the @Team-OS-Platform-Release In a way that's the right place, but one needs to be careful with modifications there.

@olivierlambert can you close this thread?

No. I'm saying that all VMs (HVM) are using RFB consoles, readable with VNC protocol (used by XO or a VNC client). There's no text console since it's like a screen in HVM. If you are stuck on "Loading in progress", it's not a console issue, it's a VM issue. You can use a LiveCD to check what's going on.

@olivierlambert I did reboot the system. The fact that I can access everything fine with the using the external url but not when I try to use the local IP address of the machine is strange. I'm at work currently but I'm going to do a deeper dive when I get home and search through everything in my home network. I just don't know what else to check.

Oh I see. Thanks for explanation

@Danp Yes I. have .. no change

@DustinB Hi Dustin, It's amazing what one can miss when setting something up, and I surely did miss that part. I now see much more in the way of management items. My project for the weekend will be XO/XOCE from source for my home rack. Thanks so much for seeing what I didn't. Take care, Eric

@Greg_E Having backup XO's has always been our policy here. @business we have our min XOA on a (now dedicated Intel server doing the backups, because of the EPYC networking issues) and then a XO (from sources) on the main pool if XOA tanks or during reboots. @home I hace one XO on each host. Has saved me time and time again.

@pdonias said in Wrong colours in dashboard: Thanks for the feedback, we'll take care of that. To get more of an idea about the HDR technology checkout these links:- https://www.viewsonic.com/library/photography/what-is-hdr-hdr-vs-sdr/ https://en.wikipedia.org/wiki/High_dynamic_range https://www.dolby.com/technologies/dolby-vision/ Some of the links refer to videos though the graphics technology applies outside of videos, these will help you get an idea of how the technology will affect the user interface of XOA and XO Lite. In this case it's the colours part of HDR which is relevant as the user interface, doesn't have photos or videos in it but does still have other forms of imagery. Though the client devices may be used with other usage which the full HDR is appropriate for, so thus have compatible hardware and have the feature active. @ph7 If your interested in finding out more about HDR you can also check out the links above. I also added my input about your issue, as I knew that HDR can play a part in the reproduction of colour etc in an image, or user interface. So can have an impact on what colours are used on the dashboard, as well as other parts of the user interface.

Hi @mattnj I think it's possible deploy took some time and as long as you have a XAPI task running, remove can't be done Yes rebooting will "cancel" the task and destroy can work then

@tcorp8310 yes yum update should do the trick

Hi @Houbsi, good question. This is how it works: any XO instance that is connected to a pool will add some information about itself to the pool's metadata XO Lite reads that information to know the URL of XO's UI In xo-server's config, you can force XO to report a custom URL instead of raw network information: [http] publicUrl = 'http://example.com' However, at the moment, XO Lite doesn't support it, but it's coming soon: https://github.com/vatesfr/xen-orchestra/pull/7849 And @olivierlambert, yes, for now, any XO instance, whether it's an XOA or not, reports itself on the pool and we simply pick the latest one. But we can definitely implement something smarter in the future if necessary. pdonias opened this pull request in vatesfr/xen-orchestra closed feat(lite/XoaButton): support `xo-server`'s setting `http.publicUrl` #7849

@Tristis-Oris said in XOLite - Which URL?: @itpartner it already builtin at xen 8.3, so guide will not requried. This, XCP-ng 8.3 isn't released yet, so you're running 8.2 which doesn't include the package.