Fórum Qubes OS Forum

I tried updating qubes. I clicked the rotating icon at the top right of the menu-bar. Two templates dom0 and fedra-43-xfce were checked. Windows-standalone was not checked. I just clicked “Next”. I clicked on the template under update and observed what was going on. For dom0, the view of the log sometimes switched to the top. I clicked “Next” after two templates were updated. I clicked “Finish and restart/shutdown 3 qubes”. (Three qubes sys-usb, sys-net and sys-firewall were checked.) The three qubes were shutdown and they restarted. At this moment, I have a question. Should I do something for reflecting the update of fedra-43-xfce template? The targets I have in mind are default-dvm , personal , untrusted , vault , work and a duplicate of work .

Starbyte: when I open the Windows 11 settings app, it doesn’t show the right panel at all This does not happen for me. I am using 4.3.18 with Windows 11 25H2 Pro. Maybe this behavior depends on the graphics card used by Qubes???

Qubes networking is fiddly even if you have good a understanding of Networking and Linux. Did you read Joanna’s “Playing with Qubes Networking for Fun and Profit” from 15 years ago? Still a good read! (link here ). Read this caveat also: unman’s post . That said, when you use an “app”, in your case - “Karing”(? - of which I know nothing), to establish a VPN connection in a qube, and that app is not designed for QubeOS use, you have to fix manually at least a lot of the nft (firewall) rules to achieve what you desire. To check if your sys-karing is actually accepting and forwarding connections (acting as a netvm), I would connect a simple disposable to it and run “curl https://ip.me ”. If it shows your local IP, it’s not working. If it shows the VPN IP chosen through Karing, it is working. Like this: (xterm on )dispNNNN -> sys-karing -> sys-firewall -> sys-net -> "THE INTERNET(s)"

Thank you GWeck! I am happy to know it’s done.

Спрашивал про этот способ у программистов. Говорят, раньше так можно было. Сейчас очень тяжело обходить таким способом, так как ТСПУ активно ищет и борется с такими обходами. А если почитать в этом треде, как люди усиленно себе голову ломают над этим (и у большинства всё равно не получается), так отпадает всякое желание пробовать. Тем более, что у меня и подавно таких знаний нет, как у них.

Hi. I needed a VPN to bypass the so-called “whitelists” in Russia. The setup: VPN qube → sys-whonix. In other words: VPN at the entry point, Tor at the exit point. I’ve already tried several VPN subscriptions. During the whitelist restrictions, many servers respond to pings and Karing connects to them, but sys-whonix fails to connect to Tor — it behaves as if it’s still connecting via sys-firewall instead of Karing. I need to determine whether connection fails because the VPN servers themselves cannot bypass the whitelists or because Qubes requires additional configuration. Here is a description of exactly what I did: Initially, I used the portable version of Karing to manage my VPN subscriptions/configurations. I created a dedicated Debian-based qube for it, using sys-firewall as its network qube. During testing, I set the network qube for sys-whonix to the qube containing Karing (which I named sys-karing). Next, I used the Karing application to connect to a server that was successfully responding to pings. After that, I attempted to connect sys-whonix to Tor using Snowflake bridges. The result: sys-whonix fails to connect. The behavior is identical to what happens when it fails to connect during the whitelists. Here is what I tried next: I cloned the Debian template of Karing and installed the Karing .deb package inside it. I consulted the Amnezia VPN installation guide and, just in any case, installed all the additional packages listed in the Amnezia VPN manual into the te

In 4.2 I’m able to unlock a disk in dom0 and have the fs’s automatically discovered to mount etc. So they are in /dev/mapper/… and /dev//… But in 4.3 when unlocking in the same way with cryptsetup, it doesn’t work the same. Is there some required lvm command or additional step that needs to be done, or what has changed? Thanks

You don’t need arch to do this, any distribution will do. Many distribute ollama in their package manager, but that makes you use a template to store ollama itself (not necessarily the downloaded models). To store models in AppVM what matters is not the way you install ollama, but how you configure it. By default ollama stores models in the home directory of the user ollama server runs as. To store models in an AppVM you either need to ensure that home directory is persistent on the AppVM, or directly set where ollama server stores models using OLLAMA_MODELS environment variable. Probably the easiest way to do this is to set ollama user directory to a persistent location, such as /usr/local/ollama : # install -d -o ollama -g ollama -m 700 /usr/local/lib/ollama_models # usermod -d /usr/local/lib/ollama_models ollama This approach assumes that ollama is installed in a template, and user directory modification requires running the commands in the template. Alternatively, you could set User and Group of ollama service to a user with persistent home directory, such as your user user , but that is less appropriate unless you plan to use the ollama qube just for ollama and nothing else.

If we check the contents of the ollama installation script , we observe that it checks if you have /usr/local/bin/ in your PATH first among other installation directory candidates. That means it will install ollama into /usr/local/bin/ if you have it in your PATH . Run echo $PATH to see what you have in path. /usr/local/ is persistent on AppVMs . Things you install there are kept between reboots and consume private storage of the qube. The script is not perfect though, it creates ollama user and configures the service in such a way they are not preserved between reboots. It also may try to install drivers if you don’t have them installed already. Service and user are easy to fix by moving /etc/systemd/system/ollama.service to /usr/local/lib/systemd/system/ollama.service and either replacing User and Group values with a persistent user or creating ollama user in the template.

Experimental Qube Manager feature: Convert AppVM to StandaloneVM I have developed an experimental Qube Manager feature for Qubes OS 4.3 that adds a “Convert to StandaloneVM” action to the VM context menu. Repository: github.com GitHub - demosios/qubes-manager-convert-to-standalone: Qubes OS Qube Manager feature adding AppVM to... Qubes OS Qube Manager feature adding AppVM to StandaloneVM conversion with configuration and application-menu preservation. This is an unofficial development build and is not part of the standard Qubes OS packages. What it does When exactly one halted AppVM is selected, Qube Manager offers: Convert to StandaloneVM The original AppVM is retained. The feature creates a new VM named: -SA The new VM is an independent StandaloneVM and has no TemplateVM dependency. Configuration copied The conversion copies: The template root filesystem into the StandaloneVM root volume The AppVM private volume Network configuration, including netvm Memory, CPU, boot, kernel, GUI, audio, and management settings Backup and disposable-VM settings VM features, including application-menu selections and service features Tags Notes Firewall rules Persistent device assignments where supported Generated application menus The original AppVM is not modified, renamed, or deleted. Application menus Application-menu selections are stored as VM features, but dom0 menu entries must also be regenerated. The feature starts the new StandaloneVM and runs: qvm-sync-appmenus --force-rpc -SA Th

Hello! First I wanted to thank you on all the wonderful work you’ve done on the new QWT, it has been something I have wanted for a while and it’s nice to see it coming along! I do have a few odd-ball bugs to report. The first is that when I open the Windows 11 settings app, it doesn’t show the right panel at all. When I tried to take the screenshot, all the windows in seamless mode disappeared and half of them came back (this is another bug that seems to happen often, almost as if it’s disconnecting and reconnecting) so I can’t show a weird glitch I had but I can explain it. When I would open settings previously, the inactive lusrmgr window would paint the contents of the right panel of the settings window, I could navigate settings via the two windows using keyboard navigation but this is obviously not the expected behavior. I am not sure if maybe the seamless driver is confusing the buffer spaces between windows or if it’s something else. The next bug I had was during install, I believe the instructions somewhere stated to run the installer 3 times, however, I was able to run the 1st install just fine, reboot, and it started in seamless mode unprompted. When I tried to run the installer the 2nd time, it removed all the windows and I was unable to see anything at all. I rebooted after waiting a few minutes to see if the installer was just doing things in the background and the windows returned but re-running the installer does the same thing so I am unsure if it is partially

Thank you all for the responses. As this is open-source, anyone wishing to enable IPV6 functionality is free to do and they are welcome to post the change here in detail for the rest of us. I am not a ‘legitimate IT professional’.