| 5 Dec 2025 |
|  okamis joined the room. | 14:15:27 |
| 9 Dec 2025 |
| okamis | Hello, Im in a pickle, im using runnixostest as an interactive playground, and in my machine nixosconfig when I set k3s.images=manyImages it slowly eats all my disk space
in the filesystem shared and xchg and then every following command just gives input/output error. How can I go about resolving this? The /tmp/shared itself is empty when I try to list its content
[root@machine:/tmp]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 800M 0 800M 0% /dev
tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs 4.0G 3.4M 4.0G 1% /run
/dev/vda 49G 3.1G 44G 7% /
nix-store 196G 20G 166G 11% /nix/.ro-store
tmpfs 7.9G 0 7.9G 0% /nix/.rw-store
overlay 7.9G 0 7.9G 0% /nix/store
shared 3.2G 3.2G 36K 100% /tmp/shared
xchg 3.2G 3.2G 36K 100% /tmp/xchg
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
tmpfs 7.9G 1.1M 7.9G 1% /run/wrappers
tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service
tmpfs 1.6G 4.0K 1.6G 1% /run/user/0
| 13:03:56 |
 K900 | That's honestly not a thing it was designed for | 13:05:03 |
| K900 | Why not set up a proper VM | 13:05:08 |
| okamis | Its such a nice way to do proof of concepts on. | 13:07:05 |
| K900 | nixos-rebuild build-vm is not nice? | 13:07:56 |
| okamis | I dont know I been using nix run .#packages.x86_64-linux.test.driverInteractive | 13:08:45 |
| okamis | I will read up on build-vm | 13:09:19 |
| K900 | ... | 13:12:06 |
| okamis | Do you have any knowledge of the issue? using build-vm I get a 168GB /tmp/shared. What limit of runnixotest did I break? | 15:19:06 |
| okamis | * Do you have any knowledge of the issue?, What limit of runnixotest did I break? Using. buildvm I get a 168GB /tmp/shared dir, Im guessing its a qemu thing but Im not really sure of its purpose | 15:20:08 |
| K900 | The test VMs have limited disk space, by design | 15:21:26 |
| okamis | Where can I read up on that? there is the config virtual.diskSize, but I take it its different from the /tmp/shared | 15:23:33 |
| okamis | * Where can I read up on that? there is the config virtual.diskSize, but It doesnt affect /tmp/shared | 15:24:38 |
| K900 | /tmp/shared specifically is backed by a temporary directory, which is probably backed by tmpfs, which is backed by RAM | 15:25:39 |
| K900 | With build-vm you should not have a /tmp/shared at all unless you've configured it explicitly | 15:25:53 |
| okamis | with build-vm I did get a /tmp/shared, but my confusion is more why I cannot see anything in /tmp/shared, I just see it consuming disk | 15:27:43 |
| K900 | See anything where? | 15:28:12 |
| okamis | ´ls /tmp/shared´ gives me empty dir | 15:28:28 |
| okamis | * 'ls /tmp/shared' gives me empty dir | 15:28:40 |
| K900 | You might want ls -a | 15:28:49 |
| okamis | * 'ls -a /tmp/shared' gives me empty dir | 15:28:57 |
| K900 | If it's still empty, I'm guessing this is just qemu misreporting filesystem size for shared folders | 15:29:14 |
| okamis | thank you for sharing your wizdom, bye-bye | 15:30:25 |
| 11 Dec 2025 |
|  suua joined the room. | 16:11:27 |
| 13 Dec 2025 |
 l0b0 | How do I disable the NixOS "Tour" popup when starting GNOME for the first time? I had a look at nixpkgs/nixos/tests/gnome.nix, but it's not obvious what they do (or even whether they dismiss or disable the popup). | 13:01:52 |
| l0b0 | * How do I disable the NixOS "Tour" popup when starting GNOME for the first time? I had a look at nixpkgs/nixos/tests/gnome.nix, but it's not obvious what they do (or even whether they dismiss or disable the popup). Update: nodes.machine.environment.gnome.excludePackages = [ pkgs.gnome-tour ]; seems to have taken care of it. | 13:04:54 |
| l0b0 | How do I send the Super key to GNOME in a test? send_key doesn't seem to support it. | 13:39:15 |
| l0b0 | * How do I send the Super key to GNOME in a test? send_key doesn't seem to support it. Update: It doesn't seem to be documented anywhere, but an old forum post had the answer: meta_l or meta_r. | 13:41:58 |
| l0b0 | Why does machine.wait_for_text(r"some regex", 10) never seem to finish? It prints "machine: waiting for some regex to appear on screen", then continues to print system logs, and never exits. This is the last line of code in the test, so it should exit after 10 seconds. | 13:48:24 |
