alturismo

Hi, may i think wrong, but currently i see low, small usage on isolated cores while they are not in use thats my cpu pinning, so cores 2/10 up should be off while my VM's (which are assigned there) are off now, when they are off i see some small usage all over, 1-3 % now when i try to check what is running on them as sample root@AlsServer:~# CORENUM=2 root@AlsServer:~# ps -e -o pid,psr,cpu,cmd | grep -E "^[[:space:]][[:digit:]]+[[:space:]]+${CORENUM}" 8681 2 - [kworker/2:2-wg-crypt-vpn] root@AlsServer:~# CORENUM=3 root@AlsServer:~# ps -e -o pid,psr,cpu,cmd | grep -E "^[[:space:]][[:digit:]]+[[:space:]]+${CORENUM}" 7793 3 - [kworker/3:1-wg-crypt-vpn] root@AlsServer:~# CORENUM=4 root@AlsServer:~# ps -e -o pid,psr,cpu,cmd | grep -E "^[[:space:]][[:digit:]]+[[:space:]]+${CORENUM}" root@AlsServer:~# CORENUM=5 root@AlsServer:~# ps -e -o pid,psr,cpu,cmd | grep -E "^[[:space:]][[:digit:]]+[[:space:]]+${CORENUM}" 5502 5 - [kworker/5:1H-events_highpri] root@AlsServer:~# CORENUM=6 root@AlsServer:~# ps -e -o pid,psr,cpu,cmd | grep -E "^[[:space:]][[:digit:]]+[[:space:]]+${CORENUM}" 1303 6 - [kworker/6:1-wg-crypt-vpn] 5501 6 - [kworker/6:1H-events_highpri] root@AlsServer:~# CORENUM=7 root@AlsServer:~# ps -e -o pid,psr,cpu,cmd | grep -E "^[[:space:]][[:digit:]]+[[:space:]]+${CORENUM}" 5500 7 - [kworker/7:1H-events_highpri] root@AlsServer:~# and so on ... same on the HT cores which are more likely in use. am i wrong or did i miss something ?

here how it looks like, as you see chrome in guacamole

then you do something wrong, just tested here and works

no, i say add a port maping in chromium docker and setup with 5900, thats it.

@dfox1787 and as you use(d) firefox browser (i guess djoss one) you should be aware about the 2 different ports, its explained in his template about web front end and vnc direct ...

like described, this wont work, you try now to connect to the webinterface which is used in the chromium docker and not directly vnc. this docker also provides its own web interface for vnc, like guac is ... but guac wont work with this, im pretty sure its listening locally on 5900 (standard vnc port) and if you try to keep inside your proxynet its overall completely wrong. then you should use as host your dockername like "chromium" lower case ONLY and as port 8080 (the local port, not the port provided to your net) ... but as mentioned is NOT the VNC port ... i would suggest to add the port variable like described and try port 5900 then

@dfox1787 may show your setup what you did. im pretty sure you are connecting wrong from guac to your chrome docker, in terms you use VNC protocol i guess, you have to point to the native vnc port in the chrome docker and by default this port aint added to the template. by default the bridged port from the template is for the webui and not from vnc, you should add a port forward in the docker like 5900 5900 and no, this has nothing todo with security ... then guac can connect via vnc. sample

Hier ein Ansatz

@limetech would be really nice if this would be included, would make life alot easier when working with hooks

Hi, as we have libvirt 6.5, shouldnt it be possible to use hook scripts ? i created the folder /etc/libvirt/hooks/qemu.d/ where the scripts should be executed ordered by name (i only need 1) so in my case i added a script work_gvt.sh, chmod +x, with the following content (also a test output which also doesnt get executed) #!/bin/bash echo "Testrun" > /mnt/cache/testrun.txt if [ $# -ge 3 ]; then if [ $1 = "Work_gvt" -a $2 = "prepare" -a $3 = "begin" ]; then echo "Creating vgpu" echo ee0036c0-8e21-40b2-9f33-8d5c5f6f5f93 > "/sys/devices/pci0000:00/0000:00:02.0/mdev_supported_types/i915-GVTg_V5_8/create" elif [ $1 = "Work_gvt" -a $2 = "release" -a $3 = "end" ]; then echo "removing vgpu" echo 1 > "/sys/devices/pci0000:00/0000:00:02.0/ee0036c0-8e21-40b2-9f33-8d5c5f6f5f93/remove" fi fi so question is, only possible to modify the limetech qemu file to initiate things ... which shouldnt be the goal i d guess.

@Michel Amberg may tried ip instead hostname, i use it on custom bridge and can connect to an rdp desktop, but i use ip instead hostname @nik82 may uninstall, reinstall guacamole to revert whatever patch you added ?

at least 3x [emoji41] its a major improvement ... thanks again@ich777 Gesendet von meinem SM-G981B mit Tapatalk

after the nice explenation from @Alex R. Berg i took a test here again and turned cache dirs on again while turning off /mnt/user as its useless anyway when i understand him correctly (in the current state). what i can say now, its still working here at least, sample procedure i always can reproduce scenario 1 all activity always ONLY on cache drive i cut and remux my records to mkv and save them, then scripted way is to remove original files, let filebot do its job and rename and move to proper target location, now scripted is triggering api calls to plex and emby to refresh and import the new files there too immediately and here is now the change no cache dirs active -> disks spin up ... cache dirs activated -> all good here scenario 2 Kodi on my Desktop Computer, opening kodi (using emby backend) also would always spinup the disks cache dirs activated -> all good here prolly more but these are 2 scenarios as "daily drivers" where i can say there still is a difference with/without cache dirs. cache Dir Settings with my Shares forgot, im on 6.9 rc2, and since latest releases i had alot of spinups over and over again, now back to normal usage again, so thanks for keeping this alive as good as possible @Alex R. Berg

i guess lsio wont make a sample config for every possible app out there so to your questions, yes of course, u can use "externals" too. may take a look at your folder where the sample are and ... use ip instead container_name as sample ...

32400 is the direct connection to your plex docker, then reverse is out of the game. if you need a more safe protection is up to you, behind reverse means its only listening on the specific hostname for plex, port 32400 doesnt matter then, but i personally never heard of someone hacking plex servers ...

if you are properly behind a reverse proxy you should be using port 443 and not 1443 (thats the internal port for swag)

@b3rs3rk may in case u get bored and do some sort of gpu stats plugin for the vm users, if they would run gpu-z in the background including logging, the idea may, tail the logfile for realtime data and put them to the dashboard just as idea little backdoor to the data needed for such a plugin.

good, may as note, the writer of webgrab+ is also helpful, he is active in his forum in case you hang now with your setup

may take another look at the page you posted above, its in the readme

u should consider that this is really meant for 1 purpose, keep kodi's sync and have a updater kodi on a server without keeping a client awake, if you want todo so, setup a local kodi, setup media folders as network shares (pathes will be a hard time ...), etc etc ... and it works nice, but actually not really your usecase ... look for emby, plex, or even tiny media manager therefore just for watching your library ... like advised before here, easier for you now to hndle and even a better user experience for your case

here a sample when emby stalls ... after 100 % fillrate in /tmp stream stops, cant continue, only stop and restart stream.

emby falls back to /config/transcoding-temp .. plex yes, it will use /tmp

after some tests also consider to test the apps how they behave when tmpfs gets full sample, plex has a management and is working in a 80 - 90 % windows when filling up emby on livetv filling to 100 % and stops/crashing the stream, only exit, restart works, wont continue even it tries to free up ... emby on local media also filled up to 100 % ... playback runs a little longer (due not a live stream) but also stalls after a while ... both emby tests with active throttle on transcode so, plex, good solution, emby, not (yet) prolly by emby design

@ich777 in emby, ffmpeg transcode logs before and after restarting docker before -segment_list "/transcode/transcoding-temp/95499A.m3u8" after restarting docker -segment_list "/config/transcoding-temp/BDAC04.m3u8" of course the segmented files also come in there ...

yes, but not really a solution when u need to run a script after docker run and restart, but im glad im not alone ... same goes for any docker like emby too it seems ... at least after tests here and i would say, this would also hit in when u just restart the server (which in the end restarts dockers too)