Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with omnissa Horizon client thinstation-ng #880

Open
trezel opened this issue Feb 25, 2025 · 5 comments
Open

Issue with omnissa Horizon client thinstation-ng #880

trezel opened this issue Feb 25, 2025 · 5 comments

Comments

@trezel
Copy link

trezel commented Feb 25, 2025

Hi,

I'm trying to build an omnissa thin client, and I noticed some bugs in thinstation-ng :

First, omnissa autostart doesn't work. The message (in logs) tells options fullscreen and allmonitors can't be used together.
I couldn't find any allmonitors option in conf files, and didn't find the way to disable it. Disabling fullscreen option in SESSION options makes the omnissa autostart to work, though (and in fullscreen mode !).

Second, during building, I saw an error message :

Configuration file /etc/systemd/system/horizon-USBArbitrator.service is marked executable. Please remove executable permission bits. Proceeding anyway.

I tried a chmod -x on this file in chroot, before a new build, but error message still present. It seems the executable bit is added during build process.
The service can't launch (error message during client start).

Have a nice day

E.T.

@rohrbachger
Copy link
Contributor

trezel,
on earlier versions I changed after the first build process in vmview/etc...
After the next build it was in the iso .
How large is your image with omnissa, I have 700MB, this does not start as ISO under iPXE.
Don gave same hints, I need to check this and your good described way to boot with iPXE.
But in general he imag is much larger, before I was under 500MB

@trezel
Copy link
Author

trezel commented Mar 7, 2025

Hi,

A few days later....
Omnissa client finally works.

First, the "fullscreen thing" : You can disable fullscreen option in SESSION# options, and it launches, as I told in the first post.
I found the all monitors option, in build/packages/horizon/etc/cmd/horizon.global
This file is a place where you can add more launch options, if you want.

Second : the error message about "horizon-USBArbitrator.service is marked executable" doesn't prevent omnissa client to work (USB works).

Last : I couldn't launch a VM, without disabling H246, av1... in omnissa client's preferences menu. Even with nouveau driver installed. We need nvidia drivers for this to work, and since nvidia driver installation is for now impossible in ts-ng,..
It doesn't seem clean to me to oblige users to make such things everytime they want to connect.
I found the solution for this too (leaving only blast) :

  • Create a file named horizon-mandatory-config with these parameters :
view.allowBlastProxy = 'FALSE'
view.allowBlastToast = 'TRUE'
view.enableAV1 = 'FALSE'
view.enableBlastCodec = 'TRUE'
view.enableH264 = 'FALSE'
view.enableH264YUV444 = 'FALSE'
view.enableHEVC = 'FALSE'
view.enableHEVCYUV444 = 'FALSE'
  • Put it in : build/packages/horizon/etc/omnissa/horizon-mandatory-config
    It will be present on clients, and configure the right options for users.

If it can help someone...
Regards

E.T.

@Doncuppjr
Copy link
Collaborator

I wonder if your just missing codecs, or if you really need Nvidia proprietary for this to work.

@trezel
Copy link
Author

trezel commented Mar 7, 2025

I'm not sure neither. Maybe some codecs, you're right.

But nouveau is sufficient for the need we have. The only annoying thing for me was the configuration tasks the user had to do before launching a vm. This is fixed with horizon-mandatory-config file, it's enough for me at this time.

I took a look at installation of rpm nvidia driver file, but I found it was out of my abilities in thinstation, to install a rpm, first, and then debug nvidia driver... I chosed the lazy way.... waiting for Don to manage this ;-)

Thanks
E.T.

@Doncuppjr
Copy link
Collaborator

The lift on the Nvidia driver is quite a bit of work, as I mentioned earlier. I don't personally have any real use for this, so likely it would need to be a sponsored effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants