Spice ( virt-viewer) resolution change on fullscreen

[RudiOnTheAir]

Hi

The virt-viewer v9 seems to have a problem with the resolution. Usually the viewer adjusts the resolution to the client resolution. I just copied an iso to a USB drive and started it. The resolution of the VM is reduced to the smallest possible if the fullscreen is activated in the virt viewer. Did I configure something wrong?

Thanks in adv..

[RudiOnTheAir]

Wait, it seems that only happens on a RockLinux9 virtual machine. Not on windows11. But the latest virt-viewer v11 has no problem with that os. Maybe the virt-viewer could be updated.?

[Doncuppjr]

thinstation-ng uses Fedora binaries and has v11.

[RudiOnTheAir]

That means i have to start over with the dev env from here?

https://www.thinstation.org/TS-7.0.0-Installer-0101.iso

[RudiOnTheAir]

Whats that? Should i better stop using thinstation ?

[Doncuppjr]

It's a banner. For your own creations, you can change the text to anything you want. I had to pick something. I guess I could have been a little less specific. It's not USG, unless the USG makes the images.

[RudiOnTheAir]

What about simply removing it from startscreen...?

[Doncuppjr]

True, you don't have to have it all.
LIGHTDM_BANNER=true enables it, don't have that set that during build, and you will have no banner.
Use autologin, also no banner. Banners are however a typical req for corporate and government systems.

[RudiOnTheAir]

OK, thanks for help..

[Doncuppjr]

I have updated the banner for you, and of course for my own entertainment. :)

[RudiOnTheAir]

Oh, thanks so much. Yesterday i created a first iso, that is booting from USB, but ending in a black screen... Will try it again.
My thinclients are from HP with a small 8 GB flashdrive inside..

[RudiOnTheAir]

The settings for the lang are not stored after change to another language...

[Doncuppjr]

I've not migrated all the locale packages from 6.3. I only speak english, so my incentive is low. You could however compare the locale-en_US from 6.3 and 7.0 to see what changed, and replicate those changes for whichever locale you use. TS does not store anything by default. You can make a home partition, have it mounted and then any user settings will persist, or you can fix the locale and force a client to use a specific language with each boot.

For diagnosing the black screen, try using the other kernelcmdline in build.conf and disabling the logo

[RudiOnTheAir]

TS does not store anything by default

Not? I mean, that the 6.x has stored the language settings. So what. Thats not realy a problem, i thought that was something to fix in this beta state. For me the lang is not the problem, more to find something like / and @ on the wrong keyboard then... ;)

[Doncuppjr]

A locale is a multifaceted thing. It describes how a person from a region expects to interact with a computer. Much like a car, which basically has four wheels and a steering wheel, but in one area, people drive on the right hand side of the road so the steering wheel is on the left, and in another area, people drive on the left hand side of the road, so the steering wheel is on the right. For a locale, that means which keyboard map is used, how is money represented, how is time represented, what is the preferred language and a few other details.

[RudiOnTheAir]

Yes, thats clear. I mean, i added german aus keyboard layout und removed english. After reboot the "hd installed" thinstation has german removed..

[Doncuppjr]

I completed the migration of the locale's from 6.3 to 7.0. Maybe this will work for you now.

[RudiOnTheAir]

OK, that means, everytime u changes something, te user has to reinstall the dev enviroment from iso?
I tried to rund dnf update. But that does not work, gives a disk full message...

//edit - OK. Now the german keyb. is stored. Tnx.

[RudiOnTheAir]

OK, with disabled Logo and selinux=0.. > started in proxmox vm to test only the boot

Lighdm is enabled.

btw. on the 6.x release i was able to enable a default hardware in the config. The 7.x has only options for qemu, vmware... But i run the resulting iso on real HP thinclient hardware...

[Doncuppjr]

No, not everytime. In this case Start->DevStation->Update-DeVstation.

[RudiOnTheAir]

No, not everytime. In this case Start->DevStation->Update-DeVstation.

OK, my bad. Havn't seen this..

[Doncuppjr]

With regards to the sshd, I would have to see your whole config, I can't replicate over here with my configs.

[RudiOnTheAir]

Oh, thats simple. The most is default. Only enabled spice, some passwords, disabled selinux.
In the thinstation.conf.buildtime i've only change the ntp and the timezone...

The build.conf:

https://paste.schwoon.info/?dfc8c68f455806f6#ffQyrLNkq59wCTzgfXpAZiwd5rH4nLMo7szMAsXpHiP

[Doncuppjr]

So I used your config, and the system booted without issue. No failed services, no hang. I wonder if the network is timing out. Perhaps try networkmanager instead of autonet. It might be more tolerant of slow networks.

[RudiOnTheAir]

OK, build is running. That takes some time. Will report tomorrow. On what hardware u are booting? Or virt. env?

[Doncuppjr]

Virt.
Start->DevStation->Test-Build->CD

[RudiOnTheAir]

?
I use "Build Image" und copy the iso to my virt host to boot... Isn't the Test Build not a dry run only?

[Doncuppjr]

No, it starts QEMU to test a build that you have made. If your host is a VM, then you will need to enable options for nested virtualization, as QEMU uses KVM.

[RudiOnTheAir]

Perhaps try networkmanager instead of autonet

That has not changed anything... Try to change the vm to allow nested virt...

//edit nested virt won't run at a first check. But thats not the problem here...

[RudiOnTheAir]

If you are interested in taking a deeper look in my last iso...

https://cloud.schwoon.info/s/ttFz59qzPWgZwec

[Doncuppjr]

The ISO booted without issue. Maybe you need more RAM. I would think 4G is enough to do pretty much anything, and usually the least amount you can get on a PC these days.

[RudiOnTheAir]

WTF... Yes, you're right. Added 4GB of mem to my vm and it booted... Now i will see, how much is inside the thinclient

[Doncuppjr]

Another approach for memory constrained systems is to change fastboot from "lotsofmem" to "true". That will leave most of the OS on disk until needed vs lotsofmem which loads everything into memory. lotsofmem is the best user experience with quick application launching, but it does use more memory than other modes.

[RudiOnTheAir]

Will test that tomorrow. On the thinclient hardware ist only 2 Gb mem.

[Doncuppjr]

Also set MEMORY_CONSTRAINED=true in thinstation.conf.buildtime

[RudiOnTheAir]

Sorry that this ended up being a bit off topic.
Version 7 now runs with the latest fix for memory requirements.
In the end, that doesn't have much to do with the resolution problem. But initially it was about a newer version of the Spice Viewer. So maybe it's OK.
I'll close the ticket now and thanks for the help... The next step is to integrate the proxmox spice tool.. ;)

[RudiOnTheAir]

One last issue. The iso is booting from usb drive. But when written to disk with dd if=..iso of=/dev/sda it hat the same fastboot trouble like before. Maybe using dd isn't a good idea.. On disk it will be shown as cd image only.

And no, i can't put the disk on the system where i build the iso. So it would be nice to have a tool or script inside the usb drive. I had used a separete live linux (partedmagic) to write the iso to disk...

[Doncuppjr]

It's pretty easy to write a script to do the install. The total outcomes are so expansive, that I don't include anything by default, but here is an example that you could tailor to your needs. https://github.com/Thinstation/thinstation-ng/blob/7.0-Stable/ts/build/packages/blue-green/bin/initialize

[Doncuppjr]

You could also use the flash utility, and then dd that onto the sda disk, as long as your not using EFI.